Date: Sun, 23 Jun 1996 21:56:48 +0200 From: Mark Murray <mark@grondar.za> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: mark@linus.demon.co.uk (Mark Valentine), mark@grondar.za, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Syscons CUT&PASTE functionality added... Message-ID: <199606231956.VAA02659@grumble.grondar.za>
next in thread | raw e-mail | index | archive | help
Michael Smith wrote: > Mark Valentine stands accused of saying: > > > > > It does not work here. I have a vga (Et4000 with 1MB) and a genius > > > mouse (works on X as MouseSystems on /dev/ttyd1) > > > > I forgot to mention that bit in my other mail - I had to use the cuaa? > > device (/dev/cuaa1 in your case) instead! (The more I poke at serial > > devices, the less I understand them... My X server uses the ttyd? device > > just fine.) > > Operations on a ttyd? device will block until the port has DCD raised. > If DCD drops again, the process on the port will get HUP. I tried the cuaa1 device and it worked, but now X is broken. :-( If I Altfn to the X screen or launch xdm while moused is running, the screen flicks between graphics and text about 4 times, then returns to the text screen, leaving a dead xdm and no other X processes. Killing moused before doing the Alt-Fn works OK. > cua? devices are similar, but they pretend that they have DCD when you > first open them. > > The X server knows how to find the cuaa? device that corresponds > to a give ttyd? device. Moused doesn't. Worth "teaching" it? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606231956.VAA02659>