RaspberryPi Layer

RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

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.
Until a stable version of this layer we will keep this layer on bitbucket:
https://bitbucket.org/agherzan/meta-raspberrypi.
I don't know if a mailing list is needed but if there are any others who
want to contribute on this, we can adopt meta-fsl-arm's solution of a
google group and use it as a way of communicating.

Waiting for feedback and hope there will be others to come along.

@g

[-- Attachment #2: Type: text/html, Size: 1038 bytes --]

RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

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.
Until a stable version of this layer we will keep this layer on bitbucket:
https://bitbucket.org/agherzan/meta-raspberrypi.
I don't know if a mailing list is needed but if there are any others who
want to contribute on this, we can adopt meta-fsl-arm's solution of a
google group and use it as a way of communicating.

Waiting for feedback and hope there will be others to come along.

@g

[-- Attachment #2: Type: text/html, Size: 1038 bytes --]

Re: RaspberryPi Layer

[Chris Tapp]

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On 19 May 2012, at 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. 
> Until a stable version of this layer we will keep this layer on bitbucket: https://bitbucket.org/agherzan/meta-raspberrypi. 
> I don't know if a mailing list is needed but if there are any others who want to contribute on this, we can adopt meta-fsl-arm's solution of a google group and use it as a way of communicating. 
> 
> Waiting for feedback and hope there will be others to come along. 

Hi Andrei,

I'm interested in this. I've got a board here and have some basic stuff running based on the work John has done.

Graphics is painfully slow at the moment, but this seems to be mainly down to there being no hardware acceleration in the images that have been produced yet. It looks as if directfb (http://directfb.org/) plan to have this running shortly, so that looks like it would be worth keeping an eye on.

Chris Tapp

opensource@keylevel.com
www.keylevel.com




[-- Attachment #2: Type: text/html, Size: 2509 bytes --]

Re: [poky] RaspberryPi Layer

[Tomas Frydrych]

Hi,

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.

> Until a stable version of this layer we will keep this layer on
> bitbucket: https://bitbucket.org/agherzan/meta-raspberrypi. 

Considering that John Willis's work is on github, where a number of
people follow it already, why move this somewhere else? This just makes
it harder for anyone interested in this work to track what is going on.

My suggestion is to set up a github project for this, move John's repo
under that as the master, and then any temporary tweaking for poky and
otherwise can be done branches rather than separate repositories.

> I don't know if a mailing list is needed but if there are any others who
> want to contribute on this, we can adopt meta-fsl-arm's solution of a
> google group and use it as a way of communicating. 

I think mailing list is needed; please do not use a group for this, and
certainly not one that requires a google login. Perhaps Yocto could let
us have a meta-rpi list?

Tomas

Re: [poky] RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 2555 bytes --]

On Mon, May 21, 2012 at 10:47 AM, Tomas Frydrych <
tf+lists.yocto@r-finger.com> wrote:

> Hi,
>
> 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?



> > Until a stable version of this layer we will keep this layer on
> > bitbucket: https://bitbucket.org/agherzan/meta-raspberrypi.
>
> Considering that John Willis's work is on github, where a number of
> people follow it already, why move this somewhere else? This just makes
> it harder for anyone interested in this work to track what is going on.
>
>
I'm not a github user. But this wouldn't be a problem. I find bitbucket a
better place to hold any kind of git repo: it has collaborative options,
you can have private repos (free) and a bunch of other stuff. And after all
it is a git. You can clone it, fetch and pull anywhere on your computer. So
i don't find this a problem.


> My suggestion is to set up a github project for this, move John's repo
> under that as the master, and then any temporary tweaking for poky and
> otherwise can be done branches rather than separate repositories.
>
> > I don't know if a mailing list is needed but if there are any others who
> > want to contribute on this, we can adopt meta-fsl-arm's solution of a
> > google group and use it as a way of communicating.
>
> I think mailing list is needed; please do not use a group for this, and
> certainly not one that requires a google login. Perhaps Yocto could let
> us have a meta-rpi list?
>
>
Richard could tell us about this. If it's possible.

@g

[-- Attachment #2: Type: text/html, Size: 3438 bytes --]

Re: [poky] RaspberryPi Layer

[Paul Eggleton]

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?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [poky] RaspberryPi Layer

[Andrei Gherzan]

[-- 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 --]

Re: [poky] RaspberryPi Layer

[Paul Eggleton]

On Monday 21 May 2012 12:25:56 Andrei Gherzan wrote:
> For example parsing libav and rpi-zram-service will fail. We don't have
> libav and we don't have systemd yet in poky.

OK, sure, that isn't ideal - however meta-ti suffers from this issue as well, 
and they have instructions in the layer README which tell people the BBMASK 
they can use to fix it. Can we not do the same here?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [poky] RaspberryPi Layer

[John Willis]

Hi Paul,

> > For example parsing libav and rpi-zram-service will fail. We don't
> > have libav and we don't have systemd yet in poky.
> 
> OK, sure, that isn't ideal - however meta-ti suffers from this issue as
well,
> and they have instructions in the layer README which tell people the
> BBMASK they can use to fix it. Can we not do the same here?

That had been my plan but I got the impression that was frowned up in the
Yocto environment.
As mentioned before I develop with core OE and Angstrom so to date had not
worried about Yocto specific problems as it is not a distro I use in anger.

If anyone wants to chuck patches over for this that is grand. Or if Andrei
wants to maintain floating patches over my tree, that is also fine, it makes
little odds to me or my current use case.

Regards,

John

Re: [poky] RaspberryPi Layer

[Paul Eggleton]

On Monday 21 May 2012 16:16:47 John Willis wrote:
> > > For example parsing libav and rpi-zram-service will fail. We don't
> > > have libav and we don't have systemd yet in poky.
> > 
> > OK, sure, that isn't ideal - however meta-ti suffers from this issue as
> > well, and they have instructions in the layer README which tell people
> > the BBMASK they can use to fix it. Can we not do the same here?
> 
> That had been my plan but I got the impression that was frowned up in the
> Yocto environment.

Well, IMHO it's suboptimal, but far less so than two separate competing layers 
that ultimately exist for the same purpose.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [poky] RaspberryPi Layer

[John Willis]

Hi Paul,

> > That had been my plan but I got the impression that was frowned up in
> > the Yocto environment.
> 
> Well, IMHO it's suboptimal, but far less so than two separate competing
> layers that ultimately exist for the same purpose.

Pushed a note in the README with suggestions on a suitable Yocto BBMASK.

John

Re: [poky] RaspberryPi Layer

[Gary Thomas]

On 2012-05-21 09:34, John Willis wrote:
> Hi Paul,
>
>>> That had been my plan but I got the impression that was frowned up in
>>> the Yocto environment.
>>
>> Well, IMHO it's suboptimal, but far less so than two separate competing
>> layers that ultimately exist for the same purpose.
>
> Pushed a note in the README with suggestions on a suitable Yocto BBMASK.

However, this note has a typo.  BBMASK must be a proper Python regex.

diff --git a/README b/README
index 6558bdc..e9ff8e6 100644
--- a/README
+++ b/README
@@ -22,7 +22,7 @@ mask few recipes requiring systemd or other recipes not included in your distrib

  You can achieve this by adding something like the following to local.conf:

-BBMASK = "meta-raspberrypi/recipes-multimedia/libav meta-raspberrypi/recipes-core/systemd"
+BBMASK = "meta-raspberrypi/recipes-multimedia/libav|meta-raspberrypi/recipes-core/systemd"

  You can adjust the BBMASK for any .bbappends that your distribution does not contain recipes for.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [poky] RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

Or we can set up a distro file so that we can use it out of the box and in
case ppl want to use custom distros use BBMASK. A pull request was sent
with some other stuff as well.


On Mon, May 21, 2012 at 6:41 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2012-05-21 09:34, John Willis wrote:
>
>> Hi Paul,
>>
>>  That had been my plan but I got the impression that was frowned up in
>>>> the Yocto environment.
>>>>
>>>
>>> Well, IMHO it's suboptimal, but far less so than two separate competing
>>> layers that ultimately exist for the same purpose.
>>>
>>
>> Pushed a note in the README with suggestions on a suitable Yocto BBMASK.
>>
>
> However, this note has a typo.  BBMASK must be a proper Python regex.
>
> diff --git a/README b/README
> index 6558bdc..e9ff8e6 100644
> --- a/README
> +++ b/README
> @@ -22,7 +22,7 @@ mask few recipes requiring systemd or other recipes not
> included in your distrib
>
>  You can achieve this by adding something like the following to local.conf:
>
> -BBMASK = "meta-raspberrypi/recipes-**multimedia/libav
> meta-raspberrypi/recipes-core/**systemd"
> +BBMASK = "meta-raspberrypi/recipes-**multimedia/libav|meta-**
> raspberrypi/recipes-core/**systemd"
>
>  You can adjust the BBMASK for any .bbappends that your distribution does
> not contain recipes for.
>
> --
> ------------------------------**------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------**------------------------------
>
> ______________________________**_________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>

[-- Attachment #2: Type: text/html, Size: 2706 bytes --]

Re: [poky] RaspberryPi Layer

[Tomas Frydrych]

So, I have run into three issues with the meta-raspberrypi layer when
trying use it with Poky:

 * the libav bbappend; this can be BBMASKED on distro level, so that's
not a significant problem,

 * rpi-zram-service: a simple but rather hackish fix is to provide
rpi-zram-service-initd package that provides the same functionality for
sysvinit (not a big task) and then BBMASK it in the distro. But I am
wondering if there is some way that both -systemd and -initd packages
could be generated from the same recipe in a way that would work for
both setups so we can avoid the masking?

 * GCC seems to have issues generating armv6 code; I have run into this
bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47719.

Tomas

Re: [poky] RaspberryPi Layer

[Tomas Frydrych]

Hi,

On 21/05/12 09:47, Andrei Gherzan wrote:
> 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?

This really needs to be a BSP layer, not a distro, so that people can
build a custom distros with it; i.e., the fact that you currently BBMASK
packages in the BSP configuration means it will not be useable as an
independent layer.

>     > Until a stable version of this layer we will keep this layer on
>     > bitbucket: https://bitbucket.org/agherzan/meta-raspberrypi.
> 
>     Considering that John Willis's work is on github, where a number of
>     people follow it already, why move this somewhere else? This just makes
>     it harder for anyone interested in this work to track what is going on.
> 
> 
> I'm not a github user. But this wouldn't be a problem. I find bitbucket
> a better place to hold any kind of git repo: it has collaborative
> options, you can have private repos (free) and a bunch of other stuff.
> And after all it is a git. You can clone it, fetch and pull anywhere on
> your computer. So i don't find this a problem.

It should be easy for people interested in the m-rpi effort to track
what is happening, splitting it over multiple online services does
facilitate that; more so it implicitly turns this into two separate
projects simply because someone wanting to contribute will have to
choose where to send the contributions to.

Tomas

Re: RaspberryPi Layer

[Chris Tapp]

After seeing:

> After an exchange of messages with Richard, Saul and John Willis ... i started start a fork ...

I thought this was now 'the' meta-layer for the RPi. Is that not the case? It really would make sense for everyone to pull in the same direction.

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

Yes it is. Forget that.
We decided to use a single layer for both distros.


On Mon, May 21, 2012 at 10:59 PM, Chris Tapp <opensource@keylevel.com>wrote:

>
> After seeing:
>
> > After an exchange of messages with Richard, Saul and John Willis ... i
> started start a fork ...
>
> I thought this was now 'the' meta-layer for the RPi. Is that not the case?
> It really would make sense for everyone to pull in the same direction.
>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 1248 bytes --]

Re: RaspberryPi Layer

[Chris Tapp]

On 21 May 2012, at 21:08, Andrei Gherzan wrote:

> Yes it is. Forget that. 
> We decided to use a single layer for both distros.

Great. Just to be clear, which one is that?

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: RaspberryPi Layer

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

https://github.com/djwillis/meta-raspberrypi

Cheers!

@g



On Tue, May 22, 2012 at 10:40 PM, Chris Tapp <opensource@keylevel.com>wrote:

> On 21 May 2012, at 21:08, Andrei Gherzan wrote:
>
> > Yes it is. Forget that.
> > We decided to use a single layer for both distros.
>
> Great. Just to be clear, which one is that?
>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 936 bytes --]

Re: RaspberryPi Layer

[Khem Raj]

On Tue, May 22, 2012 at 12:43 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> https://github.com/djwillis/meta-raspberrypi
>

good job in joining hands on this one lets make this layer seamless for all
users of rPI with OE