From: Josh Branning <lovell.joshyyy@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: Root filesystem
Date: Thu, 30 Nov 2017 14:30:00 -0000 [thread overview]
Message-ID: <5A2015E7.10707@gmail.com> (raw)
In-Reply-To: <3314e68ddfb8456697efcbcfdac86afa@hosted3-mb01.itm.host>
On 30/11/17 08:13, Robert Bielik wrote:
> Hi all,
>
> New to the tool! I'm planning to use this for setting up a complete build toolchain for Raspberry Pi 3. This means building f.i. ALSA/GStreamer/LADSPA etc. etc. and installing them in the proper rootfs which will be packaged together with the toolchain.
>
> I suspect this is out of the scope of the ct-ng tool ? Maybe someone has ideas or pointers on how to accomplish this ?
>
> Regards
> /Robert
>
>
>
Hi,
I once did something similar for the olinuxino lime A10.
I compiled uboot and a kernel and used an arch linux arm rootfs.
The scripts can be found as a tar.gz
They are probably out of date, but can be modified and can give a
skeleton for you to work with.
http://www.publicsite.org/J05HYYY/software_downloads/olinuxinolime-archlinux.tar.gz
I'm not quite sure about the bootloader in the pi however, whether or
not it can use uboot. The pi needs a blob to run IIRC.
You may also wish to look at https://github.com/RPi-Distro/Pi-gen which
creates the isos for raspbian from the pi foundation.
Josh
next prev parent reply other threads:[~2017-11-30 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 8:13 Robert Bielik
2017-11-30 8:20 ` Baruch Siach
2017-11-30 8:27 ` Robert Bielik
2017-11-30 14:30 ` Josh Branning [this message]
2017-11-30 15:34 ` Bill Randle
2017-11-30 15:36 ` Robert Bielik
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=5A2015E7.10707@gmail.com \
--to=lovell.joshyyy@gmail.com \
--cc=crossgcc@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).