Re: Red Pitaya 122-16: kernel reaches init!
Lloyd Parkes <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <ac5804354ec8352854b8eb1a4e5c1f1c255e8e8a.camel@must-have-coffee.gen.nz> |
On Sun, 2024-04-21 at 15:05 -0500, David Young wrote:
>
> db{1}> x/c 0x90186000,4096
> 90186000: init: can't get /dev/console for controlling
> terminal: Operation
> 90186040: not
> supported\015\012\000\000\000\000\377\230\377\377\000\000\0
> 00\000\377\377\377\377\000\000\000\000\377\377\377\377\000\000\000\00
> 0\377\377\3
> 77\377\000\000\000\000\377\377\377\377\000\000\000\000\377\377\377\37
> 7\000\000\0
> . . .
>
> I don't know how this has happened. Maybe there is a bug in the
> early
> console driver?
That's certainly odd and you may be right.
If I've been paying attention (and I might not have been) the early ARM
init code you have enabled does "things" to get early access to the
console.
Maybe try a kernel without VERBOSE_INIT_ARM, EARLYCONS and CONSADDR?
The kernel fetches /chosen/stdout-path from the device tree very early,
so you shouldn't have a problem with the device tree specifying uart0
instead of uart1.
Ngā-mihi,
Lloyd