Menu
▾
▴
linuxconsole-dev
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
(235) |
Apr
(30) |
May
(32) |
Jun
(86) |
Jul
(81) |
Aug
(108) |
Sep
(27) |
Oct
(22) |
Nov
(34) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(78) |
Feb
(10) |
Mar
(81) |
Apr
(27) |
May
(13) |
Jun
(105) |
Jul
(78) |
Aug
(52) |
Sep
(59) |
Oct
(90) |
Nov
(127) |
Dec
(49) |
| 2002 |
Jan
(102) |
Feb
(72) |
Mar
(54) |
Apr
(98) |
May
(25) |
Jun
(23) |
Jul
(123) |
Aug
(14) |
Sep
(52) |
Oct
(65) |
Nov
(48) |
Dec
(48) |
| 2003 |
Jan
(22) |
Feb
(25) |
Mar
(29) |
Apr
(12) |
May
(16) |
Jun
(11) |
Jul
(20) |
Aug
(20) |
Sep
(43) |
Oct
(84) |
Nov
(98) |
Dec
(56) |
| 2004 |
Jan
(28) |
Feb
(39) |
Mar
(41) |
Apr
(28) |
May
(88) |
Jun
(17) |
Jul
(43) |
Aug
(57) |
Sep
(54) |
Oct
(42) |
Nov
(32) |
Dec
(58) |
| 2005 |
Jan
(80) |
Feb
(31) |
Mar
(65) |
Apr
(41) |
May
(20) |
Jun
(34) |
Jul
(62) |
Aug
(73) |
Sep
(81) |
Oct
(48) |
Nov
(57) |
Dec
(57) |
| 2006 |
Jan
(63) |
Feb
(24) |
Mar
(18) |
Apr
(9) |
May
(22) |
Jun
(29) |
Jul
(47) |
Aug
(11) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Nico S. <nic...@pc...> - 2002-02-17 19:45:35
|
> > However, James Simmons said that he will be working on > > this for 2.5 and move it to userspace completely, reworking gpm. >=20 > Yes I plan to move the selection code to userland.=20 Please wait until gpm-1.20.0 finally is released, so you can patch=20 against this.=20 > > Nevertheless, I didn't saw a notice about this at all since then -=20 > > there's no metion about this on linuxconsole's project homepage, in the > > 2.5 todo list nor anywhere else - and as I'm looking forward for this > > change a lot, I would like to ask if there's any movement in this issue. > > I would be even willing to help, if possible :). >=20 > I haven't gotten around to it but I do plan to work on it. I could use all > the help I can get. Same here :) But surely we'll help you where possible. --=20 Nico Schottelius Please don't wonder, if you recieve answers to old mails from me. I try to remove my huge backlog currently. |
|
From: Nico S. <nic...@pc...> - 2002-02-17 19:45:35
|
> > Possibly I have never heard about that and don't know anything particul= ar about > > it. > > But in fact, improving something is generally good and if I have/get so= me > > information about that, we could include it in gpm.=20 >=20 > It never really got out since I never got the chance to rework gpm.=20 You got it together with me.=20 > > Sounds good, so you're the person wrinting the patch for gpm ;) >=20 > There are alos patches to get GPM working with the input api in CVS. I > can post them. Just send them. --=20 Nico Schottelius Please don't wonder, if you recieve answers to old mails from me. I try to remove my huge backlog currently. |
|
From: Franz S. <Fra...@la...> - 2002-02-16 22:25:41
|
Hi, can I add #define KEY_BRIGHTNESSDOWN 224 #define KEY_BRIGHTNESSUP 225 to input.h? Franz. |
|
From: Johann D. <de...@if...> - 2002-02-16 21:45:15
|
Hello, Rodrigo Damazio has opened a project on sourceforge to build a hi-level force-feedback library. Everyone with ideas and suggestions is welcome to join. Right now, we are in the planning phase. URL of the project: http://sourceforge.net/projects/libff/ Mailing-list: lib...@li... Registering to the mailing-list: http://lists.sourceforge.net/mailman/listinfo/libff-devel -- Johann Deneux ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
|
From: Johann D. <de...@if...> - 2002-02-15 14:31:13
|
[cc: linuxconsole ML] On Fri, 15 Feb 2002 11:55:38 -0200 "Rodrigo Damazio" <cu...@uo...> wrote: > > 1: > Hi, I'm just wondering if you have a input patch with the current > code against 2.5.3-dj5 or 2.5.4... I have a small patch against 2.4.17 including only the iforce driver (+ needed files like input.h, plus a few fixes on evdev and input). See http://www.docs.uu.se/~johannd/projects/ff/ (hoping the university did not close http access from your net) I used to have an input patch for kernels 2.4.17, but it was before the changes input.h For 2.5.x-dj kernels, it is usually enough to replace the drivers/input subdir by the one found in the CVS. It works for me and iforce, but if it fails for you, please tell us (the linuxconsole people) Hopefully, we can soon do the same with the standard kernel (or maybe we can already do it, as the input core has just reached linus' tree) > > Thanks > Rodrigo > ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
|
From: Rodrigo D. <cu...@uo...> - 2002-02-14 17:33:35
|
Sorry to use the list for this, but - Johann, I've tried to send you sev= eral e-mails regarding patches and libff, and they all get returned with = this error: ... while talking to veda.it.uu.se.: >>>>>> MAIL From:<cu...@uo...> >>> <<< 550 5.0.0 [200.231.206.26] denied access; see <URL:http://www.docs.uu= .se/intruders/> 554 <jo...@do...>... Service unavailable [Servico nao disponivel] Rodrigo --=20 ******************************* * Rodrigo Damazio * * *************************** * * cu...@uo... * * rod...@po... * * ICQ: #3560450 * * http://www.vros.com/cuddly/ * * *************************** * * Engenharia da Computa=E7=E3o * * Escola Polit=E9cnica * * USP - S=E3o Paulo * ******************************* |
|
From: James S. <jsi...@tr...> - 2002-02-13 19:40:33
|
> Hi > Can You ilustrate how to video units assigned with /dev/tty's? Its automatic. As soon as a new display and new keyboard is detected it creates a VT. > How many tty's per unit? 16 > Where determined concrete /dev/fbX<->/dev/ttyX binding? At present it is first come first serve to get a tty range. > con2fb couldn't compile with ruby fb.h. I removed that functionality. Actually I need to add it back once I make fbcon modular. > I try 3dfxfb.c v1.17 and get no prompt or blank screen. I have to try it again. I haven't played with it in awhile. > VGA console and Voodoo3 framebuffer configured. Don't use vga console at the same time. Just select the framebuffer console. > Two keyboards is attatched and mapped with two different vt pointer > (checked in keyboard.c, kbd_connect()). > Must take_over_console() in framebuffer init routines called? Take_over_console replaces a display driver for a VT. In the case of having VGA console then loading in the 3dfx and fbcon driver. Thi sis tricky code tho which I haven't worked out yet. > Must be additional getty in inittab for second framebuffer added? Yes. You need to add gettys for tty16 to tty32. > I patch 3dfxfb.c . This one allowed compilation. Commited. Will test tonight. |
|
From: James S. <jsi...@tr...> - 2002-02-13 18:21:52
|
> Possibly I have never heard about that and don't know anything particular about > it. > But in fact, improving something is generally good and if I have/get some > information about that, we could include it in gpm. It never really got out since I never got the chance to rework gpm. > Sounds good, so you're the person wrinting the patch for gpm ;) There are alos patches to get GPM working with the input api in CVS. I can post them. |
|
From: James S. <jsi...@tr...> - 2002-02-13 18:16:24
|
> However, James Simmons said that he will be working on > this for 2.5 and move it to userspace completely, reworking gpm. Yes I plan to move the selection code to userland. > Nevertheless, I didn't saw a notice about this at all since then - > there's no metion about this on linuxconsole's project homepage, in the > 2.5 todo list nor anywhere else - and as I'm looking forward for this > change a lot, I would like to ask if there's any movement in this issue. > I would be even willing to help, if possible :). I haven't gotten around to it but I do plan to work on it. I could use all the help I can get. |
|
From: James S. <jsi...@tr...> - 2002-02-13 17:07:47
|
Sorry about the time away. I was busy laying with the new fbdev code going into the DJ tree. During this time I was away from my email for a good amount of time. . --- |o_o | |:_/ | Give Micro$oft the Bird!!!! // \ \ Use Linux!!!! (| | ) /'_ _/`\ ___)=(___/ |
|
From: Aivils S. <Aiv...@un...> - 2002-02-13 10:24:11
|
Hi
Can You ilustrate how to video units assigned with /dev/tty's?
How many tty's per unit?
Where determined concrete /dev/fbX<->/dev/ttyX binding?
con2fb couldn't compile with ruby fb.h.
I try 3dfxfb.c v1.17 and get no prompt or blank screen.
VGA console and Voodoo3 framebuffer configured.
Two keyboards is attatched and mapped with two different vt pointer
(checked in keyboard.c, kbd_connect()).
Must take_over_console() in framebuffer init routines called?
Must be additional getty in inittab for second framebuffer added?
I patch 3dfxfb.c . This one allowed compilation.
Don't know corpse code logic or not.
--- ruby-files/drivers/video/tdfx/3dfxfb.c Fri Jan 11 08:54:07 2002
+++ linr/drivers/video/tdfx/3dfxfb.c Tue Feb 12 20:23:10 2002
@@ -326,12 +326,12 @@
struct tdfx_par *par = (struct tdfx_par *) ptr;
unsigned long flags;
- spin_lock_irqsave(par->DAClock, flags);
+ spin_lock_irqsave(&par->DAClock, flags);
banshee_make_room(1);
tdfx_outl(VIDPROCCFG, tdfx_inl(VIDPROCCFG) ^ VIDCFG_HWCURSOR_ENABLE );
par->hwcursor.timer.expires=jiffies+HZ/2;
add_timer(&par->hwcursor.timer);
- spin_unlock_irqrestore(par->DAClock, flags);
+ spin_unlock_irqrestore(&par->DAClock, flags);
}
static u32 do_calc_pll(int freq, int* freq_out)
@@ -790,11 +790,11 @@
/* If we are going to be changing things we should disable
the cursor first */
if (info->cursor.enable) {
- spin_lock_irqsave(par->DAClock, flags);
+ spin_lock_irqsave(&par->DAClock, flags);
info->cursor.enable = 0;
del_timer(&(par->hwcursor.timer));
tdfx_outl(VIDPROCCFG, par->hwcursor.disable);
- spin_unlock_irqrestore(par->DAClock, flags);
+ spin_unlock_irqrestore(&par->DAClock, flags);
}
/* Disable the Cursor */
@@ -813,11 +813,11 @@
(cursor->cmap.green[cursor->cmap.start+1] << 8) |
(cursor->cmap.blue[cursor->cmap.start+1]));
fb_copy_cmap(&cursor->cmap, &info->cursor.cmap, 0);
- spin_lock_irqsave(par->DAClock, flags);
+ spin_lock_irqsave(&par->DAClock, flags);
banshee_make_room(2);
tdfx_outl(HWCURC0, bg_color);
tdfx_outl(HWCURC1, fg_color);
- spin_unlock_irqrestore(par->DAClock, flags);
+ spin_unlock_irqrestore(&par->DAClock, flags);
}
if (cursor->set && FB_CUR_SETPOS) {
@@ -830,10 +830,10 @@
info->cursor.pos.y = y;
x += 63;
y += 63;
- spin_lock_irqsave(par->DAClock, flags);
+ spin_lock_irqsave(&par->DAClock, flags);
banshee_make_room(1);
tdfx_outl(HWCURLOC, (y << 16) + x);
- spin_unlock_irqrestore(par->DAClock, flags);
+ spin_unlock_irqrestore(&par->DAClock, flags);
}
/* Not supported so we fake it */
@@ -897,10 +897,10 @@
cursor->enable = 1;
info->cursor = *cursor;
mod_timer(&par->hwcursor.timer, jiffies+HZ/2);
- spin_lock_irqsave(par->DAClock, flags);
+ spin_lock_irqsave(&par->DAClock, flags);
banshee_make_room(1);
tdfx_outl(VIDPROCCFG, par->hwcursor.enable);
- spin_unlock_irqrestore(par->DAClock, flags);
+ spin_unlock_irqrestore(&par->DAClock, flags);
return 0;
}
@@ -1231,7 +1231,7 @@
init_timer(&default_par.hwcursor.timer);
default_par.hwcursor.timer.function = do_flashcursor;
default_par.hwcursor.timer.data = (unsigned long)(&default_par);
- spin_lock_init(default_par->DAClock);
+ spin_lock_init(&default_par.DAClock);
}
fb_info.cursor.set = 0;
fb_info.cursor.enable = 0;
Aivils Stoss
nosy user
|
|
From: Alessandro R. <ru...@gn...> - 2002-02-12 10:02:22
|
On Feb 6th, Petr Baudis: > [...] However, James Simmons said that he will be working on > this for 2.5 and move it to userspace completely, reworking gpm. That would be great. We (gpm list) have been talking about it a few years ago, but Ian Zimmerman reported a problem with mapping glyphs to keyboard input: there was no mean (at least back then) to pass the complete mapping from the kernel to user space. Sure doing it for the trivial mapping is trivial, and I think it would be an interesting experiment. I was even thinking to have a try some time ago, when I was the gpm maintainer. > I would like to ask if there's any movement in this issue. I would > be even willing to help, if possible :). Please get on the gpm mailing list (gp...@li...) and let's put together an implementation. Best /alessandro |
|
From: Franz S. <Fra...@la...> - 2002-02-11 11:11:22
|
Hi Vojtech, would you mind updating utils/scancodes.h with your latest status? I want to regenerate the PPC tables, but it seems scancodes.h is not quite uptodate. After that you can include the PPC stuff of ruby in your next merge to the dj tree. Thanks, Franz. |
|
From: Vojtech P. <vo...@su...> - 2002-02-11 10:37:43
|
On Mon, Feb 11, 2002 at 12:32:09PM +0200, Aivils Stoss wrote: > Hi > I plug second keyboard in PS/2 hole and get this: > skipped dmesg > Testing ttyS0 (0x03f8, 0x00000000)... > ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > Testing ttyS1 (0x02f8, 0x00000000)... > ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > Testing ttyS2 (0x03e8, 0x00000000)... > serial: ttyS2: simple autoconfig failed (ff, ff) > Testing ttyS3 (0x02e8, 0x00000000)... > serial: ttyS3: simple autoconfig failed (ff, ff) > serio: i8042 KBD port at 0x60,0x64 irq 1 > serio: i8042 AUX port at 0x60,0x64 irq 12 > input.c: calling /sbin/hotplug input [HOME=/ > PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab83 > NAME=atkbd.c AT Set 2 keyboard] > input.c: hotplug returned -2 > input: AT Set 2 keyboard on isa0060/serio1 > input.c: calling /sbin/hotplug input [HOME=/ > PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab02 > NAME=atkbd.c AT Set 2 keyboard] > input.c: hotplug returned -2 > input: AT Set 2 keyboard on isa0060/serio0 > skipped dmesg > > > If single pluged in, both keyboards works very fine. If two pluged in, > works only second keyboard with PS/2 connector. Can you #define I8042_DEBUG_IO in drivers/input/serio/i8042.h and send me the dmesg in that case? That'd tell us why the two keyboard combination fails on your system. By the way, what tree are you using? Latest CVS? What version of i8042.o? > First keyboard has old type connector. inputattach -ps2ser : No such > device. Both keyboards detected without ps2serkbd module. PS2serkbd isn't needed unless you connect the keyboard to the COM ports. > Under ruby I lost my serial mouse. Any programm would use serial hungup my > system. > Sample$ cat /dev/ttyS0 > Do not know how to debug this. With printk() I find , uart_open() is caled. > In uart_open() uart_startup() ever end, uart_block_til_ready() may start, > but never end. If debug is turned on in serial_core.c and serial_8250.c > sometimes I get message: > rs_interrupt_single(4)... > status=f9...IIR=C1...end > Sometimes this message repeated 2...3 times. That's a bug in the new serial core most likely. -- Vojtech Pavlik SuSE Labs |
|
From: Aivils S. <Aiv...@un...> - 2002-02-11 10:32:50
|
Hi
I plug second keyboard in PS/2 hole and get this:
skipped dmesg
Testing ttyS0 (0x03f8, 0x00000000)...
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Testing ttyS1 (0x02f8, 0x00000000)...
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Testing ttyS2 (0x03e8, 0x00000000)...
serial: ttyS2: simple autoconfig failed (ff, ff)
Testing ttyS3 (0x02e8, 0x00000000)...
serial: ttyS3: simple autoconfig failed (ff, ff)
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
input.c: calling /sbin/hotplug input [HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab83
NAME=atkbd.c AT Set 2 keyboard]
input.c: hotplug returned -2
input: AT Set 2 keyboard on isa0060/serio1
input.c: calling /sbin/hotplug input [HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab02
NAME=atkbd.c AT Set 2 keyboard]
input.c: hotplug returned -2
input: AT Set 2 keyboard on isa0060/serio0
skipped dmesg
If single pluged in, both keyboards works very fine. If two pluged in,
works only second keyboard with PS/2 connector.
First keyboard has old type connector. inputattach -ps2ser : No such
device. Both keyboards detected without ps2serkbd module.
Under ruby I lost my serial mouse. Any programm would use serial hungup my
system.
Sample$ cat /dev/ttyS0
Do not know how to debug this. With printk() I find , uart_open() is caled.
In uart_open() uart_startup() ever end, uart_block_til_ready() may start,
but never end. If debug is turned on in serial_core.c and serial_8250.c
sometimes I get message:
rs_interrupt_single(4)...
status=f9...IIR=C1...end
Sometimes this message repeated 2...3 times.
Aivils Stoss
nosy user
|
|
From: Johann D. <jo...@do...> - 2002-02-09 23:33:03
|
Hi, I've just spent a few hours trying to help the guys of the tuxbox project to get a logitech rumble pad to work (http://www.tuxboxproject.com/). It was marked to be I-Force compliant, but the iforce driver would not handle it. The input part did not work at all (not surprising, it's handled by hid). The fact that it was however possible to get the thing shake using a modified version of the iforce driver and fftest gave us hope. Unfortunately, the eavesdropping with usb snoopy seemed to show that the protocol used is nothing close to I-Force 2.0. Does anyone know anything about it ? -- Johann Deneux |
|
From: Vojtech P. <vo...@su...> - 2002-02-09 22:49:14
|
On Sat, Feb 09, 2002 at 10:48:32PM +0100, Luciano Campal Vazquez wrote: > Sorry for being so enthusiastic, i only test buttons, not a "full" test, not have time at the moment i modified the joydev.c. It doesn't make the ugly oops. > But only the buttons works, the axis ones doesn't > If i can help you, jstest reports 3 axis and 6 buttons and that it is a joystick, mine is a common gamepad. so i think only 2 axis should be reported, X and Y. There is another fix in the hid-core.c file in the CVS that's needed for this gamepad. -- Vojtech Pavlik SuSE Labs |
|
From: Luciano C. V. <lu...@te...> - 2002-02-09 21:49:03
|
Sorry for being so enthusiastic, i only test buttons, not a "full" test, not have time at the moment i modified the joydev.c. It doesn't make the ugly oops. But only the buttons works, the axis ones doesn't If i can help you, jstest reports 3 axis and 6 buttons and that it is a joystick, mine is a common gamepad. so i think only 2 axis should be reported, X and Y. bye |
|
From: Luciano C. V. <lu...@te...> - 2002-02-09 19:03:02
|
Yes it works perfectly now. Thanks for your help and for being so fast. |
|
From: Vojtech P. <vo...@su...> - 2002-02-09 17:26:12
|
On Thu, Feb 07, 2002 at 02:38:48PM +0100, Johann Deneux wrote: > > I have just buy a Logitech Wingman Precision USB, and i can not make it work on linux. > > > > i have a debian woody, with 2.4.17 kernel, and all usb support in modules. > > > > kernel installs usbcore, and then i modprobe usb-uhci after that the gamepad is recognise > > but it doesn't load automatically a driver, it says no driver claims the device but it loads input module, so i try to load the driver manually i do > > > > modprobe joydev > > > > it gaves a seg fault and after that it seems to lock, doing a lsmod it appears > > modprobe segfaults ? That should not happen. Check if there is a kernel > oops in your log files. If that's the case, please tell us (using > ksymoops). Do not also forget to send us the list of modules inserted when > the bug occurs. Yes, it's a bug in 2.4.17, fixed in the CVS. Division by zero because of incorrectly parsed HID descriptor. -- Vojtech Pavlik SuSE Labs |
|
From: Vojtech P. <vo...@su...> - 2002-02-09 17:24:11
|
On Thu, Feb 07, 2002 at 12:56:06PM -0500, Adam Goode wrote: > I have a couple such mice, and I had wanted to start such work last summer. > > But I ran into a few issues, and kind of just put things on hold. > Perhaps these are now adequately solved? > > Issues: > > * The HID driver which controls mice and mice-like devices had no support > for force feedback stuff, and I really didn't want to make a > completely new driver which was specific to the iFeel and yet > was 99% identical to the generic HID stuff. I think the HID driver can be extended to handle ifeel. The same way as it will have to be extened to handle PID. There isn't much difference, really. By the way, we could get rid of the Wacoms in the black list this way as well. -- Vojtech Pavlik SuSE Labs |
|
From: Paul de B. <P.W...@it...> - 2002-02-09 11:49:50
|
> The modprobe crashed in joydev_connect, on a division by 0. This bug seems > to have been corrected in the current CVS tree. The easiest (?) way to fix > your issue would be to search for the lines: Excellent. Thank you so much. I had the exact same problem and the suggested changes fix it beautifully. Back to xmame... :-) Paul |
|
From: Johann D. <de...@if...> - 2002-02-09 10:19:06
|
On Thu, 07 Feb 2002 16:09:13 +0100 "LU...@te..." <LU...@te...> wrote: > Thxs for your interest. > > i send you 3 files, messages, ksyms, lsmod, they are all the output, > because they are many lines that could interest you. i have few modules > loaded for this try, but if you want me to reduce to the max those tell > me and i will send you again the files. > The modprobe crashed in joydev_connect, on a division by 0. This bug seems to have been corrected in the current CVS tree. The easiest (?) way to fix your issue would be to search for the lines: joydev->corr[i].coef[2] = (1 << 29) / ((dev->absmax[j] - dev->absmin[j]) / 2 - 2 * dev->absflat[j]); joydev->corr[i].coef[3] = (1 << 29) / ((dev->absmax[j] - dev->absmin[j]) / 2 - 2 * dev->absflat[j]); and replace them by: if (!(t = ((dev->absmax[j] - dev->absmin[j]) / 2 - 2 * dev->absflat[j]))) continue; joydev->corr[i].coef[2] = (1 << 29) / t; joydev->corr[i].coef[3] = (1 << 29) / t; They are located near line 470 in drivers/input/joydev.c Another solution would be to try the 2.5.3 kernel with Dave Jones' patch applied. Or if you want to stick to the 2.4 kernel, you can try the input-only patch available from http://www.docs.uu.se/~johannd/projects/ff/patch-2.4.17.bz2 and patch-2.4.17-fix1.bz2 (the later file is not essential, it includes new help files and a more common default configuration). -- Johann Deneux ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
|
From: Johann D. <jo...@do...> - 2002-02-07 18:25:27
|
On Thu, 7 Feb 2002, Adam Goode wrote: > I have a couple such mice, and I had wanted to start such work last summer. > > But I ran into a few issues, and kind of just put things on hold. > Perhaps these are now adequately solved? > > Issues: > > * The HID driver which controls mice and mice-like devices had no support > for force feedback stuff, and I really didn't want to make a > completely new driver which was specific to the iFeel and yet > was 99% identical to the generic HID stuff. Other people here are working on implementing force-feedback using the pid specification. So you are not alone on this. However, you raise a valid issue. It seems we have many hid/ff combinations: - hid/iforce - hid/pid - hid/whatever... How to handle this while keeping the code clean is going to be an interesting design issue. > > * When I was playing with libusb in testing, I orginially was sending > control transfers (which usb-robot supported). But I found out that > the (more-correct?) way to drive the device was through interrupt > transfers, which libusb didn't support. Does this now work with > "one-shot interrupt" support in usbdevfs? It seems one-shot interrupt urbs can be successfuly emulated with bulk urbs anyway. > > * It seemed like overkill to build a full kernel space driver for this > device. This is the big question: > > Should the iFeel be controlled by the generic HID driver like a normal > mouse, with some additional user space stuff (like libusb) controlling > the vibration? No, we allready have a kernel interface (evdev) for force feedback. So libusb is not going to help us here. Unless we use a combination of evdev/libusb. > > > I think the user space vs. kernel space issue is important. What does > everyone think? > > > Points: > > * User space driver: does not require (much?) modification to existing > kernel drivers, should be easier to develop and > test, but might cause issues related to finding > the correct devices and perhaps permissions problems > > * Kernel space driver: might require making a whole new driver or > adding special cases to the existing HID structures, > needs some userspace stuff anyway (to manage > interaction with GUI elements, etc.) There are already people here who are working on a user-space libff. > > > These are just some issues, but I am leaning towards just having a > user space driver. I am looking forward to comments on this.... > Having a working user-space implementation won't hurt anyway, especially if you find it easier to develop. -- Johann Deneux |
|
From: Adam G. <ad...@ev...> - 2002-02-07 17:56:23
|
I have a couple such mice, and I had wanted to start such work last summer.
But I ran into a few issues, and kind of just put things on hold.
Perhaps these are now adequately solved?
Issues:
* The HID driver which controls mice and mice-like devices had no support
for force feedback stuff, and I really didn't want to make a
completely new driver which was specific to the iFeel and yet
was 99% identical to the generic HID stuff.
* When I was playing with libusb in testing, I orginially was sending
control transfers (which usb-robot supported). But I found out that
the (more-correct?) way to drive the device was through interrupt
transfers, which libusb didn't support. Does this now work with
"one-shot interrupt" support in usbdevfs?
* It seemed like overkill to build a full kernel space driver for this
device. This is the big question:
Should the iFeel be controlled by the generic HID driver like a normal
mouse, with some additional user space stuff (like libusb) controlling
the vibration?
I think the user space vs. kernel space issue is important. What does
everyone think?
Points:
* User space driver: does not require (much?) modification to existing
kernel drivers, should be easier to develop and
test, but might cause issues related to finding
the correct devices and perhaps permissions problems
* Kernel space driver: might require making a whole new driver or
adding special cases to the existing HID structures,
needs some userspace stuff anyway (to manage
interaction with GUI elements, etc.)
These are just some issues, but I am leaning towards just having a
user space driver. I am looking forward to comments on this....
Adam
On Tue, Feb 05, 2002 at 10:06:49AM +0100, Johann Deneux wrote:
> Hi,
>
> Does anyone have an IFeel mouse at hand here ? Information about the
> protocol can be found here:
> http://moore.cx/out/ifeel/
>
> If no one with an IFeel mouse feels like starting to implement a driver
> using the information available above, I may well volunteer to do it, but
> that means I would need to buy such a mouse.
>
> --
> Johann Deneux
>
>
>
> _______________________________________________
> Linuxconsole-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
>
|
1998 messages has been excluded from this view by a project administrator.
