From: Andy Green <andy@warmcat.com> To: Arnd Bergmann <arnd@arndb.de> Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, patches@linaro.org, nicolas.pitre@linaro.org, x0132446@ti.com, s-jan@ti.com, tony@atomide.com Subject: Re: [RFC PATCH 1/2] OMAP2+: add cpu id register to MAC address helper Date: Fri, 25 Mar 2011 12:08:59 +0000 [thread overview] Message-ID: <4D8C85DB.6060001@linaro.org> (raw) In-Reply-To: <201103251249.32578.arnd@arndb.de> On 03/25/2011 11:49 AM, Somebody in the thread at some point said: > On Thursday 24 March 2011, Andy Green wrote: >> Introduce a generic helper function that can set a MAC address using >> data from the OMAP unique CPU ID register. >> >> For comparison purposes this produces a MAC address of >> >> 2e:40:70:f0:12:06 >> >> for the ethernet device on my Panda. >> >> >> Note that this patch requires the fix patch for CPU ID register >> indexes previously posted to linux-omap, otherwise the CPU ID is >> misread on Panda by the existing function to do it. This patch >> is already on linux-omap. >> >> "OMAP2+:Common CPU DIE ID reading code reads wrong registers for OMAP4430" >> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=b235e007831dbf57710e59cd4a120e2f374eecb9 >> >> Signed-off-by: Andy Green<andy.green@linaro.org> > > Acked-by: Arnd Bergmann<arnd@arndb.de> Thanks. > TI folks: While this is a working solution, I still think it would > be good to get an officially sanctioned method that allows the creation > of a IEEE 802 MAC address in a range assigned to TI instead of using > an address from the locally administered range. > > Is that something that can be done? Having a proper MAC from IEEE assigned for each interface is of course ideal. But even if that happened today though, on Panda there is no "board identity storage" to put the reserved MAC addresses in to bind it to the physical board. If you try to manage them on SD Card, you have the problem of dealing with correct MAC addresses needing putting there again every time it is nuked. So it doesn't in itself help in the Panda case. David Anders mentioned yesterday that for next OMAP board, he probably puts a general board identity EEPROM where one could stash MACs. This kind of API can be extended to query the EEPROM at device-register-time and fetch the MAC instead of compute it. So I think we go in a reasonable direction even when it is possible to get assigned MACs. -Andy
WARNING: multiple messages have this Message-ID (diff)
From: andy@warmcat.com (Andy Green) To: linux-arm-kernel@lists.infradead.org Subject: [RFC PATCH 1/2] OMAP2+: add cpu id register to MAC address helper Date: Fri, 25 Mar 2011 12:08:59 +0000 [thread overview] Message-ID: <4D8C85DB.6060001@linaro.org> (raw) In-Reply-To: <201103251249.32578.arnd@arndb.de> On 03/25/2011 11:49 AM, Somebody in the thread at some point said: > On Thursday 24 March 2011, Andy Green wrote: >> Introduce a generic helper function that can set a MAC address using >> data from the OMAP unique CPU ID register. >> >> For comparison purposes this produces a MAC address of >> >> 2e:40:70:f0:12:06 >> >> for the ethernet device on my Panda. >> >> >> Note that this patch requires the fix patch for CPU ID register >> indexes previously posted to linux-omap, otherwise the CPU ID is >> misread on Panda by the existing function to do it. This patch >> is already on linux-omap. >> >> "OMAP2+:Common CPU DIE ID reading code reads wrong registers for OMAP4430" >> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=b235e007831dbf57710e59cd4a120e2f374eecb9 >> >> Signed-off-by: Andy Green<andy.green@linaro.org> > > Acked-by: Arnd Bergmann<arnd@arndb.de> Thanks. > TI folks: While this is a working solution, I still think it would > be good to get an officially sanctioned method that allows the creation > of a IEEE 802 MAC address in a range assigned to TI instead of using > an address from the locally administered range. > > Is that something that can be done? Having a proper MAC from IEEE assigned for each interface is of course ideal. But even if that happened today though, on Panda there is no "board identity storage" to put the reserved MAC addresses in to bind it to the physical board. If you try to manage them on SD Card, you have the problem of dealing with correct MAC addresses needing putting there again every time it is nuked. So it doesn't in itself help in the Panda case. David Anders mentioned yesterday that for next OMAP board, he probably puts a general board identity EEPROM where one could stash MACs. This kind of API can be extended to query the EEPROM at device-register-time and fetch the MAC instead of compute it. So I think we go in a reasonable direction even when it is possible to get assigned MACs. -Andy
next prev parent reply other threads:[~2011-03-25 12:09 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-24 21:27 [RFC PATCH 0/2] OMAP2+: PANDA: Provide unique-ish MAC addresses for Ethernet and WLAN interfaces Andy Green 2011-03-24 21:27 ` Andy Green 2011-03-24 21:27 ` [RFC PATCH 1/2] OMAP2+: add cpu id register to MAC address helper Andy Green 2011-03-24 21:27 ` Andy Green 2011-03-25 11:49 ` Arnd Bergmann 2011-03-25 11:49 ` Arnd Bergmann 2011-03-25 12:08 ` Andy Green [this message] 2011-03-25 12:08 ` Andy Green 2011-03-25 13:24 ` Arnd Bergmann 2011-03-25 13:24 ` Arnd Bergmann 2011-03-25 13:34 ` Andy Green 2011-03-25 13:34 ` Andy Green 2011-03-25 14:50 ` Arnd Bergmann 2011-03-25 14:50 ` Arnd Bergmann 2011-03-25 15:00 ` Andy Green 2011-03-25 15:00 ` Andy Green 2011-03-24 21:27 ` [RFC PATCH 2/2] OMAP2+: PANDA: Fix up random or missing MAC addresses for eth0 and wlan0 Andy Green 2011-03-24 21:27 ` Andy Green 2011-03-25 7:39 ` Hema Kalliguddi 2011-03-25 7:39 ` Hema Kalliguddi 2011-03-25 20:13 ` Jason Kridner 2011-03-25 20:13 ` Jason Kridner 2011-03-25 20:20 ` Arnd Bergmann 2011-03-25 20:20 ` Arnd Bergmann 2011-03-25 20:23 ` Nicolas Pitre 2011-03-25 20:23 ` Nicolas Pitre 2011-03-28 12:54 ` Jason Kridner 2011-03-28 12:54 ` Jason Kridner 2011-03-25 20:30 ` Andy Green 2011-03-25 20:30 ` Andy Green 2011-03-25 11:39 ` Arnd Bergmann 2011-03-25 11:39 ` Arnd Bergmann 2012-06-28 14:18 ` [RFC PATCH 0/2] OMAP2+: PANDA: Provide unique-ish MAC addresses for Ethernet and WLAN interfaces Arnd Bergmann 2012-06-28 14:18 ` Arnd Bergmann 2012-06-28 14:45 ` Steven Rostedt 2012-06-28 14:45 ` Steven Rostedt 2012-06-28 14:49 ` "Andy Green (林安廸)" 2012-06-28 14:49 ` "Andy Green (林安廸)"
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=4D8C85DB.6060001@linaro.org \ --to=andy@warmcat.com \ --cc=andy.green@linaro.org \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=nicolas.pitre@linaro.org \ --cc=patches@linaro.org \ --cc=s-jan@ti.com \ --cc=tony@atomide.com \ --cc=x0132446@ti.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: linkBe 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.