From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: NOTE: hwmod changes merged to linux-omap master for testing
Date: Mon, 04 Oct 2010 08:06:14 -0700 [thread overview]
Message-ID: <8762xi3sm1.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DB90C96B@dbde02.ent.ti.com> (Manjunath Kondaiah G.'s message of "Mon, 4 Oct 2010 13:19:40 +0530")
"G, Manjunath Kondaiah" <manjugk@ti.com> writes:
> Hi Tony,
> With latest merges on master branch with commit ID:
> 0882b1455797b0a104978000a622c3f2412e7cf5 omap: READ CAREFULLY: Fix build after merging in hwmod support for testing
>
> Booting with zoom3 seems to be fine but observed issues with omap4 blaze board.
>
> Looks like multiple warning dumps and finally it crashes after "Freeing init memory" with both NFS and ramdisk file systems.
>
> The complete bootlogs are available at:
> NFS bootlog:
> http://pastebin.com/nrWQ5FGG
In the future, it helps greatly if you state what defconfig you're
using, and specifically what you've changed from the default defconfig.
Looking at this log, you've enabled CPUidle in your config, which is not
(yet) supported for OMAP4 in mainline.
Kevin
> Ramdisk bootlog:
> http://pastebin.com/1F75d2Ew
>
> -Manjunath
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony Lindgren
>> Sent: Saturday, October 02, 2010 6:18 AM
>> To: linux-omap@vger.kernel.org
>> Subject: NOTE: hwmod changes merged to linux-omap master for testing
>>
>> Hi all,
>>
>> So I've finally merged Kevin's hwmod branch into the
>> linux-omap master so we can give it some testing to see if we
>> can merge it to the mainline. Might take few minutes to hit
>> the mirrors.
>>
>> Please note that for omap2plus machines you need to change:
>>
>> - u-boot bootargs for kernel cmdline needs to change with setenv
>> - if you use hardcoded CONFIG_CMDLINE, change it in your .config
>> - /etc/inittab in your omap root file system if using serial console
>>
>> This is because otherwise the serial-omap would be
>> conflicting with the 8250 driver. This should not affect
>> omap1 machines.
>>
>> Please give it a try and report any issues on this list! Now
>> all the machines except ams_delta_defconfig should build.
>> That one is still missing some camera driver changes to build.
>>
>> Regards,
>>
>> Tony
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-omap" in the body of a message to
>> majordomo@vger.kernel.org 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-04 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 0:48 NOTE: hwmod changes merged to linux-omap master for testing Tony Lindgren
2010-10-04 7:49 ` G, Manjunath Kondaiah
2010-10-04 9:20 ` Govindraj
2010-10-04 11:34 ` G, Manjunath Kondaiah
2010-10-04 12:09 ` Ohad Ben-Cohen
2010-10-04 12:13 ` G, Manjunath Kondaiah
2010-10-04 12:13 ` Ohad Ben-Cohen
2010-10-04 12:20 ` G, Manjunath Kondaiah
2010-10-04 12:32 ` Ohad Ben-Cohen
2010-10-04 12:52 ` G, Manjunath Kondaiah
2010-10-04 22:29 ` Ohad Ben-Cohen
2010-10-07 0:04 ` Tony Lindgren
2010-10-07 8:17 ` G, Manjunath Kondaiah
2010-10-04 15:06 ` Kevin Hilman [this message]
2010-10-04 16:46 ` G, Manjunath Kondaiah
2010-10-04 18:26 ` G, Manjunath Kondaiah
2010-10-04 19:34 ` Kevin Hilman
2010-10-05 6:36 ` G, Manjunath Kondaiah
2010-10-05 14:57 ` Kevin Hilman
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=8762xi3sm1.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=tony@atomide.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).