Forwarding to the list...
-------- Forwarded Message --------
Subject: Re: Why was support for real console on Ultra removed?
Date: Tue, 21 Nov 2017 23:48:24 +0100 (CET)
From: Jiri Svoboda <[email protected]>
To: Jakub Jermář <[email protected]>
Hi Jakub,
Jakub wrote:
Yes, this was intentional. I removed this legacy initialization code in
favor of a DDF based one which uses serial console and can be used
together with ever-improving QEMU w/ OpenBIOS* (but broke keyboard
support on the real Sun workstations for the time being) even by people
who don't have access to a real-world Sun workstation.
I see, but technically these should not be mutually exclusive, right?
Input server
can multiplex any number of keyboard devices (e.g. a legacy device, and
any number of kbdev devices).
I intend this regression in functionality to be rather temporary as it
should be possible to reimplement the lost functionality using DDF
drivers. We should however first discuss how to figure out which device
is the console. The boot argument solution is a bit clumsy and
inflexible.
I guess for "real" serial ports (that have sockets on the chassis) we
want a configuration utility that allows you to select what's connected
(since reliable auto detection is probably not possible). For a fixed
function port such as the Ultra keyboard port, you'd want the system to
automatically do the right thing. I don't know if there is any generic
way to detect such a port (OpenFirmware properties?) or if you'd
actually need to specify which device is the keyboard for each
particular model. In any case it's a rather complicated problem so I
wouldn't hold my breath.
Thanks,
Jiri
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
