>-----Original Message-----
>From: Chris Tapp [mailto:opensou...@keylevel.com]
>Sent: Monday, October 08, 2012 1:03 PM
>To: Bodke, Kishore K
>Cc: Bruce Ashfield; yocto@yoctoproject.org Project
>Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in
>the
>kernel
>
>On 8 Oct 2012, at 17:35, Bodke, Kishore K wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>> boun...@yoctoproject.org] On Behalf Of Chris Tapp
>>> Sent: Monday, October 08, 2012 12:59 AM
>>> To: Bruce Ashfield
>>> Cc: yocto@yoctoproject.org Project
>>> Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs
>>> in
>the
>>> kernel
>>>
>>> On 7 Oct 2012, at 22:41, Bruce Ashfield wrote:
>>>
>>>> On Sun, Oct 7, 2012 at 6:08 PM, Chris Tapp <opensou...@keylevel.com>
>>> wrote:
>>>>> On 7 Oct 2012, at 03:00, Saxena, Rahul wrote:
>>>>>
>>>>>> Try adding the unionfs feature (below) to your kernel:
>>>>>>
>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-
>>> 3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta
>>>>>>
>>>>>> create a file my_cedartrail.scc with following line:
>>>>>> include features/unionfs/unionfs.scc
>>>>>>
>>>>>> put this file in a dir linux-yocto, the dir being created in
>>>>>>
>>>>>> meta-cedartrail/recipes-kernel/linux
>>>>>>
>>>>>> add following line in meta-cedartrail/recipes-kernel/Linux/linux-
>>> yocto_3.0.bbappend
>>>>>>
>>>>>> SRC_URI +="file://my_cedartrail.scc"
>>>>>
>>>>> Thanks - I thought just running 'menuconfig' would allow me to enable it
>>> (for a quick test).
>>>>>
>>>>> However, this still doesn't seem to be working. I can see that
>>> 'my_cedartrail.scc' gets fetched in to the build area, but I still don't see
>>> CONFIG_UNION_FS if I run 'menuconfig'. There is also no 'unionfs' folder in
>>> fs/ of the build tree.
>>>>>
>>>>> Also, if I specify an invalid feature (e.g. feature2/unionfs/unionfs.scc)
>I'm
>>> not seeing any diagnostic.
>>>>
>>>> unionfs was never merged to the 3.0 kernel, I re-added it to the
>>> development
>>>> trees for 3.2 and the 3.4 kernel (aufs for the 3.6 tree at the moment). The
>>> meta
>>>> data is carried forward from the older kernels as a placeholder and is
>>>> documented
>>>> in the .scc file itself:
>>>>
>>>> -----------------------
>>>> kconf non-hardware unionfs.cfg
>>>>
>>>> # commented pending update to a newer version ported to 2.6.35+
>>>> # patch unionfs-2.5.4-integration.patch
>>>> -----------------------
>>>>
>>>> So to get unionfs in the 3.0 kernel, we'd need a port .. but since
>>>> we've moved on
>>>> quite a bit past 3.0, I don't know of any pending ports myself.
>>>
>>> Thanks Bruce.
>>>
>>> I guess I need to ask the Intel guys if there are any plans to move
>>> Cedartrail
>on
>>> from 3.0 ?
>>
>> If the interest is to have unionfs, you can still get it from 3.2 or 3.4
>> Kernel.
>>
>> But the downside is you will be missing the PVR Graphics and will be falling
>back to the
>> basic vesa graphics mode.
>
>Tricky. One of the reasons for specifying Cedartrail was the accelerated
>graphics. However, I've got code running without acceleration and it looks like
>it should be fast enough to do what I need without it.
>
>> PVR graphics has support only for 3.0 kernel only, so we had only put the
>> 3.0
>kernel recipe in the meta-intel.
>>
>> We do not have plans to port PVR graphics to 3.4 kernel.
>
>That's a pity, as this platform has a very good level of performance. I guess
>I'll
>have to be patient and wait for Ivy Bridge graphics ;-)
>
>> We can update the Cedartrail BSP to have 3.2 and 3.4 kernel but it will be
>vesa graphics support only.
>
>How much work would this take? It looks like there is no unification FS support
>in 3.0 that I could use instead, but this is only for a low-volume project and
>I
>wouldn't like to think it was using resource that could be deployed more
>effectively else where.
>
>Thanks for your input on this - looks like I may need to revise my deployment
>strategy for this project ;-)
>
For denzil, try with this by creating a new file in
meta-cedartrail/recipes-kernel/linux/linux-yocto_3.2.bbappend.
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_cedartrail-nopvr =
"git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
KMACHINE_cedartrail-nopvr = "cedartrail"
KBRANCH_cedartrail-nopvr = "yocto/standard/cedartrail"
KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_cedartrail-nopvr ?=
"8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c"
SRCREV_meta_pn-linux-yocto_cedartrail-nopvr ?=
"486f7aec824b4127e91ef53228823e996b3696f0"
Add these below lines to meta-cedartrail/conf/machine/cedartrail-nopvr.conf
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
PREFERRED_VERSION_linux-yocto ?= "3.2%"
Add MACHINE = "cedartrail-nopvr" to your local.conf and build.
Ofcourse you should be adding your unionfs related stuff by some means either
by menuconfig or by creating .scc file.
Thanks
Kishore.
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
