linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: "Pavel Roskin" <proski@gnu.org>, Dave <kilroyd@googlemail.com>,
	"Stefanik Gábor" <netrolller.3d@gmail.com>,
	"Bernhard Reiter" <bernhard@intevation.de>
Subject: Re: 802.11 pccard, Agere 0x0156,0x0003?
Date: Thu, 19 Jun 2008 08:55:30 +0200	[thread overview]
Message-ID: <200806190855.30791.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1213833799.5258.13.camel@dv>

> > There is a more recent version of the Agere driver
> > available, which has been patched for 2.6 kernels. See
> > <http://ubuntuforums.org/showthread.php?t=304217>
>
> It's really a low hanging fruit.  The big thing that was
> missing was firmware download for Agere, but Dave implemented
> that.

You mean I can convert the sta_h2.h file from the above link to 
some binary file and let orinoco+Dave's patches load that 
firmware to the card?

I'm asking this because I also have a bunch of Hermes I and 
Hermes II cards, which don't work with the Orinoco driver, but 
with the "brought somewhat up to kernel 2.6" wlags_h2_718.tgz 
driver from the above link. That driver works, but hurts the 
eyes, and now has some problems with 2.6.25, e.g. at unloading 
time.

  reply	other threads:[~2008-06-19  6:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 15:15 802.11 pccard, Agere 0x0156,0x0003? Bernhard Reiter
2008-06-18 15:31 ` Stefanik Gábor
2008-06-18 22:04   ` Dave
2008-06-19  0:03     ` Pavel Roskin
2008-06-19  6:55       ` Holger Schurig [this message]
2008-06-19 17:27         ` Dave
2008-06-19  8:23       ` Bernhard Reiter
2008-06-19  9:19         ` Holger Schurig
2008-06-19 12:44           ` Bernhard Reiter
2008-06-19 13:54             ` Holger Schurig
2008-06-19 17:40         ` Dave
2008-06-20  7:35           ` Bernhard Reiter
2008-06-20  7:37             ` Johannes Berg
2008-06-23 16:12               ` Kalle Valo
2008-06-23 16:53                 ` Dan Williams
2008-06-23 17:01                   ` Kalle Valo

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=200806190855.30791.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=bernhard@intevation.de \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    --cc=proski@gnu.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).