From: Jiri Benc <jbenc@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Ketrenos <jketreno@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
Simon Barber <simon@devicescape.com>,
Jeff Garzik <jeff@garzik.org>, Patrick McHardy <kaber@trash.net>,
David Kimdon <dwhedon@devicescape.com>,
netdev@vger.kernel.org
Subject: Re: [patch] d80211: use pfifo_qdisc_ops rather than d80211-specific qdisc
Date: Thu, 2 Nov 2006 15:05:50 +0100 [thread overview]
Message-ID: <20061102150550.5c30f704@midnight> (raw)
In-Reply-To: <20061102121657.GA13468@infradead.org>
On Thu, 2 Nov 2006 12:16:57 +0000
Christoph Hellwig <hch@infradead.org> wrote:
> The most important merge requirement is to not break userspace. That means
> proper support of WE (hopefully via cfg80211), and a single ethX network
> device.
Sounds reasonable. Though:
- I don't think ethX is the appropriate name. It's not an ethernet
device and many wireless drivers currently use wlanX name. I think
the current wlanX name is a better choice here.
- Single device is not as easy as it sounds. It would require rather
invasive changes in the networking core or ugly hacks in d80211. I'm
afraid this is something not achievable in a near future with current
number of people working on d80211. But in general, it's doable and
desirable, yes.
> The second most important is proper smp support, or good code
> quality in general. We can't afford to merge buggy code.
I definitely agree here.
> Third most
> important is to make sure it's a full replacment for the current ieee80211
> code - for the softmac cards that's mostly trivial, but the half-hard mac
> old intel cards are hard. That's where intel comes into play because you
> support that hardware _and_ are pushing for d80211. That makes your team
> pretty much volunteer to fix that up in my eyes.
Let's see...
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2006-11-02 14:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 22:04 [patch] d80211: use pfifo_qdisc_ops rather than d80211-specific qdisc David Kimdon
2006-10-25 23:29 ` Patrick McHardy
2006-10-26 1:21 ` Patrick McHardy
2006-10-26 2:38 ` Jeff Garzik
2006-10-26 3:37 ` Simon Barber
2006-10-26 5:04 ` Jeff Garzik
2006-10-26 5:15 ` Simon Barber
2006-11-01 10:28 ` Jiri Benc
2006-11-01 14:20 ` John W. Linville
2006-11-01 18:31 ` James Ketrenos
2006-11-02 0:30 ` Jeff Garzik
2006-11-02 1:48 ` d80211 merge (was Re: [patch] d80211: use pfifo_qdisc_ops rather than d80211-specific qdisc) James Ketrenos
2006-11-02 2:55 ` Jeff Garzik
2006-11-02 8:49 ` cfg80211/nl80211/WE (was: Re: d80211 merge) Johannes Berg
2006-11-02 8:59 ` cfg80211/nl80211/WE Jeff Garzik
2006-11-02 10:56 ` cfg80211/nl80211/WE (was: Re: d80211 merge) Christoph Hellwig
2006-11-02 12:03 ` Johannes Berg
2006-11-02 12:16 ` [patch] d80211: use pfifo_qdisc_ops rather than d80211-specific qdisc Christoph Hellwig
2006-11-02 14:05 ` Jiri Benc [this message]
2006-11-02 14:18 ` Christoph Hellwig
2006-11-02 14:32 ` Johannes Berg
2006-11-02 14:41 ` Jochen Friedrich
2006-11-02 14:45 ` Christoph Hellwig
2006-11-02 15:02 ` Johannes Berg
2006-11-02 16:38 ` Simon Barber
2006-11-02 15:42 ` Jiri Benc
2006-11-02 16:09 ` Sven-Haegar Koch
2006-11-02 18:38 ` Jiri Benc
2006-11-02 20:58 ` Dan Williams
2006-11-02 21:27 ` Simon Barber
2006-11-02 22:48 ` Stephen Hemminger
2006-11-02 23:15 ` Luis R. Rodriguez
2006-11-02 14:22 ` Johannes Berg
2006-11-02 16:33 ` [patch] d80211: use pfifo_qdisc_ops rather thand80211-specific qdisc Simon Barber
2006-11-02 16:43 ` Johannes Berg
2006-11-02 22:34 ` Stephen Hemminger
2006-11-02 22:56 ` Johannes Berg
2006-11-03 19:23 ` [patch] d80211: use pfifo_qdisc_ops rather thand80211-specificqdisc Simon Barber
2006-11-03 19:29 ` Simon Barber
2006-11-03 19:39 ` John W. Linville
2006-11-03 23:07 ` Johannes Berg
2006-11-04 2:20 ` [patch] d80211: use pfifo_qdisc_ops ratherthand80211-specificqdisc Simon Barber
2006-11-02 14:06 ` [patch] d80211: use pfifo_qdisc_ops rather than d80211-specific qdisc John W. Linville
2006-10-26 1:34 ` Simon Barber
2006-10-26 1:49 ` Patrick McHardy
2006-10-26 3:17 ` Simon Barber
2006-10-26 2:04 ` Patrick McHardy
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=20061102150550.5c30f704@midnight \
--to=jbenc@suse.cz \
--cc=dwhedon@devicescape.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=jketreno@linux.intel.com \
--cc=kaber@trash.net \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.com \
/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;
as well as URLs for NNTP newsgroup(s).