Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Sep 1996 08:34:23 +0200 (MET DST)
From:      sos@FreeBSD.org
To:        bde@zeta.org.au (Bruce Evans)
Cc:        cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org, peter@freefall.freebsd.org
Subject:   Re: cvs commit:  src/sys/i386/isa syscons.c
Message-ID:  <199609110634.IAA27277@ra.dkuug.dk>
In-Reply-To: <199609102015.GAA02194@godzilla.zeta.org.au> from "Bruce Evans" at Sep 11, 96 06:15:48 am

next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Bruce Evans who wrote:
> 
> >  Modified:    sys/i386/isa  syscons.c
> >  Log:
> >  Hack workaround XFree86 switching failure when used with /dev/sysmouse
> >  and xdm, possibly in general.
> >  
> >  What was happening was that the server was doing a tcsetattr(.. TCSADRAIN)
> >  on the mouse fd after a write.  Since /dev/sysmouse had a null t_oproc,
> >  the drain failed with EIO.  Somehow this spammed XFree86 (!@&^#%*& binary
> >  release!!), and the driver was left in a bogus state (ie: switch_in_progress
> >  permanently TRUE).

Hmm, that problem doesn't exist with Xinsides server (which I use
with my strange P9100 card). I'll have a look at this before commenting
further..

> This reminds me of what happens when crtscts is locked on for the mouse.
> My mouse doesn't supply CTS, so draining takes forever.  Killing XFree86
> require kill -9 from somewhere other than the console IIRC, and leaves
> the console driver in a bogus state.  Some graphics cards go into a
> strange state when XFree86 is started up again in this state.  Sometimes
> XFree86 manages to kill itself after a timeout, but the console driver
> is left in a bogus state.

Hmm, maybe its time I take a look at XFree86's screen switch code again
(well I did write it at sme point :) ), as the Xinside server
doesn't seem to suffer from all these problems...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609110634.IAA27277>