From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de,
linux-wireless <linux-wireless@vger.kernel.org>,
Oncaphillis <oncaphillis@snafu.de>
Subject: Re: [PATCH RFC] ssb: Generic SPROM override for devices without SPROM
Date: Fri, 20 Nov 2009 08:05:39 -0600 [thread overview]
Message-ID: <4B06A233.2070708@lwfinger.net> (raw)
In-Reply-To: <200911201212.19588.mb@bu3sch.de>
On 11/20/2009 05:12 AM, Michael Buesch wrote:
> This patch adds a generic mechanism for overriding the SPROM mechanism
> on devices without SPROM hardware.
>
> There currently is a major problem with this:
> It tries to deduce a MAC address from various hardware parameters. But
> currently it will result in the same MAC address for machines of the same
> type. Does somebody have an idea of some device-instance specific serial
> number or something similar that could be hashed into the MAC?
You might look at the "root=" part of /proc/cmdline. Mine says
"root=/dev/disk/by-id/ata-TOSHIBA_MK2546GSX_18C2P0KCT-part1". That disk serial
number would certainly be unique. Even if it just said "root=/dev/sda1", it
would be repeatable.
Larry
next prev parent reply other threads:[~2009-11-20 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 11:12 [PATCH RFC] ssb: Generic SPROM override for devices without SPROM Michael Buesch
2009-11-20 11:38 ` Florian Fainelli
2009-11-20 11:44 ` Michael Buesch
2009-11-20 14:05 ` Larry Finger [this message]
2009-11-20 14:11 ` Michael Buesch
2009-11-20 14:16 ` Florian Fainelli
2009-11-20 14:51 ` Larry Finger
2009-11-20 17:19 ` Larry Finger
2009-11-20 14:34 ` Stefan Lippers-Hollmann
2009-11-20 14:50 ` Ehud Gavron
2009-11-20 14:55 ` Larry Finger
2009-11-24 8:51 ` Oncaphillis
2009-11-24 10:52 ` Michael Buesch
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=4B06A233.2070708@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=oncaphillis@snafu.de \
/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.