From: Jonathan Bagg <jbagg@lenbrook.com>
To: backports@vger.kernel.org
Subject: Re: Issue reading kernel config
Date: Wed, 07 Aug 2013 16:33:18 -0400 [thread overview]
Message-ID: <5202AF0E.9010201@lenbrook.com> (raw)
In-Reply-To: <5202A643.8080404@lenbrook.com>
So I had a look at the Kconfig file and realised it isn't a kernel
config. If I add
config BT
def_bool y
under the "# some hacks ..." section, I can enable BT drivers in
backports in the menuconfig. So if a kconfig depends on an external
config, there is no way to feed in a kernel config to backports? you
list external config under "# some hacks ..." section?
Jon
On 13-08-07 03:55 PM, Jonathan Bagg wrote:
> Hello,
>
> I am cross compiling backports successful using "alldefconfig". I
> would like use menuconfig and have conf read in options from my kernel
> instead of the default. (CONFIG_BT is not enabled in the default and
> I want to enable BT drivers in backports). It looks like kconf/conf
> program is loading a kernel config from the root of backports called
> Kconfig. When I replace this file with my kernel config (from
> 2.6.35-3) I get many....
>
> Kconfig:1967: syntax error
> Kconfig:1966: unknown statement "CONFIG_CRC_ITU_T"
> Kconfig:1967: unknown statement "CONFIG_CRC32"
> Kconfig:1971: syntax error
> Kconfig:1970: unknown statement "CONFIG_ZLIB_INFLATE"
> Kconfig:1971: unknown statement "CONFIG_ZLIB_DEFLATE"
> Kconfig:1972: unknown statement "CONFIG_LZO_COMPRESS"
> Kconfig:1973: unknown statement "CONFIG_LZO_DECOMPRESS"
> Kconfig:1974: unknown statement "CONFIG_GENERIC_ALLOCATOR"
> Kconfig:1975: unknown statement "CONFIG_HAS_IOMEM"
> Kconfig:1976: unknown statement "CONFIG_HAS_IOPORT"
> Kconfig:1977: unknown statement "CONFIG_HAS_DMA"
> Kconfig:1978: unknown statement "CONFIG_NLATTR"
> make[1]: *** [menuconfig] Error 1
> make: *** [menuconfig] Error 2
>
> What is the right way to do this? I could add CONFIG_BT=y to the
> default Kconfig file, but that seems hackish.
>
> Jon
>
next prev parent reply other threads:[~2013-08-07 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 6:23 [PATCH 1/8] ath9k: Do a quick scan only when scan_not_start is true Sujith Manoharan
2013-08-01 6:23 ` [PATCH 2/8] ath9k: Use a subroutine to check for short scan Sujith Manoharan
2013-08-01 6:23 ` [PATCH 3/8] ath9k: Add ALT check for cards with GROUP-3 config Sujith Manoharan
2013-08-01 6:23 ` [PATCH 4/8] ath9k: Use a subroutine to try LNA switch Sujith Manoharan
2013-08-01 6:23 ` [PATCH 5/8] ath9k: Use a helper function for checking LNA options Sujith Manoharan
2013-08-01 6:23 ` [PATCH 6/8] ath9k: Simplify checks in quick_scan Sujith Manoharan
2013-08-01 6:23 ` [PATCH 7/8] ath9k: Use a subroutine to calculate ALT ratio Sujith Manoharan
2013-08-01 6:23 ` [PATCH 8/8] ath9k: Add statistics for antenna diversity Sujith Manoharan
2013-08-01 15:27 ` [PATCH v2 " Sujith Manoharan
2013-08-01 16:37 ` cross compile backports? Jonathan Bagg
2013-08-01 17:47 ` Solomon Peachy
2013-08-01 19:03 ` Luis R. Rodriguez
2013-08-01 19:36 ` Solomon Peachy
2013-08-01 19:12 ` cross compile backports with LTIB Jonathan Bagg
2013-08-01 19:17 ` Jonathan Bagg
2013-08-07 19:55 ` Issue reading kernel config Jonathan Bagg
2013-08-07 20:33 ` Jonathan Bagg [this message]
2013-08-08 6:37 ` Johannes Berg
2013-08-08 11:45 ` Jonathan Bagg
2013-08-08 12:16 ` Johannes Berg
2013-08-01 19:44 ` [PATCH v2 8/8] ath9k: Add statistics for antenna diversity John W. Linville
2013-08-01 19:53 ` John W. Linville
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=5202AF0E.9010201@lenbrook.com \
--to=jbagg@lenbrook.com \
--cc=backports@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.