From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Mihai Lindner <mihaix.lindner@linux.intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
Development list for the linux-yocto repositories
<linux-yocto@yoctoproject.org>,
yocto@yoctoproject.org
Subject: Re: [PATCH 0/1] [linux-yocto-3.0] boot-live.cfg: enable BLK_DEV_INITRD in kernel
Date: Wed, 19 Sep 2012 15:01:36 -0400 [thread overview]
Message-ID: <505A1690.60007@windriver.com> (raw)
In-Reply-To: <5059EB19.9070600@linux.intel.com>
On 12-09-19 11:56 AM, Mihai Lindner wrote:
> On 2012-09-19 18:43, Bruce Ashfield wrote:
>> On 12-09-18 10:46 AM, Mihai Lindner wrote:
>>> On 2012-09-18 17:23, Tom Zanussi wrote:
>>>> On Tue, 2012-09-18 at 16:58 +0300, Mihai Lindner wrote:
>>>>> On 2012-09-18 16:49, Tom Zanussi wrote:
>>>>>> On Tue, 2012-09-18 at 08:21 -0400, Bruce Ashfield wrote:
>>>>>>> On 12-09-18 01:59 AM, Mihai Lindner wrote:
>>>>>>>> Please pull into linux-yocto-3.0, meta.
>>>>>>>>
>>>>>>>
>>>>>>> Adding linux-yocto, Darren and Tom.
>>>>>>>
>>>>>>> This looks fine to me, and we should consider it for all the repositories,
>>>>>>> not just 3.0.
>>>>>>>
>>>>>>> Tom/Darren. Any side effects you can think of for this change ?
>>>>>>>
>>>>>>
>>>>>> No, but shouldn't it already be there, inherited from base.cfg?
>>>>>
>>>>> For cedartrail, at least, standard.cfg is used.
>>>>>
>>>>
>>>> And standard inherits from base, so it should be turned on. Somehow
>>>> it's getting turned off in cedartrail...
>>>
>>> Yes, it the final .config file is turned off. Solved it by setting it in boot-live.
>>> --Mihai
>>
>> To follow up on this, is someone taking a closer look at this config
>> to see if we can get a root cause for that option being disabled for
>> this board ?
>>
>> I won't be able to poke at it myself for another day or so.
>>
>> Bruce
>>
> I'm still digging on this, trying to figure out what cfg files are included / omitted by `configme` and why.
> base.cfg is not included, nor stanadrd.cfg it seems.
> The list of included cfg files is way to short.
That likely means the BSP .scc file is missing and update (i.e. does
it still have scc_leaf?) and the tools aren't finding it and
auto-generating something to get you up and running.
I just checked the meta branch here, and it looks to be updated, but
if you look at your build's linux source dir, what's in meta/top_tgt ?
Bruce
>
> --Mihai
>>>
>>>>
>>>> Tom
>>>>
>>>>> --Mihai
>>>>>
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>>> Bruce
>>>>>>>
>>>>>>>> Added BLK_DEV_INITRD in boot-live.cfg for linux-yocto-3.0, meta branch.
>>>>>>>> Cedartrail (at least) cannot boot live from ISO image due to
>>>>>>>> BLK_DEV_INITRD missing:
>>>>>>>> "VFS: Cannot open root device "ram0" or unkown-block(0,0)"
>>>>>>>> Should fix #3050
>>>>>>>>
>>>>>>>> [YOCTO #3050]
>>>>>>>>
>>>>>>>> Signed-off-by: Mihai Lindner<mihaix.lindner@linux.intel.com>
>>>>>>>> ---
>>>>>>>>
>>>>>>>> The following changes since commit bf5ee4945ee6d748e6abe16356f2357f76b5e2f0:
>>>>>>>>
>>>>>>>> meta: rename virto.scc to virtio.scc (2012-08-18 22:09:35 -0400)
>>>>>>>>
>>>>>>>> are available in the git repository at:
>>>>>>>> git://git.yoctoproject.org/poky-contrib mihai/linux-yocto-3.0/meta
>>>>>>>>
>>>>>>>> Mihai Lindner (1):
>>>>>>>> boot-live.cfg: enable BLK_DEV_INITRD in kernel
>>>>>>>>
>>>>>>>> meta/cfg/kernel-cache/cfg/boot-live.cfg | 2 ++
>>>>>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>>>>>>
>>>>>>>> Mihai Lindner (1):
>>>>>>>> boot-live.cfg: enable BLK_DEV_INITRD in kernel
>>>>>>>>
>>>>>>>> meta/cfg/kernel-cache/cfg/boot-live.cfg | 2 ++
>>>>>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
next prev parent reply other threads:[~2012-09-19 19:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 5:59 [PATCH 0/1] [linux-yocto-3.0] boot-live.cfg: enable BLK_DEV_INITRD in kernel Mihai Lindner
2012-09-18 6:00 ` [PATCH 1/1] " Mihai Lindner
2012-09-18 12:21 ` [PATCH 0/1] " Bruce Ashfield
2012-09-18 13:49 ` Tom Zanussi
2012-09-18 13:58 ` Mihai Lindner
2012-09-18 14:18 ` Bruce Ashfield
2012-09-18 14:23 ` Tom Zanussi
2012-09-18 14:46 ` Mihai Lindner
2012-09-19 15:43 ` Bruce Ashfield
2012-09-19 15:56 ` Mihai Lindner
2012-09-19 19:01 ` Bruce Ashfield [this message]
2012-09-19 19:39 ` Mihai Lindner
2012-09-19 20:22 ` Bruce Ashfield
2012-09-19 20:32 ` [linux-yocto] " Bruce Ashfield
2012-09-19 20:54 ` Mihai Lindner
2012-09-19 21:55 ` Brian Lloyd
2012-09-19 23:56 ` Bruce Ashfield
2012-09-20 2:38 ` Tom Zanussi
2012-09-20 10:03 ` Mihai Lindner
2012-09-20 16:26 ` Saxena, Rahul
2012-09-18 14:17 ` Bruce Ashfield
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=505A1690.60007@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=linux-yocto@yoctoproject.org \
--cc=mihaix.lindner@linux.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.