From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/rtl8821au: switch upstream to abperiasamy
Date: Sat, 23 Jul 2016 15:13:52 +0200 [thread overview]
Message-ID: <20160723151352.77eea94b@free-electrons.com> (raw)
In-Reply-To: <1469220888-2215-1-git-send-email-christian@paral.in>
Hello,
On Fri, 22 Jul 2016 13:54:48 -0700, Christian Stewart wrote:
> Switching to the very active and well maintained rtl8821au
> fork at github.com/abperiasamy/rtl8812AU_8821AU_linux.
Is it really more active and maintained? This new github in fact has a
lot less recent commits that the current github we're using. So it
isn't really clear that this new github is a better "upstream". What
makes you believe it is a better upstream?
Also, what about the firmware? If it's no longer part of this new
upstream project, how can people get the firmware? Is it part of
linux-firmware?
Not your fault, but it would be so much better if those people
submitted such drivers to the staging tree of the official Linux
kernel. This way, instead of having multiple separate efforts to
cleanup/fix such drivers, there would be a single place.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-23 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 20:54 [Buildroot] [PATCH 1/1] package/rtl8821au: switch upstream to abperiasamy Christian Stewart
2016-07-23 13:13 ` Thomas Petazzoni [this message]
2016-07-23 17:50 ` Christian Stewart
2016-07-23 20:16 ` Thomas Petazzoni
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=20160723151352.77eea94b@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