On 2012-09-19 22:01, Bruce Ashfield wrote:
> 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
> 
In meta/top_tgt i have:

/home/mihai/cedartrail/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git5+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+1e79e03d115ed177882ab53909a4f3555e434833-r4.1/linux/meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-standard.scc


I've also hit an error, after more verbose runs of ./cedartrail-standard in 
meta/cfg/scratch/obj/:

./0-cedartrail-standard-897c5c055888aca397b3ab0d7be9e6fa.sco: line 17: 
standard_5b57715386592f694588063dd3ec6ebb: command not found

After this the scripts stops.

Mihai

> 
>>
>> --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.lind...@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(-)
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
> 
> 
> 


-- 
Mihai Lindner
Yocto Project
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to