Hi Ian,

On 2 September 2014 03:22, Ian Campbell <i...@hellion.org.uk> wrote:
> On Sun, 2014-08-31 at 21:54 -0700, Simon Glass wrote:
>> Hi,
>>
>> On 30 August 2014 19:44, Ian Campbell <i...@hellion.org.uk> wrote:
>> > On Sat, 2014-08-30 at 13:40 +0400, Matwey V. Kornilov wrote:
>> >> 30.08.2014 04:04, Ian Campbell пишет:
>> >>
>> >> > In the meantime "touch include/config/auto.conf" lets it build (hardly
>> >> > ideal though!)
>> >>
>> >> Hi, I do
>> >>
>> >> make defconfig
>> >> make silentoldconfig
>> >> make tools-only
>> >
>> > Thanks. I feared that would be baking some sort of non-default defconfig
>> > (IYSWIM) stuff into the tools build. Perhaps that worry is unfounded
>> > though.
>>
>> That works,
>
> You mean that "make defconfig" is (now) the recommended way to get
> tools-only to build?

I mean that it builds sandbox, which is the best thing to build.

>
>>  and builds with sandbox_defconfig so that you get full
>> functionality (verified boot).
>
> Not sure what you mean here. Verified in what way? What is booting that
> way, this should only build tools, not something which can boot.
>
> We are using tools-only as part of the Debian packaging, what we are
> trying to build is a usable generic version of mkimage (and potentially
> other tools in the future) which can be placed in a generic u-boot-tools
> package which is separate from the u-boot package(s) which contain(s)
> u-boot binaries.

mkimage has additional support for verified/secure boot, but only if
enabled at build time. It is enabled for sandbox. So if you want full
functionality you should use that build.

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

Reply via email to