All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: yorkliu@sourceforge.net, Dan Williams <dcbw@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: network manager vs. missing firmware
Date: Thu, 15 Feb 2007 10:53:57 -0800	[thread overview]
Message-ID: <45D4AC45.6050903@linux.intel.com> (raw)
In-Reply-To: <43e72e890702131847q3306ef05s8ecb2c5f8d3b5676@mail.gmail.com>

Luis R. Rodriguez wrote:
> On 2/13/07, James Ketrenos <jketreno@linux.intel.com> wrote:
>> Dan Williams wrote:
>>
>> > The simpler, the better I think; but it's complicated.  A sample of
>> > current drivers and when they call request_firmware() from a 2.6.19
>> > kernel:
>> >
>> > on dev->open: atmel, prism54, bcm43xx (softmac)
>> > on dev->init: ipw2100, ipw2200
>>
>> request_firmware is also used during mode changes (ie, BSS to IBSS to
>> MONITOR)
> 
> This is a bit off topic but if that's the case then we should also add
> the check for Master mode and if so check to see if the AP firmware is
> available and switch to on master mode. We'd then need to incorporate
> the ap ipw2200 support on ipw2200
> 
> http://sourceforge.net/projects/ipw2200-ap
> 
> I wanted to try a patch to send along but I cannot find the relevent
> code except the firmware there. Perhaps yorkliu can supply that
> though.

Under the 'Download' link there is v0.3 available -- 
http://sourceforge.net/project/showfiles.php?group_id=149502

I haven't tried it myself.  It hasn't been updated since Sept so 
probably needs some kernel API cleanup.

James

  reply	other threads:[~2007-02-15 20:21 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
2007-02-14  0:36   ` James Ketrenos
2007-02-14  2:47     ` Luis R. Rodriguez
2007-02-15 18:53       ` James Ketrenos [this message]
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=45D4AC45.6050903@linux.intel.com \
    --to=jketreno@linux.intel.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=yorkliu@sourceforge.net \
    /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.