From: Larry Finger <Larry.Finger@lwfinger.net>
To: JoSH Lehan <krellan@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: Using compat-drivers conflicts with kernel mac80211 and cfg80211
Date: Sat, 11 May 2013 18:10:18 -0500 [thread overview]
Message-ID: <518ECFDA.20208@lwfinger.net> (raw)
In-Reply-To: <518ECC39.9090401@gmail.com>
On 05/11/2013 05:54 PM, JoSH Lehan wrote:
> Yes. It's an embedded system, however, it has an exposed USB port and
> the user is free (within reason) to plug in a USB device. I'm trying to
> add support for as many USB wireless adapters that I can find. For some
> adapters (such as vt6656 and rtl8712), I use the vendor's tarball (which
> compiles directly against the kernel). So, this is why I need to mix
> and match drivers compiled against the kernel's mac80211/cfg80211 with
> drivers compiled against the mac80211/cfg80211 from compat.
>
Neither driver r8712u, which has been in the kernel since 2.6.37, nor the
equivalent vendor driver depends on anything from mac80211 or cfg80211. If it
did, the kernel version would be in the drivers/net/wireless tree rather than in
staging. I suspect the same is true for other wireless drivers from staging,
which includes vt6656.
Larry
next prev parent reply other threads:[~2013-05-11 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 0:52 Using compat-drivers conflicts with kernel mac80211 and cfg80211 JoSH Lehan
2013-05-11 7:35 ` Arend van Spriel
2013-05-11 9:18 ` Hauke Mehrtens
2013-05-11 23:10 ` JoSH Lehan
2013-05-13 4:55 ` Luis R. Rodriguez
2013-05-11 22:54 ` JoSH Lehan
2013-05-11 23:10 ` Larry Finger [this message]
2013-05-11 23:21 ` JoSH Lehan
2013-05-12 0:46 ` Adrian Chadd
2013-05-12 10:34 ` Arend van Spriel
2013-05-13 3:29 ` JoSH Lehan
2013-05-13 3:56 ` JoSH Lehan
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=518ECFDA.20208@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=krellan@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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.