All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH RFC] ssb: Generic SPROM override for devices without SPROM
Date: Fri, 20 Nov 2009 11:19:23 -0600	[thread overview]
Message-ID: <4B06CF9B.4040201@lwfinger.net> (raw)
In-Reply-To: <200911201511.11042.mb@bu3sch.de>

On 11/20/2009 08:11 AM, Michael Buesch wrote:
> 
> I think we probably have to drop this patch and instead do a mechanism that
> fetches the sprom from userspace, if the card doesn't have one. This way we
> can have a script in userspace that generates the image based on the PCI ID
> information and just randomizes the MAC address once. The firmware loading
> mechanism would be useful for that.
> In case of an embedded device with the MAC in the nvram, the kernel can still
> override the mac address provided by userspace.
> 

Your patch may be OK. You can get the serial number for the system from
/sys/class/dmi/id/product_serial or the UUID from
/sys/class/dmi/id/product_uuid. Either would work as the initialization for the
hash.

Larry


  parent reply	other threads:[~2009-11-20 17:19 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
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 [this message]
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=4B06CF9B.4040201@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.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.