RE: Do defconfigs work for 2.6.32-rc5 mainline kernels?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 

> -----Original Message-----
> From: linux-omap-owner@xxxxxxxxxxxxxxx 
> [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tim Bird
> Sent: Monday, November 02, 2009 12:21 PM
> To: Bill Gatliff
> Cc: linux-omap@xxxxxxxxxxxxxxx
> Subject: Re: Do defconfigs work for 2.6.32-rc5 mainline kernels?
> 
> 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?

Why don't you guys enable Kernel Low level prints and send the logs?

Otherwise its pretty hard to see what's wrong.

Regards,
Sergio
> 
>  -- Tim
> 
> =============================
> Tim Bird
> Architecture Group Chair, CE Linux Forum
> Senior Staff Engineer, Sony Corporation of America
> =============================
> 
> --
> To unsubscribe from this list: send the line "unsubscribe 
> linux-omap" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux