Skip to contentSkip to conversation

x86: Setup early console as early as possible

PATCH Bodo Eggert 2 participants 2 messages Jul 12, 2010 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 8 lines · H. Peter Anvin
Quoted 2 lines · Yinghai Lu

earlycon=uart8250 or console=uart8250 should be better than earlyprintk. because it is shared between different archs already.

console= is crap, because it makes the user keep track of items they should not have to deal with directly (unless they want to override the defaults), i.e. the specific I/O ports used by the serial ports.

Why does console= require these parameters, if earlyprintk does not?

IMO you should fix console= to not need these parameters unless they cannot be guessed (in which case earlyprintk cannot guess them, either).

¢¢

#6 lore raw
Quoted 6 lines · Bodo Eggert
Quoted 4 lines · H. Peter Anvin
Quoted 2 lines · Yinghai Lu

earlycon=uart8250 or console=uart8250 should be better than earlyprintk. because it is shared between different archs already.

Quoted 9 lines
Quoted 3 lines

console= is crap, because it makes the user keep track of items they should not have to deal with directly (unless they want to override the defaults), i.e. the specific I/O ports used by the serial ports.

Why does console= require these parameters, if earlyprintk does not?

IMO you should fix console= to not need these parameters unless they cannot be guessed (in which case earlyprintk cannot guess them, either).

earlycon is basically a low-level interface where you can steer everything. This is what you have to do on most embedded architectures, where the firmware doesn't tell you where the console is located.

On x86, either the firmware can tell you or you can rely on 20 years of legacy, with very few divergences.

-hpa