Skip to contentSkip to conversation

Consistent MAC on Beagleboard xM

DISCUSSION Darren Hart 2 participants 3 messages Jun 29, 2011

lore
Share & tools
lore
#0 lore raw

We have an open bug for a consistent MAC on the Beagleboard xM on the yocto project bugzilla. I want to track whatever solution you have or plan to take. I didn't see a fix in linux-omap_2.6.39 at a quick scan through the patches. There are two approaches suggested in Comment 3 of the bug:

http://bugzilla.yoctoproject.org/show_bug.cgi?id=1073

They are:
https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/687396
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026240.html

Do you already have plans to address this? If not, do you have any opinion on the proposed solutions in the bug?

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#1 lore raw

Op 29 jun 2011, om 23:00 heeft Darren Hart het volgende geschreven:

Quoted 6 lines

We have an open bug for a consistent MAC on the Beagleboard xM on the yocto project bugzilla. I want to track whatever solution you have or plan to take. I didn't see a fix in linux-omap_2.6.39 at a quick scan through the patches. There are two approaches suggested in Comment 3 of the bug:

Quoted 8 lines

http://bugzilla.yoctoproject.org/show_bug.cgi?id=1073

They are:
https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/687396
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026240.html

Do you already have plans to address this? If not, do you have any opinion on the proposed solutions in the bug?

I'd like to use the die-ID for the mac, but the proposed patch by the linaro folks is just wrong in the way it is done, I don't want to add 40 lines of code to my boardfiles just for the mac address *and* need to hardcode usb topology as well.

#2 lore raw
Quoted 17 lines · Koen Kooi

Op 29 jun 2011, om 23:00 heeft Darren Hart het volgende geschreven:

Quoted 14 lines

We have an open bug for a consistent MAC on the Beagleboard xM on the yocto project bugzilla. I want to track whatever solution you have or plan to take. I didn't see a fix in linux-omap_2.6.39 at a quick scan through the patches. There are two approaches suggested in Comment 3 of the bug:

http://bugzilla.yoctoproject.org/show_bug.cgi?id=1073

They are:
https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/687396
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026240.html

Do you already have plans to address this? If not, do you have any

Quoted 6 lines
Quoted 1 line

opinion on the proposed solutions in the bug?

I'd like to use the die-ID for the mac, but the proposed patch by the linaro folks is just wrong in the way it is done, I don't want to add 40 lines of code to my boardfiles just for the mac address *and* need to hardcode usb topology as well.

Seems like a combination of the two approaches would be ideal. Enable user-setting of the mac address and then have the boardfile update it using the die-ID?

I'll mark this bug as WaitForUpstream.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel