From: Larry Finger <Larry.Finger@lwfinger.net>
To: Marlon Smith <marlon.smith10@gmail.com>,
Luca Coelho <luca@coelho.fi>,
backports@vger.kernel.org
Subject: Re: Backports not building configured drivers
Date: Wed, 29 Aug 2018 16:14:11 -0500 [thread overview]
Message-ID: <f1692edb-a6c4-a155-e067-9f83ac5a7e3f@lwfinger.net> (raw)
In-Reply-To: <1535576146.25991.52.camel@gmail.com>
On 08/29/2018 03:55 PM, Marlon Smith wrote:
> On Tue, 2018-08-28 at 07:42 +0300, Luca Coelho wrote:
>> On Mon, 2018-08-27 at 15:01 -0700, Marlon Smith wrote:
>>>
>>> Hi everyone,
>> Hi Marlon,
>>>>>
>>> I'm using backports 4.14 to build for a custom kernel 3.14. That
>>> kernel includes the RT2800 wifi driver, and if I configure
>>> backports
>>> with menuconfig to build a newer version of that driver it works
>>> perfectly. However, if I configure backports to build the RTL8821
>>> driver, which my kernel otherwise does not include, the driver
>>> never
>>> gets built and backports shows it as not selected the next time I
>>> run
>>> menuconfig.
>>>
>>> Is this expected behaviour? Is there something I can do to force
>>> this
>>> driver to build?
>> This probably means that your 3.14 kernel doesn't have some of the
>> dependencies needed by the RTL8821 driver from 4.14. Check the list
>> of
>> dependencies for the driver and make sure they are included in your
>> 3.14 kernel.
>>> --
>> Luca.
>
> 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?
> --
Marlon,
That symbol postdates kernel 3.14. I have no idea if the backports code will
run, or even build, in kernels that old, but I think it would be safe for you to
edit the symbol WLAN_VENDOR_REALTEK out of that "depends on" line in the
configuration menu. At least, that will get you to the next problem. :)
Larry
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-08-30 1:12 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 [this message]
2018-08-30 7:33 ` Johannes Berg
2018-08-30 16:07 ` Marlon Smith
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=f1692edb-a6c4-a155-e067-9f83ac5a7e3f@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=backports@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=marlon.smith10@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).