From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: Consistent MAC on Beagleboard xM
Date: Wed, 29 Jun 2011 16:11:20 -0700 [thread overview]
Message-ID: <4E0BB118.4080700@linux.intel.com> (raw)
In-Reply-To: <CC992F09-A620-421C-9AC6-ED807B17F03F@dominion.thruhere.net>
On 06/29/2011 02:19 PM, Koen Kooi wrote:
>
> Op 29 jun 2011, om 23:00 heeft Darren Hart het volgende geschreven:
>
>> 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?
>
> 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
prev parent reply other threads:[~2011-06-29 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 21:00 Consistent MAC on Beagleboard xM Darren Hart
2011-06-29 21:19 ` Koen Kooi
2011-06-29 23:11 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E0BB118.4080700@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox