Hi Dmitry,
On 3/18/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> Hi Johann,
>
> On Saturday 17 March 2007 17:50, johann deneux wrote:
> > A note about that patch: Apparently Anders Fugmann submitted a patch to use
> > usb_kill_urb to linux-usb-devel for version 2.6.1
first value in the "rumble" report was actually the report's id.
Removed it, since hid-core.c takes care of it.
- Email address update.
--
Johann Deneux
PS: please CC to me when replying, I am not registred on linux-usb-devel.
diff -u linux-2.6.1-rc1/drivers/usb/input/hid-core.c
Sergey Vlasov wrote:
On Mon, Dec 15, 2003 at 11:35:33PM +, Johann Deneux wrote:
Attached is a patch doing two things:
hid-lgff.c: Fixes an obvious list handling issue.
hid-core.c: - Use INT out urbs instead of bulk out urbs. That's the way
it should be
- Remove some repor
out urbs instead of bulk out urbs. That's the way
it should be
- Remove some report->id magic.
IMPORTANT NOTE: You probably do not want to apply this patch yet. I do
not understand what the report->id thing is supposed to do, but I know
it prevents my driver to work (no c
for this
restriction, though).
PS: when replying, please include me. I am not subscribed to the list.
--
Johann Deneux
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up
t; thus it is not an indication of the real "urb->actual_length".
> Maybe it is supposed to force "urb->complete(urb)" to be called on the ports' status
>changing.
>
> These kind of "not obvious" purposes seem sadly to be common in kernel sources
w(io_addr + USBPORTSC1 + i * 2) & 0xa) > 0 ? (1 << (i +
>1)) : 0);
> len = (i + 1) / 8 + 1;
> }
>
> return !!*buf;
> }
>
>
> Little notes in code will be helpful.
>
> Best regards,
> sE
>
--
Joha
Greg KH wrote:
> On Thu, Jul 11, 2002 at 05:16:10PM +0200, Vojtech Pavlik wrote:
>
>>Hi!
>>
>>This cset is update of the HID drivers to the latest version, as a part
>>of the Input merge. It finally includes ForceFeedback support by Johann
>>Deneux, enabli
Vojtech Pavlik wrote:
> On Sat, Jun 01, 2002 at 01:02:23PM +0300, Johann Deneux wrote:
>
>>Vojtech Pavlik wrote:
>>
>>>On Mon, May 27, 2002 at 01:17:58PM +0200, Johann Deneux wrote:
>>>
>>>
>>>>Johannes Erdfelt wrote:
>>>>
>
Vojtech Pavlik wrote:
> On Mon, May 27, 2002 at 01:17:58PM +0200, Johann Deneux wrote:
>
>>Johannes Erdfelt wrote:
>>
>>
>>>
>>>I can only see 2 reasons for putting it into the HCD: OHCI and EHCI
>>>handle it implicitily and for speed.
>&
n what you mean by fast. I am trying to write a driver for a
device that needs control messages to be sent often (every 0.1s or 0.01s
or so).
--
Johann Deneux
___
Don't miss the 2002 Sprint PCS Application Developer's Confe
Hi,
It seems to me that code and comments disagree in drivers/usr/core/usb.c.
I attached a patch fixing the comments. Hopefully the code is right :)
This patch is against 2.5.16
--
Johann Deneux
--- drivers/usb/core/usb.c~ Mon May 20 11:38:18 2002
+++ drivers/usb/core/usb.c Sat May
it);
return -1;
}
while (timeout && iforce->ctrl->status == -EINPROGRESS)
timeout = schedule_timeout(timeout);
set_current_state(TASK_RUNNING);
remove_wait_queue(&iforce->wait, &wait);
if (!timeout) {
ial-boxes having many
thousands of dials (is that possible ?): register as many input devices
as necessary. I guess it would be possible to have one physical device
seen as several input devices.
>
> Please let me know what you think of this proposal; if it's acceptable, I'll
te any part of
my code (ie iforce), is it ? So why would it care if I locked one of my
own spinlocks or not ?
iforce is not a usb-serial driver, though. Did you mean that only
usb-serial drivers may not submit urbs while holding a spinlock ?
--
Johann Deneux
__
, this is
> surely a beginner'squestion) ? I know the problem is solved using some
> fork but threads are so nices...!
>
Did you try using select, poll or opening the device using O_NONBLOCK ?
--
Johann Deneux
___
[EM
end request does
> nothing and urb.state return -103. Also clearing the urb before or in
> the interrupt handler has no effect.
> Any solutions how to clear a urb?
I am no specialist of USB-programming, but I worked with Vojtech on the
iforce driver. If you show me your code, perhap
issue, and I think this needs to be resolved
> > before we can move forward. I don't think it's a huge issue, but it needs
> > to be addressed. The place to do it is with the linuxconsole folks...
>
> Hm. Do you have documentation on the iFeel protocol to how we
he
linuxconsole one, or your project page on sourceforge ?
Did you manage to get any information about the protocol itself ?
--
Johann Deneux
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
19 matches
Mail list logo
