meta-genivi-demo layer structure

Changhyeok Bae changhyeok.bae at gmail.com
Mon Mar 7 16:56:30 EST 2016


Hi Rudi

I thought that I joined your yocto lecture of linux foundation in HP(Gram)
4 or 5 years ago. :)
Nice to meet you.

Thanks for your comments.

I really prefer to your suggestion and I already reflected in rasp-dev
branch of my repo.
You saw rasp branch :)

2016-03-08 6:08 GMT+09:00 Streif, Rudolf <rstreif at jaguarlandrover.com>:

> Hi Changhyeok,
>
> Chiming in here a little late, I suppose, and I am not a GDP maintainer
> but have been doing quite some work with the Yocto project.
>
> Thanks for your opinion.
>> I just reflected my github repo(dev branch) about #4 suggestion.
>> Please your comments about this issue.
>>
>> - https://github.com/locust2001/genivi-demo-platform (rasp9-dev branch)
>>   :
>> https://github.com/locust2001/genivi-demo-platform/commit/b6352a3fe46326e5f8d7f99e51a3f6067d859280
>> - https://github.com/locust2001/meta-genivi-demo(rasp-dev branch)
>>   :
>> https://github.com/locust2001/meta-genivi-demo/commit/8fc61a8b18ca46c29f14800f85e3cb26e45497ac
>>
>>
> 4) Re-structure meta-genivi-demo like meta-openembedded
>>   : meta-genivi-demo/meta-genivi-demo
>>   : meta-genivi-demo/meta-raspberrypi-extra
>>   : meta-genivi-demo/meta-intel-extra
>>   -> One meta-genivi-demo repository
>>
>> I think that 4) is the best approach. I looked at your repo setup and
> compared it to who genivi-demo-platform is organized. For each hardware
> platform genivi-demo-platform supports there is a branch. You have that
> with you rasp9 branch, but I would actually call it raspberrypi. Beneath
> genivi-demo-platform you have:
>
> genivi-demo-platform
> |- meta-genivi-demo (submodule)
> |- meta-ivi (submodule)
> |- meta-openembedded (submodule)
> |- meta-qt5 (submodule)
> |- meta-raspberrypi (submodule)
> |- poky (submodule)
> |- .gitignore
> |- .gitmodules
> |- README.md
> |- init.sh
>
> Since you do not want to modify meta-raspberrypi with changes that are
> specific to the GENIVI demo platform and hence cannot be upstreamed, I
> would simply add meta-raspberrypi-gdp as a layer. That's where all the
> adaptations for RPi should go.
>
> I saw recipes-raspberrypi inside of meta-genivi-demo in your Github repo.
> I think the files in there should go into the meta-raspberrypi-gdp:
>
> meta-raspberrypi-gdp
> |- recipes-bsp
> |  |- bootfiles
> |  |  |- rpi-config_git.bbappend
> |  |- recipes-kernel
> |  |  |- linux
> |  |  |  |- linux-raspberrypi
> |  |  |  |- inux-raspberrypi_4.1.bbappend
>
> This would follow the already existing structure the best. At least in my
> opinion.
>
> Cheers,
> Rudi
>
>
>
> --
> *Rudolf J Streif*
> System Architect - Open Source Initiative
> Open Source Technology Centre
>
> *M:* +1.619.631.5383
> *Email:*  rstreif at jaguarlandrover.com
>
>
>
> UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
> US: 1419 NW 14th Ave, Portland, OR 97209
> jaguar.com | landrover.com
> -------------------
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
> Registered in England No: 1672070
>
> This e-mail and any attachments contain confidential information for a
> specific individual and purpose.  The information is private and privileged
> and intended solely for the use of the individual to whom it is addressed.
> If you are not the intended recipient, please e-mail us immediately.  We
> apologise for any inconvenience caused but you are hereby notified that any
> disclosure, copying or distribution or the taking of any action in reliance
> on the information contained herein is strictly prohibited.
>
> This e-mail does not constitute an order for goods or services unless
> accompanied by an official purchase order.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20160308/d1b70392/attachment.html>


More information about the genivi-projects mailing list