Date: Mon, 1 Dec 2003 21:34:53 -0800 From: "Thomas Lippert" <tlippert362@earthlink.net> To: "George Hartzell" <hartzell@kestrel.alerce.com> Cc: freebsd-mobile@freebsd.org Subject: RE: sjog, spic0 and the GRX570? Message-ID: <410-22003122253453306@earthlink.net>
index | next in thread | raw e-mail
> [Original Message] > From: George Hartzell <hartzell@kestrel.alerce.com> > To: <tlippert362@earthlink.net> > Cc: <freebsd-mobile@freebsd.org> > Date: 11/30/2003 10:03:15 PM > Subject: RE: sjog, spic0 and the GRX570? > > Thomas Lippert writes: > > [...] > > I got the same thing from sjog, not sure why. If what you're after is > > scrolling you can use moused for that. "moused -t jogdial -p /dev/jogdial" > > is I > > believe the incantation that worked on my 560 under 4.x. may be a bit > > different under 5.x. > > I haven't yet bothered to try their. Perhaps somebody else can enlighten us > > both about sjog. > > hope that helps > > > Empirically, if I want the touchpad/buttons *and* the jogdial to work > for scrolling, I have to start moused twice, once w/ > > moused -t auto -p /dev/psm0 > > and once with > > moused -t jogdial -p /dev/jogdial > > Is there a cleaner way? Not that i know of, i just start one using the rc.conf and another via a script. There should be a more elegant solution, though that works for me. There doesn't appear to be away of making both start with the rc.conf. To quote the moused man page "As many instances of the mouse daemon as the number of mice attached to the system may be run simultaneously; one instance for each mouse." So I think that the best solution i have seen is to start the second instance via a startup script. > > g. I think things are now somewhat clearer -Thomashelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?410-22003122253453306>