From: Bastien Nocera <hadess@hadess.net>
To: Hanno Zulla <abos@hanno.de>,
linux-wireless@vger.kernel.org, Jes.Sorensen@redhat.com
Cc: Larry.Finger@lwfinger.net, anthony.wong@canonical.com
Subject: Re: Support of rtl8723bs
Date: Mon, 12 Sep 2016 14:23:51 +0200 [thread overview]
Message-ID: <1473683031.2930.3.camel@hadess.net> (raw)
In-Reply-To: <688574b6-1141-f408-d397-535f1f69999e@hanno.de>
On Mon, 2016-09-12 at 11:20 +0200, Hanno Zulla wrote:
> Hi Jes,
> hello linux-wireless,
>
> I'd like to know more about the current progress of rtl8723bs support
> for Linux.
>
> Googling and reading the mailing list archives found an older vendor
> driver
> https://github.com/hadess/rtl8723bs
This is the canonical location.
> plus patches at
> https://github.com/lwfinger/rtl8723bs
This is an old tree.
> which both aren't ready for Linux according to
> https://github.com/hadess/rtl8723bs/issues/96
>
> According to
> https://github.com/hadess/rtl8723bs/issues/98
>
> there is a newer vendor driver from Realtek at
> https://github.com/anthonywong/rtl8723bs
> which Anthony wants to get ready for inclusion to the Ubuntu kernel.
>
> But after reading
> https://marc.info/?l=linux-wireless&m=146902477024130&w=2
> it appears that even that newer vendor driver isn't ready for Jes's
> work.
The "hadess" driver above is an older vendor driver with 2 years of
cleanups, and lots of code removal:
430 files changed, 81387 insertions(+), 254812 deletions(-)
Anthony's repo is just a dump of a newer version of the driver.
What would be useful would be to compare the newer vendor driver with
the last time the "hadess" driver was rebased
(a2e5bb366f6d6c19dcab6db47b68a944256e8228) and pick out bug fixes.
Anyway, as an owner of such a device, I'd like to help somehow, and
be
> it as a guinea pig to test on my hardware. The newer vendor driver
> crashed on Ubuntu' 4.4 sources and doesn't compile yet on Ubuntu 4.8-
> rc
> sources.
> https://github.com/anthonywong/rtl8723bs/issues/1
I really don't care about the vendor driver. There's no way to track
changes other than through code dumps.
Longer term, it seems likely that improving Jes' driver is the way to
go. At least there's 170k less lines of code to read in the rtl8723bs
driver to get things going.
Cheers
next prev parent reply other threads:[~2016-09-12 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 9:20 Support of rtl8723bs Hanno Zulla
2016-09-12 12:23 ` Bastien Nocera [this message]
2016-09-12 14:27 ` Anthony Wong
2016-09-12 14:47 ` Jes Sorensen
2016-09-12 15:09 ` Larry Finger
2016-09-12 15:48 ` Hanno Zulla
2016-09-12 15:50 ` Bastien Nocera
2016-09-12 16:07 ` Jes Sorensen
2016-09-13 7:47 ` Hanno Zulla
2016-09-13 15:05 ` Larry Finger
2017-01-16 13:09 ` Hanno Zulla
2017-01-16 13:25 ` Jes Sorensen
2017-01-16 17:24 ` Larry Finger
2017-03-29 10:20 ` Hanno Zulla
2017-03-29 15:24 ` Larry Finger
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=1473683031.2930.3.camel@hadess.net \
--to=hadess@hadess.net \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=abos@hanno.de \
--cc=anthony.wong@canonical.com \
--cc=linux-wireless@vger.kernel.org \
/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.