[Buildroot] [PATCH v2 3/3] imx-usb-loader: new package

[Luca Ceresoli <luca@lucaceresoli.net>]

Dear Thomas,

Thomas Petazzoni wrote:
> Dear Luca Ceresoli,
>
> On Thu, 02 Oct 2014 10:47:44 +0200, Luca Ceresoli wrote:
>
...
>>> 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?

Probably.

I didn't want to create a lot of almost-equal files: the only
difference between the two boards is the .dtb to use. Hence I thought
of a script producing the config file from a template file.

But since there would be only 2 files for now it may be fine as well to
just have the two files.

I'll choose as soon as I start coding.

-- 
Luca