public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel <damage@rooties.de>
To: linux-kernel@vger.kernel.org
Subject: Re: debug prism wlan
Date: Sun, 13 Aug 2006 11:31:40 +0000	[thread overview]
Message-ID: <200608131131.40493.damage@rooties.de> (raw)
In-Reply-To: <6.1.1.1.2.20060813071741.02ae87e0@192.168.6.12>

Am Sonntag, 13. August 2006 05:20 schrieb Roger While:
> Alistair John wrote:
>  > Daniel wrote:
>  >> Hey, that did it! But now I am a liddle confused. It worked fine
>  >> before. Why does it not work while interface is not up?
>  >
>  > I'm not sure, but I think you've just been lucky.
>  > I've had this problem even before prism54 was merged.
>  > Some in-tree drivers won't upload the firmware until you ifconfig
>  > up them, which obviously means they won't respond adequately
>  > to the wireless extension requests. Maybe a bug?
>
> Nope, no bug. It allows the driver to be built non-modular.
> When non-modular, the resources are not available,
> at boot time, to load the firmware.
>

Hi, I noticed that you can't set the channel _before_ setting an essid. Is 
this behavior correct?

Daniel

  reply	other threads:[~2006-08-13  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  5:20 debug prism wlan Roger While
2006-08-13 11:31 ` Daniel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-13 10:37 Roger While
2006-08-12 21:40 Daniel
2006-08-12 20:15 ` Alistair John Strachan
2006-08-12 22:26   ` Daniel
2006-08-12 20:43     ` Alistair John Strachan
2006-08-12 22:56       ` Daniel
2006-08-12 21:07         ` Alistair John Strachan
2006-08-12 22:49     ` Daniel
2006-08-12 21:06       ` Alistair John Strachan

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=200608131131.40493.damage@rooties.de \
    --to=damage@rooties.de \
    --cc=linux-kernel@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