From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: jt@hpl.hp.com, Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wavelan_cs update (Pcmcia backport)
Date: Fri, 11 Jan 2002 15:55:25 -0800 [thread overview]
Message-ID: <20020111155525.A15627@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020111151825.C15515@bougret.hpl.hp.com> <1563806246.1010792978@[195.224.237.69]>
In-Reply-To: <1563806246.1010792978@[195.224.237.69]>; from linux-kernel@alex.org.uk on Fri, Jan 11, 2002 at 11:49:39PM -0000
On Fri, Jan 11, 2002 at 11:49:39PM -0000, Alex Bligh - linux-kernel wrote:
> > I was playing with wavelan_cs in the kernel (converting it to
> > the new Wireless Extensions), and I realised that it doesn't work at
> > all. I had a look at the code and it is so antique that it is scary.
>
> Don't suppose you'd like to backport the non-pcmcia (i.e. true
> PCI, not pcmcia on a PCI minibridge) version too? I will happilly
> test it for you (IBM T23).
>
> --
> Alex Bligh
You are confused. I'm talking here of the wavelan_cs driver
for the old (obsolete) Wavelan hardware (non IEEE). Please check the
Wireless Howto for more details.
For the Wavelan IEEE/Orinoco, the kernel is up-to-date (the
next 2.4.18 should be once Marcelo adds the missing files), and it's
the Pcmcia package that need a backport. For PCI support, the
situation is messy, but we can talk about that off list (or check the
samba archive).
Regards,
Jean
next prev parent reply other threads:[~2002-01-11 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 23:18 Jean Tourrilhes
2002-01-11 23:49 ` Alex Bligh - linux-kernel
2002-01-11 23:55 ` Jean Tourrilhes [this message]
2002-01-13 22:19 ` Joel Jaeggli
2002-01-18 5:07 ` Jeff Garzik
2002-01-18 18:44 ` Jean Tourrilhes
2002-01-18 15:10 ` Bruce Harada
2002-01-18 23:06 ` Keith Owens
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=20020111155525.A15627@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@alex.org.uk \
--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
all inboxes | Powered by JetHome®