> "Pavel" == Pavel Machek <[EMAIL PROTECTED]> writes:
>> Would /dev/input/mice not also be affected?
Pavel> Yes, /dev/input/mice == /dev/psaux.
What I get for looking in /dev (c 10 1 vs c 13 63) rather than
/usr/src/linux. :-/
-JimC
-
To unsubscribe from this list: send the line "unsubscrib
Hello,
I stand corrected. The WSL driver is _not_ needed as it actually is possible
to use libusb. However, you need this little patch to hid-core.c:
diff -urN linux-2.6.13-rc4.orig/drivers/usb/input/hid-core.c
linux-2.6.13-rc4/drivers/usb/input/hid-core.c
--- linux-2.6.13-rc4.orig/drivers
Hi!
> > > I've attached a gzipped version of my Wireless Security Lock patch
> > > for v2.6.13-rc4.
> > > A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
> > > One part is a receiver which you plug into any available USB port.
> > > The other part is a transmitter which at fix
On Saturday 30 Jul 2005 20:42, Pavel Machek wrote:
> Hi!
>
> > I've attached a gzipped version of my Wireless Security Lock patch
> > for v2.6.13-rc4.
> > A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
> > One part is a receiver which you plug into any available USB port.
> >
Yes, the quirk is in the patch :-)
Pavel Machek wrote:
Hi!
Pavel> Well, that is if you use /dev/psaux, right? Using event devices
Pavel> you should be able to access it from userland.
Would /dev/input/mice not also be affected?
Yes, /dev/input/mice == /dev/psaux.
Until X can hotplug in
Hi!
> Pavel> Well, that is if you use /dev/psaux, right? Using event devices
> Pavel> you should be able to access it from userland.
>
> Would /dev/input/mice not also be affected?
Yes, /dev/input/mice == /dev/psaux.
> Until X can hotplug input devices /dev/input/mice rather than evdev
> will r
> "Pavel" == Pavel Machek <[EMAIL PROTECTED]> writes:
Pavel> Well, that is if you use /dev/psaux, right? Using event devices
Pavel> you should be able to access it from userland.
Would /dev/input/mice not also be affected?
Until X can hotplug input devices /dev/input/mice rather than evdev
w
Part of what I do is to tell input to keep hands of the device
(in hid-core.c).
I have tried to contact vojtech - I sent him the patches earlier
this week but I got no response. He's probably on vacation or so :-)
Ah well ...
Pavel Machek wrote:
Hi!
I (and others) have tried using combina
Hi!
> I (and others) have tried using combinations of libusb/userland
> stuff - but have failed miserably.
You may need to patch input to keep hands off that device, but the
rest should be doable using libusb, right? Or talk to vojtech, using
input devices should devices without libusb should be
Hi Pavel,
I (and others) have tried using combinations of libusb/userland
stuff - but have failed miserably.
/brian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-i
Hi!
> Hehe - the WSLs are already reality. Sitecom is a producer of
> these and you can get another brand from ThinkGeek.
Aha, ok.
> Sitecom device:
> http://www.sitecom.com/products_info.php?product_id=293&grp_id=1
>
> ThinkGeek:
> http://www.thinkgeek.com/gadgets/security/698d/
>
> Why in k
Hi Pavel,
Hehe - the WSLs are already reality. Sitecom is a producer of
these and you can get another brand from ThinkGeek.
Sitecom device:
http://www.sitecom.com/products_info.php?product_id=293&grp_id=1
ThinkGeek:
http://www.thinkgeek.com/gadgets/security/698d/
Why in kernel? Well, the de
Hi!
> I've attached a gzipped version of my Wireless Security Lock patch
> for v2.6.13-rc4.
> A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
> One part is a receiver which you plug into any available USB port.
> The other part is a transmitter which at fixed intervals sends
>
I'll try it again ... - it looks ok now - sorry for the noise!
diff -urN linux-2.6.13-rc4.orig/drivers/usb/Makefile
linux-2.6.13-rc4/drivers/usb/Makefile
--- linux-2.6.13-rc4.orig/drivers/usb/Makefile 2005-07-29 00:44:44.0
+0200
+++ linux-2.6.13-rc4/drivers/usb/Makefile 2005-07-
Brian Schau wrote:
*Grrr* - it's the mailer (I'm using Mozilla Thunderbird). I don't
know why it has chosen to fold those two lines.
I use thunderbird too... It does a good job with text file attachments,
it inserts them inline correctly... Maybe try again that way?
--
Michael Krufky
-
*Grrr* - it's the mailer (I'm using Mozilla Thunderbird). I don't
know why it has chosen to fold those two lines.
The section looks like:
+ struct usb_wsl *wsl=urb->context;
+ int id=0, retval;
+
+ switch (urb->status) {
+ case -ECONNRESET:
/brian
Zwane Mwaikambo wrot
On Sat, 30 Jul 2005, Brian Schau wrote:
> Hi Michael (and others),
>
>
> Thanks for the info. Well, the reason why I didn't inline the patch
> was due to the size of it - in terms of lines. However, here it is:
> +static void wsl_irq_in(struct urb *urb, struct pt_regs *regs)
> +{
> + st
Hi Michael (and others),
Thanks for the info. Well, the reason why I didn't inline the patch
was due to the size of it - in terms of lines. However, here it is:
diff -urN linux-2.6.13-rc4.orig/drivers/usb/Makefile
linux-2.6.13-rc4/drivers/usb/Makefile
--- linux-2.6.13-rc4.orig/drivers/us
Brian Schau wrote:
I've attached a gzipped version of my Wireless Security Lock patch
for v2.6.13-rc4.
The WSL driver touches these files:
drivers/usb/Makefile(1 line)
drivers/usb/input/Kconfig(10 lines)
drivers/usb/input/Makefile(1 line)
drivers/usb/
Hello,
I've attached a gzipped version of my Wireless Security Lock patch
for v2.6.13-rc4.
A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
One part is a receiver which you plug into any available USB port.
The other part is a transmitter which at fixed intervals sends
"ping
20 matches
Mail list logo
