From: David Gibson <hermes@gibson.dropbear.id.au>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org,
orinoco-users@lists.sourceforge.net, dhinds@sonic.net
Subject: Re: [Orinoco-users] [PATCH] orinoco_plx-0.13b backport to kernel 2.2
Date: Mon, 6 Jan 2003 11:09:29 +1100 [thread overview]
Message-ID: <20030106000929.GC18808@zax.zax> (raw)
In-Reply-To: <20030105231921.GA7294@www.kroptech.com>
On Sun, Jan 05, 2003 at 06:19:21PM -0500, Adam Kropelin wrote:
> I've backported David Gibson's orinoco_plx wireless driver to kernel 2.2.
> The port is based on David Hinds's pcmcia-cs package. I've been running
> various versions of this backport for over a year now and it has been
> working well. I've updated it to the latest (testing, beta) version of
> the orinoco_plx driver (0.13b) and the latest version of pcmcia-cs (3.2.3).
>
> The patch comes in two parts. The first part updates the version of
> orinoco, hermes, and orinoco_cs modules in pcmcia-cs-3.2.3 from 0.11b to
> 0.13b. The second part adds the backported orinoco_plx module. After
> applying both patches, configure, build, and install pcmcia-cs as normal
> and you should have an additional orinoco_plx.o module ready to use.
Eck... be aware that the "testing" version, although labelled 0.13b
may not be the final 0.13b version.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2003-01-06 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 23:19 [PATCH] orinoco_plx-0.13b backport to kernel 2.2 Adam Kropelin
2003-01-06 0:09 ` David Gibson [this message]
2003-01-06 0:25 ` [Orinoco-users] " Stephen Evanchik
2003-01-06 0:48 ` Adam Kropelin
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=20030106000929.GC18808@zax.zax \
--to=hermes@gibson.dropbear.id.au \
--cc=akropel1@rochester.rr.com \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=orinoco-users@lists.sourceforge.net \
/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