From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Daniel Schultze <kinglag@gmail.com>
Cc: backports@vger.kernel.org
Subject: Re: menuconfig
Date: Tue, 10 Dec 2013 10:39:43 +0100 [thread overview]
Message-ID: <20131210093943.GA16978@cerro.do-not-panic.com> (raw)
In-Reply-To: <CAEsx0Y_RwZSks_EqBYY7XxUgiRaX4qP-yrSK4Lx4Mbdi1iqNtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
On Wed, Dec 04, 2013 at 03:12:55PM -0800, Daniel Schultze wrote:
> Hello Developers,
>
> I'm trying to use backports for its updated Bluetooth drivers on
> Kernel 2.6.31. When I make menu config in LTIB the line for Bluetooth
> support does not appear, however when I make menuconfig for the host
> the line for Bluetooth appears,
I am unfamiliar with LTIB and its unclear what you mean by running
'in LTIB' and then 'for the host'. I take it LTIB lets you package
of kernel and by 'in LTIB' you mean for the target kernel /
architecture. By 'for the host' I take it you mean -- on the local
build machine, not the target kernel. If I deciphered your issue
then be sure to read this documentation:
https://backports.wiki.kernel.org/index.php/Documentation#Cross_compiling
Also since you are using LTIB and if you succeed it seems worthwhile
if you can add an LTIB section to the documentation unless the existing
documentation already suffices, but it seems there is a section already
for LTIB:
https://backports.wiki.kernel.org/index.php/Documentation#Cross_compile_with_Freescale.27s_LTIB
Please cross check against that.
> I'm using the same source archive from
> backports-3.13-rc2-1 and I also tried backports-3.11.8-1 with the same
> result. What should I check to make the Bluetooth line appear?
In general if you don't see the entry it means your target kernel's
configuration does not meet the requirements needed to enable the
backported driver / feature. Check its dependencies just as you
would for a normal kernel.
Luis
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-10 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:12 menuconfig Daniel Schultze
2013-12-05 7:58 ` menuconfig Nikita N.
2013-12-10 9:39 ` Luis R. Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 9:41 menuconfig Miloš Soukup
2003-02-02 21:04 menuconfig b_adlakha
2003-02-02 21:14 ` menuconfig John Bradford
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=20131210093943.GA16978@cerro.do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=backports@vger.kernel.org \
--cc=kinglag@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 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.