From: Christoph Hellwig <hch@infradead.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Michael Wu <flamingice@sourmilk.net>, Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org
Subject: Re: [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names
Date: Sat, 5 Aug 2006 12:46:50 +0100 [thread overview]
Message-ID: <20060805114650.GC21135@infradead.org> (raw)
In-Reply-To: <20060801122142.GB29208@tuxdriver.com>
On Tue, Aug 01, 2006 at 08:21:49AM -0400, John W. Linville wrote:
> I don't anticipate the d80211 naming conventions to ever make it out
> of wireless-dev. By the time we are ready to push that stuff upstream,
> we will have cleaned-up our messes.
Yes, absolutely.
> This does raise the question: Should we start taking patches to
> wireless-dev that migrate the current (i.e. ieee80211/softmac) stack
> out of the kernel? This would include (re-)moving the current stack
> code, pointing non-migrated drivers (ipw2[12]00, zd1211rw) at the old
> code, moving drivers out of drivers/net/wireless/d80211 up a level,
> removing the softmac-based version of the bcm43xx driver, etc.
I think you first need to come up with a way to deal with ipw2[12]00,
dealing with that kind of devices is priority number one before the
devicescape stack can go anywhere. Once that is handled all software
MAC drivers in wireless-dev should be migrated to the device-scape based
stack.
After that we're in the right position to deal with last big step of
the merge:
a) deal with the userspace interface issue. Either rever to the single
network device and eth%d name interface (at least for the non-AP case)
so existing userspace won't know about the name underlying stack at
all or alternatively go through the painfull design process for a new
userspace interface. I think the first variant will be a lot easier..
b) do all the small compare and review work. See how different the interface
for software mac devices are for softmac vs dscape. See if any of the
old code should be reintegrated into dcape, port forward dscape API
changes to mainline to make merging more gradually. In the best case
we'd migrate the current mainline code fully to the finally dscape
revisited API so the new code really is a drop in, but I don't expect
that happen, the concepts are just too different. At least we should
try to make the interface diff as small a possible.
Once we're there I'm happy to help out on that step b) as much as I can.
next prev parent reply other threads:[~2006-08-05 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 7:37 [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names Michael Wu
2006-07-31 20:31 ` John W. Linville
2006-07-31 20:51 ` Michael Wu
2006-08-01 9:56 ` Christoph Hellwig
2006-08-01 12:21 ` John W. Linville
2006-08-01 13:58 ` Jiri Benc
2006-08-01 14:07 ` John W. Linville
2006-08-01 14:25 ` Ivo Van Doorn
2006-08-01 17:11 ` John W. Linville
2006-08-01 17:31 ` Ivo van Doorn
2006-08-01 19:13 ` Ulrich Kunitz
2006-08-05 11:46 ` Christoph Hellwig [this message]
2006-08-05 17:30 ` Michael Buesch
2006-08-05 17:47 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 6:02 Michael Wu
2006-07-26 16:32 ` Jiri Benc
2006-07-26 16:43 ` Michael Wu
2006-07-26 16:53 ` Jiri Benc
2006-07-26 17:10 ` Michael Wu
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=20060805114650.GC21135@infradead.org \
--to=hch@infradead.org \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).