Alternatively, as mac_serial_print is not used in head.S, perhaps you
can just rewrite it in C (incl. manually inlining serial_putc) and put
it in arch/m68k/mac/debug.c?
Reading through arch/m68k/mac/debug.c again, I can't see why we even need
mac_debug_console_write() and mac_serial_print(). I've only ever used
debug=ser|ser1|ser2 (rather than debug=scn|con) and it's always worked.
Moreover, I don't see any advantage in calling
register_console(&mac_console_driver) with
mac_console_driver.write = mac_debug_console_write
as opposed to,
mac_console_driver.write = mac_sccb_console_write
Or am I missing something??
Debug output before console init, perhaps?
(Disclaimer: I've not looked at the code in question. We used to have need
for serial debug output early on before console init, that's all)
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
