Hi Simon,

On Sat, Aug 8, 2015 at 3:26 AM, Simon Glass <s...@chromium.org> wrote:
> Hi Bin,
>
> On 7 August 2015 at 03:28, Bin Meng <bmeng...@gmail.com> wrote:
>> Currently the microcode-tool writes microcode into a data block as
>> well as the device tree properties which represents the first 48
>> bytes in the microcode data. Now we change the tool to only write
>> the microcode without device tree stuff so that multiple microcode
>> data blocks can be included in a single property.
>>
>> Signed-off-by: Bin Meng <bmeng...@gmail.com>
>> ---
>>
>>  tools/microcode-tool.py | 23 ++++++++++++-----------
>>  1 file changed, 12 insertions(+), 11 deletions(-)
>
> I would rather than we use a tool to pack the microcode together (e.g.
> ifdtool) rather than changing the source data. I realise that the FSP
> requires this packing, but I quite dislike the approach of making the
> source files fit the object files.
>

Could you roughly describe how you want to do using ifdtool? Is the
microcode source still from dtb?

> If you like I can take a look at adding this feature to ifdtool.
>

Regards,
Bin
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to