Re: [Ltib] LTIB for Raspberry Pi

[Mike Goins]

On Wed, Sep 26, 2012 at 7:15 PM, Sean Malloy <address@hidden> wrote:
>>      there will be a RC3 of rpi_boot.tar.gz that contains this license
>>      file and up-to-date /boot code
>>      from https://github.com/raspberrypi/firmware/tree/master/boot.
>
> RC3 of rpi_boot*.diff.gz is available.

Reviewing the patch now and running the build.  Just a few more questions.

"Be sure to run "sync" before removing the card from the reader."

I have found that running "blockdev --flushbufs /dev/[blockdev]" is
much better at flushing out to block devices since sync concerns
itself primarily with file-systems.  I'm not sure if newer versions of
sync do this automatically.  We may consider adding this to the
mksdimage script.

Speaking of which.  The post build script prompts for sudo password.
This is a bit unconventional for ltib (and tougher for some automation
systems, but doable).  Like your note said, probably needs to be moved
to deployment since ltib somehow is capable of doing these types of
operations (not sure how myself, but looking at it now).   It may be
possible to put this operation in the rpi_boot.spec since that is run
as root (and is relatively easy to do).

What is the license on the original toolchain?  I failed to find it
anywhere in the github files we used to create the RPM.   I am sure it
is permissive, but wanted to make sure.

Stuart, is it feasible to keep list member generated toolchains at the
GPP?  Sean, can you find out if the maintainer of the current tools at
github is willing to accept and check in our rpm version of the
toolchain?  This may be the best alternative if not using GPP.



> --
> Sean C. Malloy
> address@hidden
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib