From: Marlon Smith <marlon.smith10@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Luca Coelho <luca@coelho.fi>,
backports@vger.kernel.org
Subject: Re: Backports not building configured drivers
Date: Thu, 30 Aug 2018 09:07:46 -0700 [thread overview]
Message-ID: <1535645266.25991.54.camel@gmail.com> (raw)
In-Reply-To: <1535614402.5215.36.camel@sipsolutions.net>
Thanks everyone for the replies. The setting I was missing in the
kernel was that I need to have PCI enabled. I'm not sure why the
backports menuconfig said PCI [=y], since it was not enabled in the
kernel, but once I enabled it backports built the wifi driver
correctly.
Thanks again for the help!
Marlon
On Thu, 2018-08-30 at 09:33 +0200, Johannes Berg wrote:
> On Wed, 2018-08-29 at 13:55 -0700, Marlon Smith wrote:
>
> >
> > Hey Luca, thanks for the reply! The requirements in the backports
> > 4.14
> > menuconfig are listed as follows:
> >
> > Depends on: WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTL_CARDS [=m]
> > &&
> > m && BP_MODULES [=y] && PCI [=y]
> >
> > I can find the symbol WLAN_VENDOR_REALTEK in the backports 4.14
> > menuconfig but not in the 3.14 kernel's menuconfig. Does this mean
> > I
> > can't use the driver with this kernel?
> No, actually the symbol is enabled? See the [=y] above.
>
> The above looks like it is actually enabled though, so something else
> must be going on?
>
> johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2018-08-30 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:01 Backports not building configured drivers Marlon Smith
2018-08-28 4:42 ` Luca Coelho
2018-08-29 20:55 ` Marlon Smith
2018-08-29 21:14 ` Larry Finger
2018-08-30 7:33 ` Johannes Berg
2018-08-30 16:07 ` Marlon Smith [this message]
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=1535645266.25991.54.camel@gmail.com \
--to=marlon.smith10@gmail.com \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=luca@coelho.fi \
/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.