From: "\"Andy Green (林安廸)\"" <andy@warmcat.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
s-jan@ti.com, arnd@arndb.de, patches@linaro.org,
tony@atomide.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH 4 0/4] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values
Date: Tue, 10 Jul 2012 20:58:58 +0800 [thread overview]
Message-ID: <4FFC2712.9020208@warmcat.com> (raw)
In-Reply-To: <201207101437.54877.florian@openwrt.org>
On 10/07/12 20:37, the mail apparently from Florian Fainelli included:
Hi -
> Le jeudi 05 juillet 2012 04:44:33, Andy Green a écrit :
>> The following series adds some code to generate legal, locally administered
>> MAC addresses from OMAP4 CPU Die ID fuse data, and then adds a helper at
>> net/ethernet taking care of accepting device path / MAC mapping
>> registrations and running a notifier to enforce the requested MAC when the
>> matching network device turns up.
>
> This looks like something you can solve by user-space entirely. Expose the
That might seem so from a openwrt perspective, where you custom cook the
whole userland thing per-device, but it ain't so from a generic rootfs
perspective.
Why should Ubuntu, Fedora etc stink up their OSes with Panda-specific
workarounds? And Panda is not the only device with this issue.
-Andy
WARNING: multiple messages have this Message-ID (diff)
From: andy@warmcat.com ("Andy Green (林安廸)")
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4 0/4] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values
Date: Tue, 10 Jul 2012 20:58:58 +0800 [thread overview]
Message-ID: <4FFC2712.9020208@warmcat.com> (raw)
In-Reply-To: <201207101437.54877.florian@openwrt.org>
On 10/07/12 20:37, the mail apparently from Florian Fainelli included:
Hi -
> Le jeudi 05 juillet 2012 04:44:33, Andy Green a ?crit :
>> The following series adds some code to generate legal, locally administered
>> MAC addresses from OMAP4 CPU Die ID fuse data, and then adds a helper at
>> net/ethernet taking care of accepting device path / MAC mapping
>> registrations and running a notifier to enforce the requested MAC when the
>> matching network device turns up.
>
> This looks like something you can solve by user-space entirely. Expose the
That might seem so from a openwrt perspective, where you custom cook the
whole userland thing per-device, but it ain't so from a generic rootfs
perspective.
Why should Ubuntu, Fedora etc stink up their OSes with Panda-specific
workarounds? And Panda is not the only device with this issue.
-Andy
next prev parent reply other threads:[~2012-07-10 12:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 2:44 [PATCH 4 0/4] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values Andy Green
2012-07-05 2:44 ` Andy Green
2012-07-05 2:44 ` [PATCH 4 1/4] OMAP: add cpu id register to MAC address helper Andy Green
2012-07-05 2:44 ` Andy Green
2012-07-05 2:44 ` [PATCH 4 2/4] NET ethernet introduce mac_platform helper Andy Green
2012-07-05 2:44 ` Andy Green
2012-07-05 3:12 ` Joe Perches
2012-07-05 3:12 ` Joe Perches
2012-07-05 3:20 ` Andy Green
2012-07-05 3:20 ` Andy Green
2012-07-05 3:25 ` Joe Perches
2012-07-05 3:25 ` Joe Perches
2012-07-06 22:40 ` Ben Hutchings
2012-07-06 22:40 ` Ben Hutchings
2012-07-06 22:40 ` Ben Hutchings
2012-07-05 2:44 ` [PATCH 4 3/4] OMAP4 PANDA register ethernet and wlan for automatic mac allocation Andy Green
2012-07-05 2:44 ` Andy Green
2012-07-05 2:45 ` [PATCH 4 4/4] config test config extending omap2plus with wl12xx etc Andy Green
2012-07-05 2:45 ` Andy Green
2012-07-10 12:37 ` [PATCH 4 0/4] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values Florian Fainelli
2012-07-10 12:37 ` Florian Fainelli
2012-07-10 12:58 ` "Andy Green (林安廸)" [this message]
2012-07-10 12:58 ` "Andy Green (林安廸)"
2012-07-10 13:08 ` Steven Rostedt
2012-07-10 13:08 ` Steven Rostedt
2012-07-10 15:20 ` Alan Cox
2012-07-10 15:20 ` Alan Cox
2012-07-27 7:26 ` arm interrupt handling Qipeng Zha
2012-07-27 7:26 ` Qipeng Zha
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=4FFC2712.9020208@warmcat.com \
--to=andy@warmcat.com \
--cc=arnd@arndb.de \
--cc=florian@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rostedt@goodmis.org \
--cc=s-jan@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.