netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>, Michael Wu <flamingice@sourmilk.net>,
	netdev@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH wireless-dev] d80211: Don't discriminate against	802.11b drivers
Date: Mon, 15 May 2006 16:01:48 +0200	[thread overview]
Message-ID: <200605151601.49290.mb@bu3sch.de> (raw)
In-Reply-To: <20060515153533.11491649@griffin.suse.cz>

On Monday 15 May 2006 15:35, you wrote:
> [removed some people from Cc: list as this is probably not much
> interesting for them]
>
> On Mon, 15 May 2006 14:04:44 +0200, Johannes Berg wrote:
> > On Mon, 2006-05-15 at 13:37 +0200, Jiri Benc wrote:
> > > bcm43xx does that. If I understand it correctly, bcm43xx driver doesn't
> > > know allowed modes until it loads firmware. And the firmware is not
> > > loaded until the device is opened (they probably have a reason for
> > > this).
> >
> > No, that's not right, the firmware has nothing to do with it. At least
> > not that we know of, so we treat it as all doing the same :)
>
> Hm, so your calls to ieee80211_update_hw are probably unnecessary.

No, We must allocate the ieee80211_hw, before we can attach the board.
But before we attached the board, we don't know what hardware it is.
Sure, this can be worked around by some very ugly hack (It was done
in an early version of the dscape port, because there was no 
ieee80211_update_hw), but I am not very happy to add the hack again.
(I am not sure anymore _what_ we actually did to workaround it. I would
have to look up the SVN repository ;) )

  reply	other threads:[~2006-05-15 14:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05  2:32 [PATCH wireless-dev] d80211: Don't discriminate against 802.11b drivers Michael Wu
2006-05-11 15:54 ` Jiri Benc
2006-05-10 17:31   ` Michael Wu
2006-05-12 10:47     ` Jiri Benc
2006-05-12 20:35       ` Michael Wu
2006-05-15 11:37         ` Jiri Benc
2006-05-15 12:04           ` Johannes Berg
2006-05-15 13:35             ` Jiri Benc
2006-05-15 14:01               ` Michael Buesch [this message]
2006-05-15 14:12                 ` Jiri Benc
2006-05-15 17:19           ` Michael Wu
2006-05-19 18:06             ` John W. Linville
2006-05-19 19:03               ` Michael Wu
2006-05-19 19:22                 ` John W. Linville
2006-05-11 20:41   ` 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=200605151601.49290.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    /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).