--Signature_Wed__18_May_2005_08_11_30_-0400_ABViTdsB7Oo1nMee
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> > One will carry the (console) tag, but that's not necessarily
> > wsdisplay0, and to make things worse ttyE0 may not point at the
> > console output device - it will point at the first virtual console
> > on wsdisplay0.
>=20
> There is a "console" locator for wsdisplay (and wskbd) which
> should allow to wire a specific wsdisplay to the hardware instance
> initialized as console. Something like
> wsdisplay0 at [driver]? console 1
> wsdisplay* at [driver]?

This won't help in GENERIC kernels when there are - like many U10s - two
display devices with only one in use. Of course we could assume that if
a Creator board is present it will almost certainly the console but
that's ugly in my opinion.

> If you vave different cards (with different drivers), matching
> the interface attribute
> wsdisplay0 at wsemuldisplaydev? console 1
> should also work.

Thanks, I'll give that a try.

have fun
Michael

--Signature_Wed__18_May_2005_08_11_30_-0400_ABViTdsB7Oo1nMee
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQosw8spnzkX8Yg2nAQL9Rwf/fer3Y+fDU2RMmPup3Ox4jyrgwcdULcsq
kOGF5hsBEri+xTtKWylv1NVrZLlCl5DvDfqebegtHnRtAWE02GkcFFy0ciqEPhRr
A1uCxAws4wiO9/UX7R87a4IUhr95yRwgf6gQk3NCOKwZA/898OJ3ALaKdCJ8cabK
OH/oA6rMsYKQPlgBntwa2KwOTkj/+DzmsvmAGSnhZTIgNT5RlSg5DFfcBFYSR03c
OUC4GjCT2KeB6+C//TJ8BZJK5SnappB9hFGNg7B3ybJTlucXuVEV2oB0MvrujY2L
2HRYLU0bMgrjKb0dw1NU5+NvDI6uXXmWt2rlCyIBa8NcK3CQ0amEdA==
=SMgk
-----END PGP SIGNATURE-----

--Signature_Wed__18_May_2005_08_11_30_-0400_ABViTdsB7Oo1nMee--