I spent some time working on the "zs" driver this weekend,
with the main result being confusion.  This is mostly due
the fact that I don't know what config.new and autoconfig
do to build various driver structures.

So, here are some questions:

I could not find callers of all zs driver entry points.
How does the "zs" driver get called in the sparc kernel?

The virtual console driver (sys/dev/cons.c) aparently
wants to find the real console by calling a series of
cn_probe functions for potential console devices.
How is this table of candidates built?

There appears to be a hack in the zs driver that it uses to
determine where to send its input (sys/arch/sparc/dev/zs.c:886)
and a mention of "bstreams" being a better way.
How should this multi-console stuff work?

Is there some documentation on config.new and the kernel
autoconfiguration phase that might answer these questions?

Gordon W. Ross  		Mercury Computer Systems
gwr@mc.com      		199 Riverneck Road
508-256-1300			Chelmsford, MA 01824-2820

------------------------------------------------------------------------------