-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 11 Nov 2002 21:03, Zephaniah E\. Hull wrote:
> 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've previously submitted patches to update 2.4, but they were knocked back 
(too late in the 2.4.19-pre series) at the time, and I haven't updated them.

> > > 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.
Trust me :)

> Do you have any thoughts on how to get X to turn drivers on/off?
That is the bit I don't know. I'm really only across the input layer and usb 
stuff. I've basically been lurking here, trying to find someone who knows 
enough X drivers, and then motivate them...

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

Brad
- -- 
http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9z4BdW6pHgIdAuOMRAtDvAJ926WfQJEsUe5vgZM2mmeVHwofu0ACgpdKN
JLxQsjbcbnw7qJqCxJPoX48=
=EcEV
-----END PGP SIGNATURE-----

_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to