On Mon, Nov 11, 2002 at 07:58:50PM +1100, Brad Hards wrote:
> > EVIOCGUNIQ does not even exist in the 2.4.x headers, and EVIOCGBUS
> > happily returns 0 0 0 0, instead of useful data.
> What kernel are you using? I'll take a look if I can get some time.
> Note that EVIOCGBUS is gone in 2.5 (replaced by EVIOCGPHYS, which returns a 
> string instead of short[4]).

2.4.20-pre10-ac2

Though I'm about to see about moving this box to 2.5.47.
> 
> > This means that, at least with 2.4.x, it is impossible to tell the
> > difference between two identical mice.
> We'll backport whatever is important to 2.4

That is probably going to be EVIOCGPHYS and possibily EVIOCGUNIQ.
> 
> > I guess this means that my next step is seeing what is available for
> > 2.5.x drivers.
> By the time that people are shipping X with event drivers, the kernel will be 
> 2.6, and 2.4 will probably have enough coverage to work.

Hope so.

Do you have any thoughts on how to get X to turn drivers on/off?

The hotplug side of things I can probably handle pretty easily, but the
X side I could use some help on.

Zephaniah E. Hull.
> 
> Brad

-- 
        1024D/E65A7801 Zephaniah E. Hull <[EMAIL PROTECTED]>
           92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
            CCs of replies from mailing lists are requested.

"Microsoft is a cross between the Borg and the Ferengi.  Unfortunately,
they use Borg to do their marketing and Ferengi to do their
programming."
  -- Simon Slavin in asr

Attachment: msg10735/pgp00000.pgp
Description: PGP signature

Reply via email to