Linux wireless drivers development
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	orinoco-devel <orinoco-devel@lists.sourceforge.net>
Subject: Can we please schedule orinoco_pci for removal?
Date: Fri, 14 Dec 2007 14:11:18 -0500	[thread overview]
Message-ID: <1197659478.1539.23.camel@dv> (raw)

Hello!

Examples of other drivers have convinced me that orinoco_pci should be
removed from the kernel.  It's superseded by hostap_pci.  Those replying
on orinoco_pci should look at hostap_pci now and make sure that it's
working for them.

orinoco_pci supports Prism 2.5/3 chipset only, so the support for other
related chipsets (Agere and Symbol) is useless for that driver.
Considering that all hostap drivers are Prism-only, orinoco_pci and
hostap_pci support exactly the same hardware.

Other backends for Orinoco deal with PCMCIA cards, inserted (or even
soldered) into proper PCMCIA adapters or into some less capable
replacements.  PCI cards are real 32-bit PCI devices, and stand apart to
a certain degree.  I think it would be useful if Orinoco driver
concentrates on supporting 16-bit PCMCIA cards.  That can possibly
include Orinoco USB.  There is still work to be done in that direction.

Let's not turn this discussion into another discussion whether Orinoco
should give up all Prism IDs in all drivers.  It's not as trivial as it
seems to some, as some cards can only be recognized by the firmware
version.  I'm aware of the problem.  It's a different issue.

So, what timeframe for orinoco_pci removal from the kernel would be
reasonable?

-- 
Regards,
Pavel Roskin

                 reply	other threads:[~2007-12-14 19:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1197659478.1539.23.camel@dv \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orinoco-devel@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