From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] RPi
Date: Wed, 21 May 2014 20:04:35 +0200 [thread overview]
Message-ID: <20140521180435.GA3556@free.fr> (raw)
In-Reply-To: <1826939078.15041392.1400673931165.JavaMail.root@openwide.fr>
Pierre, All,
(He! The same usual suspects! ;-) )
On 2014-05-21 14:05 +0200, Pierre Ficheux spake thusly:
> I did some work on BR around Raspberry Pi platform:
>
> - adding a post-image script for RP SD-card image generation (adapted
> from Yocto RPi recipe)
> - adding BR support for Adafruit touchscreen ->
> https://www.adafruit.com/products/1601
>
> I don't know if it could help, but I can build patches.
For the RPi script, I have to admit I'm a bit sceptic. We usually
document, as much as we can, the preparation of media for the boards
(you can see the one for the RPi in boards/raspberrypi/readme) but we
usually do not provide such scripts.
The only board we're currently doing it for, is the cubieboard, and it
IMHO has quite a few shortcomings:
- requires being root
- uses host-tools without enabling them in the defconfig
- makes some heavy assumptions on the layout (generated files and
medium)
- does not handle all failure modes
- is (a bit) convoluted
Also, I'm a bit warry at providing such a root-requiring script, as it
is so easy to bork things on an unsuspecting user's machine. I for one
would not run such a script to begin with.
I highly prefer we provide a good documentation on how to generate basic
media for a board, and redirect the user to the upstream documentation
(if it exists.)
We've tried to have a generic infrastructure that would generate images
for any board, without any hard-coded layout or the likes), but it turns
to not be so easy. Such an infra would have to cover all comon cases,
but also weird corner-cases, where the layout is not simply a collection
of partitions laid out on some media (think initramfs with part of the
VFS mounted from a block device, it's not easy.)
Others may disagree on the above, so please provide your script, so we
can see and decide on actual code. ;-)
As for the touchscreen support, that would be very interesting, indeed!
Please send your patch! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-05-21 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <123137298.15041034.1400673767940.JavaMail.root@openwide.fr>
2014-05-21 12:05 ` [Buildroot] RPi Pierre Ficheux
2014-05-21 18:04 ` Yann E. MORIN [this message]
2014-05-21 20:59 ` Thomas Petazzoni
2014-05-22 7:01 ` Pierre Ficheux
2014-05-23 9:33 ` Alvaro Gamez
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=20140521180435.GA3556@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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