Am Dienstag, 25. April 2017, 02:08:48 CEST schrieb Syrone Wong:
> try `make kernel_menuconfig` and select the corresponding one.
Thats how it has to be done now. However I claim that the new one should be
the default, and teh right way is to have people using old bootloaders do the
hard way.
Howe
try `make kernel_menuconfig` and select the corresponding one.
Best Regards,
Syrone Wong
On Mon, Apr 24, 2017 at 11:18 PM, Josua Mayer wrote:
> Am Montag, 24. April 2017, 02:37:48 CEST schrieb Syrone Wong:
>> You may want to enable CONFIG_DEBUG_MVEBU_UART0_ALTERNATE
> Yes, this is the one. But
Am Montag, 24. April 2017, 02:37:48 CEST schrieb Syrone Wong:
> You may want to enable CONFIG_DEBUG_MVEBU_UART0_ALTERNATE
Yes, this is the one. But it is not visible from the Lede menuconfig. The
problem I was trying to point out is that in the kernel-config this is what
should be selected when s
You may want to enable CONFIG_DEBUG_MVEBU_UART0_ALTERNATE or
CONFIG_DEBUG_MVEBU_UART1_ALTERNATE if early printk is being enabled.
Best Regards,
Syrone Wong
On Mon, Apr 24, 2017 at 3:39 AM, Josua Mayer wrote:
> Hi everybody,
>
> I noticed a serious problem with a Clearfog build that enables
> C
Hi everybody,
I noticed a serious problem with a Clearfog build that enables
CONFIG_KERNEL_EARLY_PRINTK=y.
In short: after Loading Kernel, the serial console stays completely
silent, and apparently the board does *not* boot.
This came as a serious surprise to me.
Turns out the reason for this is
