From: "Arend van Spriel" <arend@broadcom.com>
To: "JoSH Lehan" <krellan@gmail.com>
Cc: "Adrian Chadd" <adrian@freebsd.org>,
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: Sun, 12 May 2013 12:34:03 +0200 [thread overview]
Message-ID: <518F701B.2080900@broadcom.com> (raw)
In-Reply-To: <CAJ-VmonOuhBgXa3-LkspaCgAAh8Y9Jxejn-McVourzgE-ajHTw@mail.gmail.com>
On 05/12/2013 02:46 AM, Adrian Chadd wrote:
> Hi,
>
> On 11 May 2013 15:54, JoSH Lehan <krellan@gmail.com> wrote:
>
>> Thanks! So, I'll need to maintain two sets of mac80211/cfg80211
>> modules: one for drivers that were compiled along with the kernel, and
>> another for drivers that were compiled as part of the compat-drivers
>> package.
>
> No, you or the vendor should forward port it to linux-next, then you
> can just pick up the whole driver/framework set from compat-wireless.
That is indeed the approach. So integrate your vendor provided driver
into your local linux-next tree and create you own compat-drivers
package using that tree (see [1]). You have to tinker the framework to
include that driver.
Regards,
Arend
[1]
https://backports.wiki.kernel.org/index.php/Documentation/compat-drivers/hacking
next prev parent reply other threads:[~2013-05-12 10:34 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
2013-05-11 23:21 ` JoSH Lehan
2013-05-12 0:46 ` Adrian Chadd
2013-05-12 10:34 ` Arend van Spriel [this message]
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=518F701B.2080900@broadcom.com \
--to=arend@broadcom.com \
--cc=adrian@freebsd.org \
--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.