linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Reiter <bernhard@intevation.de>
To: linux-wireless@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: 802.11 pccard, Agere 0x0156,0x0003?
Date: Wed, 18 Jun 2008 17:15:12 +0200	[thread overview]
Message-ID: <200806181715.20516.bernhard@intevation.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]

[Greg gave me the hint to ask here. Please CC me on relevant replies. No need 
to further include him, unless this should go up on the "DriverNeeded" page 
later I presume.]

Sitting here a  pc card wireless land adapter. 
id 0x0156, 0x0003, which probably makes it an Agere card.
cardctl info says:
"Wireless PC Card Model 0110"

We bought it quite a while ago under the tradename Lancom Airlancer MC-11
from Lancom Systems. 
http://www.lancom-systems.de/AirLancer-MC-11b.117.0.html

Background: We bought it because we thought it has a supported chipset based
on the old orinocco driver. The vendor announces "linux" supported, but this 
turned out to be only a driver for Linux 2.4.x.
Some old stuff (with picture) can be found at: 
ftp://ftp.lancom.de/AirLancer/AirLancer-11/AirLancer-MC-11
this seems to be Free Software under GNU GPLv2 even.

We could not get it to work with 2.6 and searching the web gave us only 
reports that it does not work with kernel 2.6.x.
See http://questier.com/howto.html#Proxim
(the "local copy" links might haver newer source code)

I've grepped the kernel sources (2.6.24) to try to find the id in a driver
or the source code comment "Agere" to see if source code was taken in from 
the 2.4. driver. To no prevail.
Even pages like 
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.802.11b.html
do not help me.

So I cannot really say: is there a driver which should work with this card in 
Linux 2.6.x and just missed the manufacturer id to recognise it?
Where did the old Free Software code go? Was it never ported to 2.6?

Thanks,
Bernhard
[Please CC me on relevant replies.]

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-06-18 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 15:15 Bernhard Reiter [this message]
2008-06-18 15:31 ` 802.11 pccard, Agere 0x0156,0x0003? Stefanik Gábor
2008-06-18 22:04   ` Dave
2008-06-19  0:03     ` Pavel Roskin
2008-06-19  6:55       ` Holger Schurig
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=200806181715.20516.bernhard@intevation.de \
    --to=bernhard@intevation.de \
    --cc=greg@kroah.com \
    --cc=linux-wireless@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).