From: Andrei Gherzan <andrei@gherzan.ro>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [poky] RaspberryPi Layer
Date: Mon, 21 May 2012 12:25:56 +0300 [thread overview]
Message-ID: <4FBA0A24.70704@gherzan.ro> (raw)
In-Reply-To: <4278335.i6izktZTML@helios>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On 05/21/2012 12:19 PM, Paul Eggleton wrote:
> On Monday 21 May 2012 11:47:15 Andrei Gherzan wrote:
>> On Mon, May 21, 2012 at 10:47 AM, Tomas Frydrych wrote:
>>> On 19/05/12 22:51, Andrei Gherzan wrote:
>>>> After an exchange of messages with Richard, Saul and John Willis (he
>>>> already started a layer for oe and did a good job in it) i want to
>>>> announce that i started start a fork from his layer and with Florin
>>>> Sarbu will prepare a layer for RaspberryPi to work upon poky.
>>> Why a fork? This is a bsp layer so it should be sufficiently generic to
>>> work both with Poky and OE, it is really undesirable that there should
>>> be more than one m-rpi layers in circulation.
>> There are issues that cannot be solved with just one layer. A distro is a
>> workaround but still. More about this, rpi layer will be included in yocto
>> project repos as Richard plans so it makes sense to have a yocto specific
>> layer. It could be a discussion here about using a core layer and above
>> that some distro specific layers but in my opinion this would be a little
>> too complicated for this. Right now i use a distro file which inherits poky
>> distro in order to BBMASK some bbappends which we don't have in poky. Clear
>> now?
> Not really, no. I can't believe there is a good reason to have two layers for
> this. Can you please be more clear why we can't just have one?
>
For example parsing libav and rpi-zram-service will fail. We don't have
libav and we don't have systemd yet in poky.
@g
[-- Attachment #2: Type: text/html, Size: 2257 bytes --]
next prev parent reply other threads:[~2012-05-21 9:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 21:51 RaspberryPi Layer Andrei Gherzan
2012-05-19 21:51 ` Andrei Gherzan
2012-05-19 22:09 ` Chris Tapp
2012-05-21 7:47 ` [poky] " Tomas Frydrych
2012-05-21 8:47 ` Andrei Gherzan
2012-05-21 9:19 ` Paul Eggleton
2012-05-21 9:25 ` Andrei Gherzan [this message]
2012-05-21 9:32 ` Paul Eggleton
2012-05-21 15:16 ` John Willis
2012-05-21 15:31 ` Paul Eggleton
2012-05-21 15:34 ` John Willis
2012-05-21 15:41 ` Gary Thomas
2012-05-21 15:45 ` Andrei Gherzan
2012-05-21 16:21 ` Tomas Frydrych
2012-05-21 10:12 ` Tomas Frydrych
2012-05-21 19:59 ` Chris Tapp
2012-05-21 20:08 ` Andrei Gherzan
2012-05-22 19:40 ` Chris Tapp
2012-05-22 19:43 ` Andrei Gherzan
2012-05-22 21:46 ` Khem Raj
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=4FBA0A24.70704@gherzan.ro \
--to=andrei@gherzan.ro \
--cc=paul.eggleton@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.