From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] rtl8821au: new package
Date: Mon, 20 Jul 2015 23:30:37 +0200 [thread overview]
Message-ID: <20150720233037.1a9da56a@free-electrons.com> (raw)
In-Reply-To: <CA+h8R2rH2Ne_PUe85wMnEc1a817FVun0m61z+FqCfA3ph5NvMQ@mail.gmail.com>
Christian,
Please do not reply to me directly, keep the list in Cc. Thanks.
On Mon, 20 Jul 2015 20:55:09 +0000, Christian Stewart wrote:
> I didn't see the kernel module infrastructure before, not really sure how I
> missed it. I remember looking closely at the manual.
The kernel module infra is brand new, it was merged like 10 days ago.
> I put it under linux-firmware because I thought that was where all of the
> wifi related drivers should go. But I think you're right that it should be
> separate.
Yes, it's not a firmware per-se.
> The reason why I'm using my version of the driver is because it's based on
> an entirely different wifi driver release from the other repository you've
> linked. Mine is based on v4.3.14_13455.20150212_BTCOEX20150128-51 while
> theirs is based on a version from a couple years ago. Thus mine is actually
> closer to the vendor version, with some fixups.
>
> Is it okay to use this version?
I suppose it's not possible to directly download the vendor version?
If not, then using your Github repo is probably OK. The issue is of
course that in 6-12 months, you'll probably stop caring about this
driver, and no-one will be able to upstream fixes anymore. But I guess
that's the normal life-cycle for out of tree kernel drivers,
unfortunately.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-20 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 23:01 [Buildroot] [PATCH v1 1/1] rtl8821au: new package Christian Stewart
2015-07-18 21:26 ` Thomas Petazzoni
[not found] ` <CA+h8R2rH2Ne_PUe85wMnEc1a817FVun0m61z+FqCfA3ph5NvMQ@mail.gmail.com>
2015-07-20 21:30 ` Thomas Petazzoni [this message]
[not found] ` <CA+h8R2pR_BU7FRm0R8EHKuA7rqgeeRrzBzy1AkvVEuqo04uAwQ@mail.gmail.com>
[not found] ` <20150720233051.6ae1947e@free-electrons.com>
2015-07-20 21:35 ` Christian Stewart
2015-07-20 21:49 ` Yann E. MORIN
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=20150720233037.1a9da56a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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