gnewsense-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnewsense-dev] Yeeloong arrived, let's hack


From: avr
Subject: Re: [Gnewsense-dev] Yeeloong arrived, let's hack
Date: Thu, 5 Feb 2009 22:57:49 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, Feb 05, 2009 at 08:55:37PM +0100, Robert Millan wrote:
>
> Hi!
>
> My Yeeloong arrived today, and I'll get to hacking ASAP.  Please can someone
> give me info in what remaining tasks are there (specially those not currently
> being worked on) so I can pick one?

For Orchid you actually sum them up nicely below.

> Some thoughts:
>
>   - Did someone try building (and using) a D-I netboot image with Yeeloong
>     enabled Linux image?

I think the ubuntu installer/live-image needs a lot of graphical bits and large 
parts of
the gnome desktop, which still need to be compiled. This goal shouldn't be far 
off
apart from missing a kernel.

>   - Did someone build a generic (i.e. with all the blob-free goodies) Linux
>     image?  IIUC the ones we have only have Yeeloong stuff.

no. Someone needs to merge a linux-libre kernel and a lemote kernel. It should't
be all that hard, but I haven't gotten around to this yet.
 
>   - Does the bootloader need any care (e.g. packaging)?  IIUC, it lives in
>     the firmware chip which is not safe to update anyway.  But it seems to
>     provide helper programs.

eventually yes, but since it's a piece of software we formerly couldn't do
anything with we can safely just use the factory installed default until
someone (here or at debian) builds a nice package for people who would
want extra features or an easy start to get hacking on the software.

> There's also the task of pruning the non-free bits from Debian.  Is this
> being done separately?  Do you need help building a list of affected packages?

This doesn't apply to orchid, since it's mostly a straight rebuild from the 
gnewsense repository.
If it was clean there it will be clean recompiled .

        friendly,
        Andreas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]