All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel <damage@rooties.de>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: debug prism wlan
Date: Sat, 12 Aug 2006 22:26:26 +0000	[thread overview]
Message-ID: <200608122226.26516.damage@rooties.de> (raw)
In-Reply-To: <200608122115.08419.s0348365@sms.ed.ac.uk>

Oh, sorry I have forgotten to tell:

drunken init # lspci |grep Prism
00:08.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism 
Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

So I'm using the prism54 driver (CONFIG_PRISM54). My version of wireless-tools 
is 29_pre10 and the version of the used firmware is 1.0.4.3.

BTW: I tried
# modprobe prism54 pc_debug=1

and 

# modprobe prism54 pc_debug=9999999

But it doesn't increased the verbose level.

The firmware upload was successfull (according to dmesg).

Am Samstag, 12. August 2006 20:15 schrieben Sie:
> On Saturday 12 August 2006 22:40, Daniel wrote:
> > Hi,
> > my wlan gives up working somewhere between upgrading to gcc-4.1, changing
> > some kernel options and upgrading to linux-2.8.16-r4.
>
> Hi Daniel,
>
> Which driver does this card use? There's a couple Prism 1/2/2.5 802.11b
> drivers and a Prism54 driver for 802.11g cards. Any ideas?

  reply	other threads:[~2006-08-12 20:26 UTC|newest]

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

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=200608122226.26516.damage@rooties.de \
    --to=damage@rooties.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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.