> On Sat, 23 Sep 2006, e.fahle wrote:
> > Hi,
> > I wrote a driver for fullspeed device based on the code in usb_skeleton.
> > Sending data to the device goes through 2 interrupt-endpoints.
> > So my code uses the fill_int_urb() and submit_urb() and a callback for
> > writing..
> > I allow a limite
On Sat, 23 Sep 2006, e.fahle wrote:
> Hi,
> I wrote a driver for fullspeed device based on the code in usb_skeleton.
> Sending data to the device goes through 2 interrupt-endpoints.
> So my code uses the fill_int_urb() and submit_urb() and a callback for
> writing..
> I allow a limited number of
Hi,
I wrote a driver for fullspeed device based on the code in usb_skeleton.
Sending data to the device goes through 2 interrupt-endpoints.
So my code uses the fill_int_urb() and submit_urb() and a callback for
writing..
I allow a limited number of urbs to be submitted at the same time, just like
Thank you David and Alan for clarifying it.
On 11/9/05, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Nov 2005, Jayaprakash Shanmugam wrote:
>
> > Hi all,
> > I had a code that receives interrupt data from the device. It
> > worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls
On Wed, 9 Nov 2005, Jayaprakash Shanmugam wrote:
> Hi all,
> I had a code that receives interrupt data from the device. It
> worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls the
> Interrupt handler just once.
>
> On 2.4, I had the following and it was working. I got my
> USB
On Wednesday 09 November 2005 4:46 am, Jayaprakash Shanmugam wrote:
> Hi all,
> I had a code that receives interrupt data from the device. It
> worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls the
> Interrupt handler just once.
Yes, in 2.4 the host controller drivers did "auto
Hi all,
I had a code that receives interrupt data from the device. It
worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls the
Interrupt handler just once.
On 2.4, I had the following and it was working. I got my
USBH__vIRQHandler() function called for every 200 milliseconds.
s
On Tue, 26 Jul 2005 [EMAIL PROTECTED] wrote:
> Dear all:
>
> I am developing a USB Wireless adapter driver. I get a problem of
> interrupt endpoint to deal with EHCI USB host.
>
> The problem always occur every time the interrupt endpoint send a URB
> with usb_fill_int_urb ( ) and usb_submit_urb
Dear all:
I am developing a USB Wireless adapter driver. I get a problem of
interrupt endpoint to deal with EHCI USB host.
The problem always occur every time the interrupt endpoint send a URB
with usb_fill_int_urb ( ) and usb_submit_urb ( ), if interrupt interval
is set to 1 (125 us).
The error
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1833 +0200]:
> Do you have the USB debugging option turned on in the kernel
> configuration?
Yes.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
invalid/exp
On Sat, 9 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1823 +0200]:
> > It would help to see the dmesg log showing what happens at these times.
>
> Other than the timeout messages... nothing.
Do you have the USB debugging option turned on in the kerne
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1823 +0200]:
> It would help to see the dmesg log showing what happens at these times.
Other than the timeout messages... nothing.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"
On Sat, 9 Oct 2004, martin f krafft wrote:
> I tried both with 2.6.8.1 with the following results:
>
> - the ep0in timeout messages still appear
> - stopping and starting hotplug does not seem to crash khubd
> anymore
So that patch worked.
> - starting hotplug and most every USB opera
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.10.09.1508 +0200]:
> - the ep0in timeout messages still appear
[...]
> - my USB system seems to be broken. Specifically, I cannot sync
> with my Palm anymore. Curiously, my girlfriends USB media reader
> *does* work, however.
Correc
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.2000 +0200]:
> The patches I sent were for 2.6.9-rc3. The first one might work
> all right 2.6.8.1 but the second one definitely won't. Below is
> a version of the second patch for 2.6.8.1.
I tried both with 2.6.8.1 with the following result
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.2000 +0200]:
> No -- I said the fix _isn't_ in 2.6.9-rc3.
Sorry, I misread you.
> The patches I sent were for 2.6.9-rc3. The first one might work all right
> 2.6.8.1 but the second one definitely won't. Below is a version of the
> second p
On Fri, 8 Oct 2004, martin f krafft wrote:
> > Sometimes errors like this and the ones above are just temporary.
> > The device takes a moment to warm up and start working right. You
> > only need to worry about it if the device doesn't work in the end.
>
> I do have another device (a USB servo
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.1918 +0200]:
> What kind of device is this, can you say? And did it used to work with
> earlier versions of 2.6? If it did, can you pinpoint at which release it
> stopped working?
It's a new device, so I have not used it with anything othe
On Fri, 8 Oct 2004, martin f krafft wrote:
> Okay, let's go after this, I disabled all modules that I could and
> am now going to try to see how I can reproduce the error. USB
> debugging is enabled in the kernel.
>
> To recap, the whole thing is about weird messages about ep0in
> timeouts and th
Okay, let's go after this, I disabled all modules that I could and
am now going to try to see how I can reproduce the error. USB
debugging is enabled in the kernel.
To recap, the whole thing is about weird messages about ep0in
timeouts and the inability to use the affected device. With USB
debuggi
On Tue, 5 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.2016 +0200]:
> > See if you can find out exactly what happens during the USB phase when you
> > stop hotplug,
>
> As in, strace?
That's one way. If the programs are simply shell scripts, you can
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.2016 +0200]:
> See if you can find out exactly what happens during the USB phase when you
> stop hotplug,
As in, strace?
> Also, post the system log for that time period. And make sure you
> have turned on the USB debugging option in the ker
On Tue, 5 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> > The most important thing as far as I'm concerned is to learn what
> > sequence of operations caused the oops you got before.
>
> Okay, I think I can definitely say that the kernel
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> The most important thing as far as I'm concerned is to learn what
> sequence of operations caused the oops you got before.
Okay, I think I can definitely say that the kernel oops only happens
when I stop hotplug. Doing so causes
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> Which messages exactly are you seeing?
As stated in my original post:
usb 4-6: new high speed USB device using address 5
usb 4-6: control timeout on ep0in
usb 4-6: device not accepting address 5, error -71
However, it seems th
On Tue, 5 Oct 2004, martin f krafft wrote:
> Okay, I rebooted and am seeing these messages again...
Which messages exactly are you seeing?
> So now I want to try what you are proposing, but I cannot seem to
> unload hci_usb:
>
> ERROR: Module hci_usb is in use
I said to unload uhci-hcd, not
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.04.2325 +0200]:
> Is this reproducible? What happens if you do "rmmod uhci-hcd"
> yourself by hand, without involving the hotplug programs?
Okay, I rebooted and am seeing these messages again...
So now I want to try what you are proposing, but
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.04.2325 +0200]:
> Don't worry, your disassembly gave the answer we needed. For
> whatever reason (I don't have time to go searching for it now), in
> hcd_endpoint_disable the udev->hcpriv value stored in dev is
> a NULL pointer. Of course that's
On Fri, 1 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2113 +0200]:
> > No, you should use usbcore.ko.
>
> Okay, that worked.
>
> Now, the function starts at 0x5320, so +0x74 (from the oops) gives
> 0x5394... so with +/- 5 lines of context:
>
> 0x000
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2113 +0200]:
> No, you should use usbcore.ko.
Okay, that worked.
Now, the function starts at 0x5320, so +0x74 (from the oops) gives
0x5394... so with +/- 5 lines of context:
0x537e : movl $0x0,0x44(%edx,%edi,4)
0x5386 : mov$0x
On Fri, 1 Oct 2004, martin f krafft wrote:
> Are we talking about the modules directory, or the kernel source
> tree? I have the former (obviously), but the latter does not exist
> -- this is the Debian stock kernel after all.
I was talking about the kernel source tree. But the modules directory
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2026 +0200]:
> One way to do this is to run "gdb hcd.o" from within the
> drivers/usb/core directory, and then do "disass
> hcd_endpoint_disable" at the prompt. The output isn't very
> readable because no external addresses will be given. But
On Fri, 1 Oct 2004, martin f krafft wrote:
> also sprach David Brownell <[EMAIL PROTECTED]> [2004.10.01.1930 +0200]:
> > This suggests UHCI (or the hub driver?) confused usbcore somehow.
> > Can you find out what's at that line? There's some GDB command
> > that'll turn that into a line of C code
also sprach David Brownell <[EMAIL PROTECTED]> [2004.10.01.1930 +0200]:
> This suggests UHCI (or the hub driver?) confused usbcore somehow.
> Can you find out what's at that line? There's some GDB command
> that'll turn that into a line of C code if your kernel is
> appropriately compiled; doesn't
On Thursday 30 September 2004 4:53 am, martin f krafft wrote:
>
> I have a USB device (a built-in 7-in-1 Maxxtro USB 2.0 card reader)
> in this 2.6.8.1 machine of mine, and it's acting up. I am seeing
> messages such as the following every couple of seconds:
>
> usb 4-6: new high speed USB devi
Hi folks,
After having spoken to Greg about this, I am giving it a shot on
this list (at his recommendation).
I have a USB device (a built-in 7-in-1 Maxxtro USB 2.0 card reader)
in this 2.6.8.1 machine of mine, and it's acting up. I am seeing
messages such as the following every couple of seconds
I checked out the interval... it was being set to non-zero somewhere else in
the program... corrected that, and it works. Thank you for the references.
---
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForg
On Mon, 17 May 2004 08:47:27 -0500
"Lonnie Mendez" <[EMAIL PROTECTED]> wrote:
> I'm using the usb-uhci driver (this will also happen on the uhci driver) on
> vanilla kernel 2.4.26. Problem will not occur in 2.6.x
> When sending an urb down the interrupt out pipe, it will succede the first
> time
I'm using the usb-uhci driver (this will also happen on the uhci driver) on
vanilla kernel 2.4.26. Problem will not occur in 2.6.x
When sending an urb down the interrupt out pipe, it will succede the first
time. But then the next time I try this, usb-uhci will give me this error
message:
this o
On Fri, 14 May 2004, Thomas Wahrenbruch wrote:
> Hello list,
>
> the kobil_sct driver requires interrupt-out transfers to write the data
> to the device. This works fine with the ochi hcd, but fails with the
> uhci hcd. I attached the output from /var/log/messages.
> usb_submit_urb returns -22 (-
Hello list,
the kobil_sct driver requires interrupt-out transfers to write the data
to the device. This works fine with the ochi hcd, but fails with the
uhci hcd. I attached the output from /var/log/messages.
usb_submit_urb returns -22 (-EINVAL).
I tested it on a centrino notebook, but it should
hi ,
i am a new to the USB linux field..
what is the correct procedure to be followed to handle interrupt
endpoint..how to read data from an interrupt endpoint...should i wait
infinitely for the interrupt arrival??..
or is there any completion routine like that that is triggered
automatically af
At 12:31 PM 11/11/2003, Alan Stern wrote:
On Tue, 11 Nov 2003, G. Del Merritt wrote:
> I'm working with two digital cameras - a Sanyo Xacti S1 and a Canon
PowerShot
> A80 - and I'm writing an application to talk to them which uses
libusb. Each
> DSC advertises that the maximum bytecount per tran
On Tue, 11 Nov 2003, G. Del Merritt wrote:
> I'm working with two digital cameras - a Sanyo Xacti S1 and a Canon PowerShot
> A80 - and I'm writing an application to talk to them which uses libusb. Each
> DSC advertises that the maximum bytecount per transfer on the interrupt
> endpoint is 8 bytes
I'm working with two digital cameras - a Sanyo Xacti S1 and a Canon PowerShot
A80 - and I'm writing an application to talk to them which uses libusb. Each
DSC advertises that the maximum bytecount per transfer on the interrupt
endpoint is 8 bytes, so I only read a maximum of 8 bytes at a time from
How can I put a jump instruction into specific memory address in C language?
I want to use Serial 0 interrupt in CY7C68013-128AC microchip.
Norbert
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-comm
Hi,
I have a driver for three different usb crypto tokens.
It works completely in userspace by using ioctls on the
/proc/bus/usb/... device.
Now I'd like to add support for another usb crypto token.
What that token does is still 90+% the same, but it differers
in one small issue: the three tokens
John Homppi wrote:
Thanks for the comments.
Where can I find the test programs that demonstrate output on an interrupt
end-point. An example program would help immensely.
I was just using the "usbtest" driver, in 2.5, with the module
option that told it to stream OUT data using interrupt trans
Hi Wolfgang,
Thanks for the comments.
Just to clarify my assumptions, is the following a valid approach?
1) Use usb_fill_int_urb in my own driver to build a URB
2) Use usb_submit_urb to pass the URB to the USB core routines
3) Use a wait queue to await URB completion
4) (as you already stated) u
Thanks for the comments.
Where can I find the test programs that demonstrate output on an interrupt
end-point. An example program would help immensely.
Everything that I tried failed (ie. libusb, HIDDEV, bulk writes to
an interrupt endpoint etc.). Likely I was doing something wrong.
David Brown
John Homppi wrote:
Long description follows. the code to review is at the end of the message.
===
I have a device that uses interrupt OUT endpoints and I need a Linux driver.
It seems to me that the existing USB driver stack does not support OUTPUT on
interrupt end-points.
Actually
Long description follows. the code to review is at the end of the message.
===
I have a device that uses interrupt OUT endpoints and I need a Linux driver.
It seems to me that the existing USB driver stack does not support OUTPUT on
interrupt end-points.
My device is an Ontrak ADU200
On Mon, May 06, 2002, Daniel Cruz <[EMAIL PROTECTED]> wrote:
> > Daniel Cruz wrote:
> > >
> > > hello,
> > >
> > > I'm sending information to a INT endpoint with using FILL_INT_URB and
> then
> > > submitting the corresponding URB, but I'm not receiving the information
> all
> > > the times I send
> Daniel Cruz wrote:
> >
> > hello,
> >
> > I'm sending information to a INT endpoint with using FILL_INT_URB and
then
> > submitting the corresponding URB, but I'm not receiving the information
all
> > the times I send it, only a very few times the transaction is
succesfull,
> > what could I been
Daniel Cruz wrote:
>
> hello,
>
> I'm sending information to a INT endpoint with using FILL_INT_URB and then
> submitting the corresponding URB, but I'm not receiving the information all
> the times I send it, only a very few times the transaction is succesfull,
> what could I been doing wrong?.
hello,
I'm sending information to a INT endpoint with using FILL_INT_URB and then
submitting the corresponding URB, but I'm not receiving the information all
the times I send it, only a very few times the transaction is succesfull,
what could I been doing wrong?..
Thanks for the help.
On Fri, Mar 30, 2001 at 06:09:00AM +1000, Brad Hards wrote:
> I take it that my interrupt URB completion routine runs in interrupt
> context.
Correct.
> Is is OK to submit any async urb in interrupt context?
It is OK and it was supposed to work like that from the beginning.
> Is it not OK t
I take it that my interrupt URB completion routine runs in interrupt
context.
Is is OK to submit any async urb in interrupt context?
Is it not OK to submit any synchronous (usb_ctrl_msg, usb_bulk_msg) in
interrupt context?
TIA
Brad
___
[EMAIL PROTE
58 matches
Mail list logo
