From: hadess@hadess.net (Bastien Nocera)
To: linux-arm-kernel@lists.infradead.org
Subject: Staging r8723bs driver for kernel 4.12.0-rc2 on CHIPPro
Date: Thu, 08 Jun 2017 14:39:46 +0200 [thread overview]
Message-ID: <1496925586.11482.20.camel@hadess.net> (raw)
In-Reply-To: <20170608123844.igx7dofpakpcqg4o@flea.home>
On Thu, 2017-06-08 at 14:38 +0200, Maxime Ripard wrote:
> Hi Bastien,
>
> On Thu, Jun 08, 2017 at 02:34:03PM +0200, Bastien Nocera wrote:
> > On Wed, 2017-05-31 at 10:29 -0600, Angus Ainslie wrote:
> > > On 2017-05-24 15:03, Angus Ainslie wrote:
> > > > Hi
> > > >
> > > > Has the realtek rtl8723bs staging driver in kernel 4.12.0-rc2
> > > > been
> > > > tested on the CHIPPro.
> > > >
> > >
> > > This is still an issue with 4.12.0-rc3
> >
> > I only have access to the original CHIP, and the default kernel
> > configuration there didn't have the necessary options for the
> > staging
> > driver to work.
> >
> > I filed a bug and a PR a while ago:
> > https://github.com/NextThingCo/CHIP-linux/issues/33
> > https://github.com/NextThingCo/CHIP-linux/pull/39
> >
> > I haven't looked at it again in a long while due to lack of time,
> > but
> > that might be a good first pass at the problem, before getting onto
> > the
> > CHIP Pro.
>
> This is for the old NTC's 4.4 kernel though. I think Angus is talking
> about a mainline 4.12.
Which I would test on a CHIP before a CHIP Pro ;)
Then again, I don't have a CHIP Pro to test with, so...
next prev parent reply other threads:[~2017-06-08 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 21:03 Staging r8723bs driver for kernel 4.12.0-rc2 on CHIPPro Angus Ainslie
2017-05-31 16:29 ` Angus Ainslie
2017-05-31 18:05 ` Maxime Ripard
2017-06-08 12:34 ` Bastien Nocera
2017-06-08 12:38 ` Maxime Ripard
2017-06-08 12:39 ` Bastien Nocera [this message]
2017-06-08 13:15 ` Angus Ainslie
2017-06-08 13:13 ` Angus Ainslie
2017-06-08 13:23 ` Maxime Ripard
2017-06-08 12:43 ` Angus Ainslie
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=1496925586.11482.20.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-arm-kernel@lists.infradead.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.