From: Tim Bird <tim.bird@am.sony.com>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Do defconfigs work for 2.6.32-rc5 mainline kernels?
Date: Mon, 2 Nov 2009 10:21:20 -0800 [thread overview]
Message-ID: <4AEF2320.8040100@am.sony.com> (raw)
In-Reply-To: <4AEB5CD8.8060603@billgatliff.com>
Bill Gatliff wrote:
> I'm trying to build a kernel for beagleboard, using the defconfig found
> in 2.6.32-rc5 and the 2.6.32-rc5 source code.
>
> Said kernel hangs after the uncompressor, I'm just trying to figure out
> if this is a known issue or not. The defconfig in the linux-omap tree
> does seem to work with the linux-omap source code, FWIW...
Short story:
I found that the omap OSK defconfig is broken in mainline also.
Long story:
I found that the defconfig in the mainline 2.6.32-rc1 kernel
didn't work on an OMAP OSK board. Thinking there was some
problem in the code itself, I bisected from a known working
config on 2.6.29 all the way back up to 2.6.32-rc1. When
I was done I was at the current code base, but with a .config
that had about 650 differences.
I haven't had time to go back and find the individual config
option that changed to break things. I would need some kind
of "config bisect" to find this efficiently.
I didn't think to try the OSK defconfig in the omap tree.
(Silly me, might have saved me some grief. :-)
Is there a maintainer for individual defconfig files?
In other words, if I repair the OSK defconfig, who do
I send it to?
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2009-11-02 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 21:38 Do defconfigs work for 2.6.32-rc5 mainline kernels? Bill Gatliff
2009-11-02 18:21 ` Tim Bird [this message]
2009-11-02 20:33 ` Aguirre Rodriguez, Sergio Alberto
2009-11-02 22:04 ` Tony Lindgren
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=4AEF2320.8040100@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=bgat@billgatliff.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox