| Summary: | beagle-xm: random MAC address | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Robert Berger <pokylinux> |
| Component: | configuration | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | poky.bs.watcher, poky.watcher, yang.shi |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Beagleboard | ||
| OS: | arm | ||
| Whiteboard: | RFC out to meta-ti (29/Jun/2011) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Robert Berger
2011-05-15 02:30:17 UTC
Hi Robert, has this kernel patch been pushed upstream? (In reply to comment #1) > Hi Robert, has this kernel patch been pushed upstream? Hi Darren, Frankly I don't know. Let me ask around on the various mailing lists. It might be something you should not do in the kernel. It looks like there is/was something upstream from the Linaro team: https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/687396 There is also something on openembedded which uses the OMAP's die ID as a MAC (which I find a neat idea) http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026240.html Sent a mail to oe-core and the meta-ti maintainers for their preference on a solution to this as we don't want to deviate from where they go with this. Hi Darren, Assuming the MAC address comes from u-boot it might be possible to get away without a kernel patch. I did not try it out on the beagle-xm, but in general u-boot variables can be read from user space - see u-boot/tools/env. Afterwards a script could be cooked, which patches this u-boot variable into the network config: hwaddress ether <something> Just a thought at 1:00 am so I might also just be too tired for anything more creative. There is some debate on how to best resolve this. We will wait for meta-ti to decide on an approach, and then follow that. Just stumbled across this: http://www.electronsonradio.com/2011/07/angstrom-on-the-beagleboard-fixing-your-mac-address/ https://patchwork.kernel.org/patch/263861/ is supposed to be upstream explanation: http://fossplanet.com/f10/%5Bmaverick-sru%5D%5Bmaster%5D%5Bti-omap4%5D-%5Bpatch%5D-smsc95xx-generaterandom-mac-address-once-not-every-ifup-73702/ I did not test it, but it looks promising. Bruce, can you (or a delegate) pick this one up - or close it as will not fix? Checked https://patchwork.kernel.org/patch/263861/, it's commit f4e8ab7cc4e819011ca6325e54383b3da7a5d130 in mainline. It sounds this commit has been there since 2.6.x. This one is resolved in the 3.0 and 3.2 kernels, so we can mark this as fixed. |