Re: [meta-chip] Yocto on the 9$ computer

[Andrei Gherzan <andrei@gherzan.ro>]

On Sat, Oct 24, 2015 at 09:46:41PM +0100, Alex J Lennon wrote:
>
>
>
>
> Sent from my iPhone
> >> On 24 Oct 2015, at 21:13, Andrei Gherzan <andrei@gherzan.ro> wrote:
> >>
> >>> On Sat, Oct 24, 2015 at 09:58:42PM +0200, Nicolas Aguirre wrote:
> >>> 2015-10-24 19:26 GMT+02:00 Andrei Gherzan <andrei@gherzan.ro>:
> >>> Hi all,
> >>
> >> Hi Andrei,
> >>
> >>> Have a C.H.I.P. 9$ computer? It works with Yocto now.
> >>>
> >>> http://layers.openembedded.org/layerindex/branch/master/layer/meta-chip/
> >> Good job.
> >> IMO it make sense to add C.H.I.P support in meta-sunxi, don't you think ?
> >>
> >> https://github.com/linux-sunxi/meta-sunxi
> >
> > Well. Temporary it is a separate layer. And this is mainly because of the
> > overhead you need for flashing the board. So I do see a benefit in keeping it
> > separately. We will see in time.
> >
> > Thanks for feedback.
>
> Great work Andrei. I have a couple of CHiPs here and was trying to decide whether meta-sunxi would provide what was needed or whether we needed a custom layer.
>
> I've been hugely impressed with what Docker+Resin gives me for application deployment management so I'd like to look at how easy it is to take your Linux/u-boot CHiP support and deploy via Resin.
>
> Are you at the point you have a base OS image for CHiP with Resin support? If not I would be interested in having a look at this with you.
>

We definitely thought about that already. The problem is that we currently rely
on a BTRFS partition for the docker runtime environment. This obviously won't
work on a flash raw device. So if you want to dig into this I can give you some
hints, otherwise we will just tackle it when we will get to it.

Andrei

--
Andrei Gherzan