From: Manuel Estrada Sainz <ranty@debian.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
orinoco-devel@lists.sf.net, jt@hpl.hp.com
Subject: orinoco_usb Request For Comments
Date: Thu, 26 Jun 2003 22:58:11 +0200 [thread overview]
Message-ID: <20030626205811.GA25783@ranty.pantax.net> (raw)
Hello,
As many of you already know, I have been working on a variant of the
standard orinoco driver to support ORiNOCO USB devices.
I now believe that it is stable enough for the kernel, and I would like
to get it integrated in the official kernel tree.
At first I tried convincing David to accept the changes in the standard
orinoco driver but he was (rightfully) skeptic. Then Jean Tourrilhes
opened my eyes, the changes touch carefully crafted locking semantics
and could give trouble (although it has been working well for quite a
while), and suggested adding it as an independent (alternative) driver.
It has happened before with rtl8139/8139too and others, while the new
driver probes it's merits stability conscious people can still use the
standard driver.
I know that there are some issues, this is what I plan to do:
- Beautify the source
- Function renaming for consistency
- Moving code around for structure
- Remove reg_name()/rid_name()?
- Cleanup bridge_or_reg/bridge_read_reg/bridge_write_reg to the
minimum possible.
- Implement my own orinoco_interrupt using
__orinoco_ev_* directly.
- Add '-exp' to all module names and offer them as an
alternative in Kconfig.
- I have renamed a couple of functions so they don't get
mixed with the standard orinoco modules.
Please comment, how much of that or what else needs to be done to get
it in the kernel?
Also suggestions on better ways to do the USB vs. PCMCIA abstraction
would be welcomed, although IMHO that could be polished later.
Oh, and since I am at it, I wouldn't mind cleaning kcompat.h for
inclusion in 2.4 kernels to make driver porting easier. I have also
been working in porting lirc so I could put it all together (the
kcompat.h stuff) for 2.4 inclusion.
The code can be downloaded from
http://alioth.debian.org/download.php/223/orinoco-usb-0.2.1.tar.bz2
Or if you want to look at independent files:
http://orinoco-usb.alioth.debian.org/orinoco-usb-0.2.1/
And for the record, the web page for the project is:
http://orinoco-usb.alioth.debian.org/
BTW, for comparison purposes, it was last merged with standard
orinoco-0.13e.
Have a nice day
Manuel
PS: Sorry for the long message.
--
--- Manuel Estrada Sainz <ranty@debian.org>
<ranty@bigfoot.com>
<ranty@users.sourceforge.net>
------------------------ <manuel.estrada@hispalinux.es> -------------------
Let us have the serenity to accept the things we cannot change, courage to
change the things we can, and wisdom to know the difference.
next reply other threads:[~2003-06-26 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 20:58 Manuel Estrada Sainz [this message]
2003-06-26 21:41 ` Oliver Neukum
2003-06-26 23:09 ` Manuel Estrada Sainz
2003-06-27 8:27 ` Manuel Estrada Sainz
[not found] ` <Pine.LNX.4.53.0306271213350.5135@fachschaft.cup.uni-muenchen.de>
2003-07-02 10:17 ` Manuel Estrada Sainz
2003-07-02 14:02 ` Oliver Neukum
2003-06-26 22:03 ` [Orinoco-devel] " Pavel Roskin
2003-06-26 22:50 ` Manuel Estrada Sainz
2003-06-27 21:49 ` Pavel Roskin
2003-06-27 22:16 ` Manuel Estrada Sainz
2003-06-27 2:55 ` David Gibson
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=20030626205811.GA25783@ranty.pantax.net \
--to=ranty@debian.org \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orinoco-devel@lists.sf.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
all inboxes | Powered by JetHome®