From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] imx-usb-loader: new package
Date: Thu, 2 Oct 2014 11:52:00 +0200 [thread overview]
Message-ID: <20141002115200.2b6486d4@free-electrons.com> (raw)
In-Reply-To: <542D1130.1050508@lucaceresoli.net>
Dear Luca Ceresoli,
On Thu, 02 Oct 2014 10:47:44 +0200, Luca Ceresoli wrote:
> Yes. The only indication in getopt.[hc] is:
>
> License: LGPL
>
> and nothing else. This means LGPL (ant version), it is the list of
> licenses documented on the BR manual.
>
> BTW, the LGPL license is declared in BR for pppd and tslib as well.
Ok.
> > Also: what about having this package enabled by default in the sabresd
> > defconfigs, if it makes sense to have this host tool enabled for those
> > configurations?
>
> My plan is slightly more ambitious indeed. What I have in mind is to:
> 1. enable imx-usb-loader for both SABRESD boards;
> 2. prepare the configuration files that imx_usb_loader needs to boot
> the device;
> 3. document how to boot using imx_usb_loader + the config files.
Sounds like a good plan.
>
> Step 1 is trivial.
>
> For step 2 I'll have generate two files: imx_usb.conf (the top-level
> config file for imx_usb) and mx6_usb_work.conf (different for the two
> SoC variants). The former can be taken as is from the imx_usb_loader
> sources, the latter must be edited as described in Vincent's tutorial
> [1], at section "Prepare your payload and configuration".
>
> I think the best way is to use a post-image script to create these
> files in output/images, except they are not images. Does this sound
> fine?
Yes, it sounds fine. From my point of view output/images is not
necessarily strictly limited to binary images. It can also contain
other files that are useful to run/flash the system on the target.
Though do you really need to generate those files? They look like
pretty much static configuration files, that could be put in
board/freescale/<foo>/, no?
> If step 2 is well done, the actions to boot the device would be as
> simple as:
>
> ./output/host/usr/bin/imx_usb -c output/images
Cool!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-02 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:03 [Buildroot] [PATCH v2 0/3] i.MX6 SABRESD improvements (using a Freescale kernel) Luca Ceresoli
2014-10-01 15:03 ` [Buildroot] [PATCH v2 1/3] freescale/imx6-sabresd: use global patch dir for U-Boot patches Luca Ceresoli
2014-10-01 15:03 ` [Buildroot] [PATCH v2 2/3] freescale/imx6-sabresd: lock down kernel headers to the kernel version Luca Ceresoli
2014-10-01 15:03 ` [Buildroot] [PATCH v2 3/3] imx-usb-loader: new package Luca Ceresoli
2014-10-01 16:16 ` Thomas Petazzoni
2014-10-01 16:55 ` Eric Nelson
2014-10-02 8:47 ` Luca Ceresoli
2014-10-02 9:17 ` Luca Ceresoli
2014-10-02 9:52 ` Thomas Petazzoni [this message]
2014-10-02 11:10 ` Luca Ceresoli
2014-10-02 9:13 ` Vincent Stehlé
2014-10-02 11:43 ` Luca Ceresoli
2014-10-01 17:37 ` [Buildroot] [PATCH v2 0/3] i.MX6 SABRESD improvements (using a Freescale kernel) Thomas Petazzoni
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=20141002115200.2b6486d4@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.