Hello, On Wed, Dec 18, 2013 at 11:13:01AM -0600, Felipe Balbi wrote: > On Wed, Dec 18, 2013 at 10:40:58PM +0530, Mugunthan V N wrote: > > On Wednesday 18 December 2013 10:38 PM, Felipe Balbi wrote: > > > On Wed, Dec 18, 2013 at 10:30:55PM +0530, Mugunthan V N wrote: > > >> On Wednesday 18 December 2013 10:17 PM, Markus Pargmann wrote: > > >> Mac ID is to be filled by U-Boot and this kind of approach is already > > >> rejected in linux-omap list. > > >> > > >> If proper ethaddr/eth*addr is populated in U-boot environment variable > > >> then mac-address dt property in ethernet* device nodes will be populated > > >> before boot kernel in U-boot. So I don't think this patch series is > > >> required. > > > but will u-boot read MACID from control module ? > > > > > Yes, U-Boot will read the MACID from control module and if a customer > > wants to have his own MACID, U-boot ENV variable ethaddr/eth1addr must > > be updated. > > cool, then I agree this series shouldn't be applied ;-) But even then I'd suggest to take at least patches 1 and 2. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
