Date: Tue, 16 Jul 1996 20:09:12 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Ken Marsh <durang@u.washington.edu> Cc: questions@freebsd.org Subject: Re: MAKEDEV making symbolic link, not mouse dev. Message-ID: <199607170209.UAA27620@rocky.mt.sri.com> In-Reply-To: <Pine.A32.3.92a.960716185047.22821B-100000@homer26.u.washington.edu> References: <Pine.A32.3.92a.960716185047.22821B-100000@homer26.u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> I am trying to get my mouse going so I can run Xwindows. My mouse comes up
> in dmesg as:
>
> sio0 at 0x3f8-0x3ff irq 4 on isa
>
> I don't know where I got this, but I suspect the device file to be tty00
> or mouse. However, if I do "/dev/MAKEDEV tty00" then /dev/tty00 is NOT
> created, and no error message is given. If I try "/dev/MAKEDEV mouse" then
> a symbolic link, /dev/mouse is created, linked to ITSELF....
I don't know why the 'mouse' target exists in MAKEDEV, but that'
irrelevant.
In any case, if you do a 'man sio', you'll see:
FILES
/dev/ttyd? for callin ports
/dev/ttyid?
/dev/ttyld? corresponding callin initial-state and lock-state
devices
/dev/cuaa? for callout ports
/dev/cuaia?
/dev/cuala? corresponding callout initial-state and lock-state
devices
/etc/rc.serial examples of setting the initial-state and
lock-state de-
vices
So, since the mouse 'calls in' (sends data to the system), you would use
/dev/ttyd?, where ? is the device number of the port, in your case it
would be /dev/ttyd0.
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607170209.UAA27620>