On 22/10/2021 17:09, Tom Rini wrote:
On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
On Fri, 22 Oct 2021 12:09:19 +0200
Heinrich Schuchardt wrote:
On 10/21/21 15:00, Marek Behún wrote:
BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
platform in Kconfig?
> > >> I also have been doing some packaging of u-boot for GNU Guix, where I
> > >> suspect the stance wouldn't be as willing to accept such a compromise...
> > >>
> > >> So... I would *love* an option to be able to build a board-only config
> > >> without any of the tools;
> > >
> > > Why is this
On Fri, Oct 22, 2021 at 12:46:59PM -0700, Vagrant Cascadian wrote:
> On 2021-10-22, Andre Przywara wrote:
> > On Fri, 22 Oct 2021 09:47:35 -0700
> > Vagrant Cascadian wrote:
> >> On 2021-10-22, Tom Rini wrote:
> >> > On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
> >> >> On
On 2021-10-22, Andre Przywara wrote:
> On Fri, 22 Oct 2021 09:47:35 -0700
> Vagrant Cascadian wrote:
>> On 2021-10-22, Tom Rini wrote:
>> > On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
>> >> On Fri, 22 Oct 2021 11:09:27 -0400
>> >> Tom Rini wrote:
>>
>> >> > On Fri, Oct
On Fri, 22 Oct 2021 09:47:35 -0700
Vagrant Cascadian wrote:
Hi,
> On 2021-10-22, Tom Rini wrote:
> > On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
> >> On Fri, 22 Oct 2021 11:09:27 -0400
> >> Tom Rini wrote:
>
> >> > On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún
On Friday 22 October 2021 09:47:35 Vagrant Cascadian wrote:
> do some boards use board-specific tools as part of their build processes?
Lot of boards are using mkimage for generating final U-Boot binary.
Prior U-Boot 2021.10 all 32-bit mvebu boards used own specific version
of mkimage to
On 2021-10-22, Tom Rini wrote:
> On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
>> On Fri, 22 Oct 2021 11:09:27 -0400
>> Tom Rini wrote:
>> > On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
>> > > On Fri, 22 Oct 2021 12:09:19 +0200
>> > > Heinrich Schuchardt wrote:
On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
> On Fri, 22 Oct 2021 11:09:27 -0400
> Tom Rini wrote:
>
> Hi,
>
> > On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
> > > On Fri, 22 Oct 2021 12:09:19 +0200
> > > Heinrich Schuchardt wrote:
> > >
> > > > On
On Fri, 22 Oct 2021 11:09:27 -0400
Tom Rini wrote:
Hi,
> On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
> > On Fri, 22 Oct 2021 12:09:19 +0200
> > Heinrich Schuchardt wrote:
> >
> > > On 10/21/21 15:00, Marek Behún wrote:
> > > > BTW, wouldn't it be enough to simply imply
On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
> On Fri, 22 Oct 2021 12:09:19 +0200
> Heinrich Schuchardt wrote:
>
> > On 10/21/21 15:00, Marek Behún wrote:
> > > BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
> > > platform in Kconfig?
> > >
> >
> > We
On Fri, 22 Oct 2021 12:09:19 +0200
Heinrich Schuchardt wrote:
> On 10/21/21 15:00, Marek Behún wrote:
> > BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
> > platform in Kconfig?
> >
>
> We should only use 'imply' for suggested settings and never for hard
>
On 10/21/21 15:00, Marek Behún wrote:
BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
platform in Kconfig?
We should only use 'imply' for suggested settings and never for hard
requirements. TOOLS_LIBCRYPTO already defaults to 'Y'. So implying it
for mvebu would be
On 10/21/21 8:00 AM, Marek Behún wrote:
> BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
> platform in Kconfig?
No, that would not do anything. For example:
config ARMADA_32BIT
imply TOOLS_LIBCRYPTO
is equivalent to:
config TOOLS_LIBCRYPTO
On Thursday 21 October 2021 15:00:48 Marek Behún wrote:
> BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
> platform in Kconfig?
FYI https://lore.kernel.org/u-boot/20211021093304.25399-1-p...@kernel.org/
(forgot to CC)
BTW, wouldn't it be enough to simply imply TOOLS_LIBCRYPTO for mvebu
platform in Kconfig?
Hi Samuel,
On Wed, 20 Oct 2021 09:14:11 -0500
Samuel Holland wrote:
> Andre is correct. No version of this patch makes *any* change to *any*
> in-tree defconfig build, because TOOLS_LIBCRYPTO=y in all defconfigs.
> Even if I was to accept your assertion that it hides a possible error on
>
On 10/20/21 8:47 AM, Pali Rohár wrote:
> On Wednesday 20 October 2021 14:29:02 Andre Przywara wrote:
>> On Wed, 20 Oct 2021 09:29:25 +0200
>> Pali Rohár wrote:
>>
>> Hi,
>>
>>> On Tuesday 19 October 2021 21:44:51 Samuel Holland wrote:
Some image types (kwbimage and mxsimage) always depend on
On Wednesday 20 October 2021 14:29:02 Andre Przywara wrote:
> On Wed, 20 Oct 2021 09:29:25 +0200
> Pali Rohár wrote:
>
> Hi,
>
> > On Tuesday 19 October 2021 21:44:51 Samuel Holland wrote:
> > > Some image types (kwbimage and mxsimage) always depend on OpenSSL, so
> > > they can only be
On Wed, 20 Oct 2021 09:29:25 +0200
Pali Rohár wrote:
Hi,
> On Tuesday 19 October 2021 21:44:51 Samuel Holland wrote:
> > Some image types (kwbimage and mxsimage) always depend on OpenSSL, so
> > they can only be included in mkimage when TOOLS_LIBCRYPTO is selected.
> > Use Makefile logic to
On Tuesday 19 October 2021 21:44:51 Samuel Holland wrote:
> Some image types (kwbimage and mxsimage) always depend on OpenSSL, so
> they can only be included in mkimage when TOOLS_LIBCRYPTO is selected.
> Use Makefile logic to conditionally link the files.
>
> Signed-off-by: Samuel Holland
NAK.
Some image types (kwbimage and mxsimage) always depend on OpenSSL, so
they can only be included in mkimage when TOOLS_LIBCRYPTO is selected.
Use Makefile logic to conditionally link the files.
Signed-off-by: Samuel Holland
---
Changes in v4:
- Do not select TOOLS_LIBCRYPTO anywhere
Changes in
21 matches
Mail list logo
