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

Hello,

> > Okay, I have a concern this.  As far as I can tell, the cookie is
> > passed to the driver, but I cannot see how the driver can make sense
> > of it.  The cookie that wsdisplay passes seems to be a struct
> > wsscreen, which is a private structure to wsdisplay(4) -- it is not
> > declared in any external headers.
> >=20
> > So how is a display driver (e.g. machfb, or more to the point, my
> > radeonfb driver) supposed to use this member argument?  It doesn't
> > look like you are using this from within any of the modified drivers
> > (or at least the ones I looked at, p9100, amidisplaycc, machfb,
> > vga.)
> >
> > The changes to wsdisplay(4) shed no light on this either.
> >=20
> > Pass an opaque cookie is useless to the driver unless there is some
> > way for the driver to do something meaningful with it.
>=20
> What Garrett said.  If you want to identify a screen you need to pass
> emulcookie, as wsdisplay does to show_screen &co.

Argh, that's what was supposed to happen. I'll fix that.

have fun
Michael

--Signature_Wed__12_Apr_2006_21_11_36_-0400__OQwBKdF0MnMAi92
Content-Type: application/pgp-signature

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

iQEVAwUBRD2lSMpnzkX8Yg2nAQL7PAf/T2hwChAoZgJqqaSaAlXWdUq9NguxeiIb
GFOmQCY68y9N95kwXneuouJcDlJEEAvuWb3JT0gZt+MbvP5V4PzixOlvXQ0dpT05
EKAKGjasud7MEOfxU6p/J6sZVj6g/Tm93IuG1IridHi7P3wlDYN6EZ8WCvBq5tKn
MkHFivUeBOfyBU2jQ9NVPB695heV9S0eDE6F29XhR5mu+o72V1xotYbhGgVdqRyk
FzRC1hmksBC0fVuYD5a/NJhcwN+lkONSK9zQn8MZQqC76umPvoCp9iji14HC3Vlh
F4jXbApodq2QCO27XHuvX6vk2TJmlVAG4+e1zBH0jGQBkQghqm5rZQ==
=kIDy
-----END PGP SIGNATURE-----

--Signature_Wed__12_Apr_2006_21_11_36_-0400__OQwBKdF0MnMAi92--