From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] SoCkit support question?
Date: Fri, 21 Feb 2014 12:30:40 +0100 [thread overview]
Message-ID: <20140221123040.4920ad0a@skate> (raw)
In-Reply-To: <201402211124.03017.manningc2@actrix.gen.nz>
Dear Charles Manning,
On Fri, 21 Feb 2014 11:24:02 +1300, Charles Manning wrote:
> I have just sent my second patch for this to the u-boot list. They didn't like
> my last one because it was standalone and not integrated into mkimage. They
> might come back with some formatting stuff, but I think it will be mainlined
> in a day or two.
>
> Once that is in place, it can be patched into the u-boot-socfpga tree and the
> preloader is built and signed as part of a regular u-boot build. It just
> needs a build-root copy step to copy it into output/images. I will be doing
> that today.
In the mean time (until your patch gets accepted, and a new U-Boot
release is made with it), it is still possible to support the SoCkit by
having U-Boot build an unsigned image, and let the user manually use
the Altera provided mkpimage tool to sign it. It just needs to be
documented in board/arrow/sockit/readme.txt, with all the other details
on how to actually set up the board to use the bootloader and kernel
images produced by Buildroot.
Don't wait for perfection. Do something simple that works now, and
improve on top of it progressively :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-21 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <940580837.479152.1392839319094.JavaMail.root@mail>
2014-02-19 19:50 ` [Buildroot] SoCkit support question? Sébastien Bourdelin
2014-02-19 20:34 ` Charles Manning
2014-02-20 9:08 ` Maxime Hadjinlian
2014-02-20 21:30 ` Sebastien Bourdelin
2014-02-20 22:24 ` Charles Manning
2014-02-21 11:30 ` Thomas Petazzoni [this message]
2014-02-21 15:54 ` Sebastien Bourdelin
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=20140221123040.4920ad0a@skate \
--to=thomas.petazzoni@free-electrons.com \
--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