All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Saxena, Rahul" <rahul.saxena@intel.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
Date: Thu, 30 Aug 2012 13:22:49 -0400	[thread overview]
Message-ID: <503FA169.7020805@windriver.com> (raw)
In-Reply-To: <63ECFF2A2302B44093D7CE9E9962C4900332201E@ORSMSX103.amr.corp.intel.com>

On 12-08-30 01:06 AM, Saxena, Rahul wrote:
>
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Bodke, Kishore K
> Sent: Wednesday, August 29, 2012 11:08 AM
> To: Bruce Ashfield; Hart, Darren
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
>
>
>
>> -----Original Message-----
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>> bounces@yoctoproject.org] On Behalf Of Bruce Ashfield
>> Sent: Wednesday, August 29, 2012 10:47 AM
>> To: Hart, Darren
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto
>> 3.0 kernel ?
>>
>> On Tue, Aug 28, 2012 at 3:34 PM, Darren Hart<darren.hart@intel.com>  wrote:
>>> On 08/27/2012 08:18 PM, Bruce Ashfield wrote:
>>>> On 12-08-27 8:14 PM, Saxena, Rahul wrote:
>>>>> Hi,
>>>>>
>>>>> I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky.
>>>>>
>>>>> When I try to boot a image such as core-image-sato, I get kernel
>>>>> panic and errors such as:
>>>>>
>>>>> VFS: Cannot open root device "ram0" or unkown-block(0,0)
>>>>>
>>>>> Please append a correct "root=" boot option; here are the available
>>>>>
>>>>> partitions:
>>>>>
>>>>> VFS: unable to mount root fs on unknown block(0,0)
>>>>>
>>>>> User configuration error - no valid rootfilesystem found
>>>>>
>>>>> I do see that the root file system exists in
>>>>> cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir..
>>>>>
>>>>> I did not see this problem when I uses a earlier commit of the Poky
>>>>> master branch.
>>>>>
>>>>> It seems like something broke with 1.3 M3 branch that prevents a
>>>>> proper build with 3.0 kernel. I do need to build my BSP with 3.0 kernel.
>>>>>
>>>>> (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing
>>>>> does not include testing with the 3.0 kernel)
>>>>>
>>>>> Any suggestions would be most welcome. I do need to build my BSP
>>>>> with the 3.0 kernel.
>>>>
>>>> Hmm. It should work, I booted one not that long ago. Can you force
>>>> qemux86 to prefer the 3.0 kernel and see if that boots ? That would
>>>> at least start to isolate the potential problem areas.
>>>
>>> However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4
>>> and
>> 3.2?
>>
>> For 1.3 the 3 kernel sliding window plan was 3.4, 3.2 and 3.0 with
>> 2.6.37 being voted off the island. Or did you mean 1.4 ? Regardless,
>> anything using 3.0 needs to be updated since it's time is running
>> short! :)
>>
>
> Cedartrail BSP has PVR Graphics drivers which works only with 3.0 Kernel.
>
> Thanks
> Kishore.
>
>
> I am mainly interested in ensuring 3.0 Kernel works with the next Yocto release (i.e. Yocto 1.3)
> since the CedarTrail BSP will work only with 3.0 Kernel due to a graphics driver dependency.
>

And that's all definitely fine. If we are having boot problems with the
board on the kernel that it tags, then opening a defect so we can look into
it is fine, since it is a supported kernel.

Bruce

> We will not port the Cedartrail BSP beyond Yocto 1.3.
>
> Thanks
> Rahul
>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> --
>>> Darren
>>>
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Rahul
>>>>>
>>>>
>>>
>>>
>>> --
>>> Darren Hart
>>> Intel Open Source Technology Center
>>> Yocto Project - Linux Kernel
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2012-08-30 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28  0:14 Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ? Saxena, Rahul
2012-08-28  3:18 ` Bruce Ashfield
2012-08-28 19:34   ` Darren Hart
2012-08-29 17:46     ` Bruce Ashfield
2012-08-29 18:08       ` Bodke, Kishore K
2012-08-30  5:06         ` Saxena, Rahul
2012-08-30 17:22           ` Bruce Ashfield [this message]
2012-08-31 18:06             ` Saxena, Rahul

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=503FA169.7020805@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=darren.hart@intel.com \
    --cc=rahul.saxena@intel.com \
    --cc=yocto@yoctoproject.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.