From: TJ <linux@tjworld.net>
To: Greg KH <greg@kroah.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Casual J. Programmer" <casualprogrammer@googlemail.com>
Subject: Re: Building two (external) modules from the same sources
Date: Wed, 01 Oct 2008 23:27:16 +0100 [thread overview]
Message-ID: <1222900036.25554.21.camel@hephaestion> (raw)
In-Reply-To: <20081001200548.GA30009@kroah.com>
On Wed, 2008-10-01 at 13:05 -0700, Greg KH wrote:
> Hm, I'll look at the code and see if I see anything obvious.
>
> > If someone could offer (link to) hermes-1/2 programming manual ...
>
> That would probably help out a lot :)
Unfortunately the changes in the corporate history have always confused
the issue of locating the old documentation.
As I understand it, the chipset(s) were originally developed at Lucent
around 1999-ish. In 2000 the division responsible became a subsidiary
called Agere Systems. In 2002 it was spun-off as a separate business. In
April 2007 it was bought by LSI Corporation, and by the end of 2007 had
lost its separate existence, along with its web-site and the developer
resources it provided.
The Wayback Machine has working links to the product data-sheets and the
original driver packages:
http://web.archive.org/web/20031202185415/www.agere.com/client/wlan.html
http://web.archive.org/web/20060330013615/http://www.agere.com/mobility/wireless_lan_drivers.html
There is another source of confusion - the actual chip-sets used.
Under the name WaveLAN/IEEE there was a pre-802.11b chip-set, as well as
the later WaveLAN Hermes I (1/one) and II (2/two) which are 802.11b
compatible.
The orinoco_cs drivers support the Hermes I chip-set, at least for WEP,
but as I recall, not for WPA/WPA2.
With Andrey's modifications the wlags49 driver supports WPA but not WPA2
- at least not in my tests.
The only technical documentation I can find, and I'm not sure it will be
completely applicable to the 802.11b Hermes chip-sets, is the 1999
Lucent Technologies/Bell Labs Innovations document:
"DRAFT Software Interface Specification for Wireless Connection
Interface for WaveLAN/IEEE (HCF-light)"
which is available (for now) from a Berkeley graduate student's site:
http://bwrc.eecs.berkeley.edu/People/Grad_Students/jbeutel/wavelan_s0005-11-light.htm
The HCF information might be pretty close to what is used in the HCF by
the Hermes wlags49 MSF.
TJ.
P.S. Andrey: Your mail-provider (mail.ru) is blocking my emails to you.
prev parent reply other threads:[~2008-10-01 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 5:49 Andrey Borzenkov
2008-10-01 3:19 ` Greg KH
2008-10-01 10:13 ` Andrey Borzenkov
[not found] ` <1222879229.17264.4.camel@hephaestion>
2008-10-01 20:00 ` Agere Hermes source-code: copyright situation Greg KH
2008-10-01 23:00 ` Dave
2008-10-02 2:37 ` Andrey Borzenkov
2008-10-02 17:44 ` Dave
2008-10-02 20:00 ` Greg KH
2008-10-02 20:31 ` Dan Williams
2008-10-02 20:37 ` Greg KH
2008-10-02 21:28 ` Dan Williams
2008-10-01 20:05 ` Building two (external) modules from the same sources Greg KH
2008-10-01 22:27 ` TJ [this message]
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=1222900036.25554.21.camel@hephaestion \
--to=linux@tjworld.net \
--cc=arvidjaar@mail.ru \
--cc=casualprogrammer@googlemail.com \
--cc=greg@kroah.com \
--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
Powered by JetHome