linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: network manager vs. missing firmware
Date: Tue, 13 Feb 2007 15:58:09 -0500	[thread overview]
Message-ID: <1171400289.5329.51.camel@localhost.localdomain> (raw)
In-Reply-To: <43e72e890702131213s715df387wa4bd4d1c66b4a664@mail.gmail.com>

On Tue, 2007-02-13 at 15:13 -0500, Luis R. Rodriguez wrote:
> On 2/13/07, Michael Wu <flamingice@sourmilk.net> wrote:
> > On Tuesday 13 February 2007 14:37, Johannes Berg wrote:
> > > > So this isn't really consistent.  I'm unclear as to why the ipw cards
> > > > need it on init rather than on dev open, but hey, why make things
> > > > easier?
> > >
> > > When is ->init() called anyway? Isn't it when you register the netdev so
> > > it would be on probe?
> > >
> > Yes, ipw2200 does it on probe... but I know it can be pushed off to open. I've
> > done it. However.. I think intersil cards really need firmware to read the
> > eeprom.
> 
> This is correct
> 
> > prism54 currently sets a fake MAC address so they can push it off to
> > open, but I think this is wrong.
> 
> This was suggested by Jean a long time ago after we asked for advice
> on what to do since we couldn't read the MAC before loading the
> firmware. Whatever we decide on we should standardize on it in case
> other new cards end up with same issue. One option was to have the
> probe() fail if no firmware was present but obviously this would force
> you to reload the module/reboot if you then get the firmware. We
> decided to leave the firmware upload on open() to overcome this but
> the problem then was the lack of a MAC address.
> 
> Anyone know if wireless network devices the only ones requiring a
> firmware? If not then we should think of slapping something onto
> net_device. Otherwise we should distinguish the requirement on
> cfg80211_config so userspace tools know WTF is going on and inform the
> user appropriately.

No; others include Apple iSight cameras (the built-in USB variants),
bluetooth devices (usually USB too), Keyspan serial adapters (usually
USB), a bunch of stuff in drivers/media/video/, some non-USB network
adapters, and some adaptec and qlogic sci drivers.

It seems that most USB devices require firmware no matter what type they
are.  Beyond that:

probe: scsi/qla2xxx, net/myri10ge, scsi/aic94xx, net/spidernet
open: serial/icom

Dan



  reply	other threads:[~2007-02-13 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 18:41 network manager vs. missing firmware Johannes Berg
2007-02-13 19:23 ` Dan Williams
2007-02-13 19:37   ` Johannes Berg
2007-02-13 19:43     ` Michael Wu
2007-02-13 20:13       ` Luis R. Rodriguez
2007-02-13 20:58         ` Dan Williams [this message]
2007-02-14  0:36   ` James Ketrenos
2007-02-14  2:47     ` Luis R. Rodriguez
2007-02-15 18:53       ` James Ketrenos
2007-02-14 19:24     ` Johannes Berg

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=1171400289.5329.51.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=flamingice@sourmilk.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).