All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/28] rt2x00: Add debugfs support
Date: Wed, 28 Feb 2007 17:52:36 +0100	[thread overview]
Message-ID: <200702281752.36875.IvDoorn@gmail.com> (raw)
In-Reply-To: <1172680639.5015.39.camel@johannes.berg>

> > Well at the moment the cfg80211/nl80211 updates have had a great impact
> > on our CVS tree. So it is starting to look like we are going to drop our CVS
> > version if we don't find a backwards compatibility for vanilla kernels for it.
> 
> Well, we had to start looking forward somewhere. I wish we'd gotten our
> cfg80211 wext-compat hooks into mainline but unfortunately that isn't
> so.

True, and I was expecting problems like this when I decided to keep supporting
vanilla kernels. But at the moment i am just considering what the best options
for rt2x00 would be.

> > Working the other way around will have a negative (But as mentioned above
> > a probably unescapable) side effect. 90% of our testers use the CVS against
> > vanilla kernels, and I cannot see them swicthing to the wireless-dev tree.
> > So I could switch (it is already under consideration) but it will cost us a lot
> > of testers.. :(
> 
> Intel is providing snapshots for this stuff and I think James is still
> trying to figure out if there's any chance to provide cfg80211 w/o
> patches to mainline, which may just work until critical functionality
> mac80211 is moved over to cfg80211 instead of wext.

I have seen that package, James is as far with backwards compatibility as
we are in rt2x00. But we are apparently hitting against the same problem.
But there is some progress I believe, Robin seems to have managed to
compile cfg80211 now against a 2.6.20 kernel. So we probably need some
research now to add older kernels to the supported list. ;)

Ivo

  reply	other threads:[~2007-02-28 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 14:07 [PATCH 2/28] rt2x00: Add debugfs support Ivo van Doorn
2007-02-28 16:16 ` Johannes Berg
2007-02-28 16:26   ` Ivo van Doorn
2007-02-28 16:20 ` Johannes Berg
2007-02-28 16:32   ` Ivo van Doorn
2007-02-28 16:37     ` Johannes Berg
2007-02-28 16:52       ` Ivo van Doorn [this message]
2007-02-28 16:54         ` Johannes Berg
2007-02-28 17:09           ` Ivo van Doorn
2007-02-28 17:21             ` Robin Cornelius
2007-02-28 17:30               ` Johannes Berg
2007-02-28 20:02               ` Johannes Berg
2007-02-28 20:09                 ` Johannes Berg
2007-02-28 17:16     ` Ivo van Doorn

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=200702281752.36875.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.