Michael Lorenz wrote:
> Helo,
>
>   
>>> 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.
>>>       
>> struct wsscreen is not really defined anywhere I can see. 
>>     
>
> Me blind. Fixed that so ->ioctl() and ->mmap() now get
> scr->scr_dconf->emulcookie
>
> have fun
> Michael
>   

Hmm... since this change represents an API change for device drivers,
maybe the kernel version should have been bumped to 3.99.18?

-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191