I have been testing the g_serial serial gadget with my superh_udc driver
on the 2.4.21 kernel. It works when I send data from the host to the
device but when I send from the device to the host I get extra characters.
Example:
device# echo 1234 /dev/ttygs0
host# cat /dev/usb/tts/0
1234
1^
Mahlzeit
I am currently testing the cyberJack driver under 2.6.0-test9 and
get following message:
Debug: sleeping function called from invalid context at include/asm/uaccess.h:498
in_atomic():0, irqs_disabled():1
c011b3c1: __might_sleep+0x91/0xb0
c783c67f: cyberjack_write+0x3df/0x4d0
c784b501:
Julian --
Julian Back wrote:
I have been testing the g_serial serial gadget with my superh_udc driver
on the 2.4.21 kernel. It works when I send data from the host to the
device but when I send from the device to the host I get extra characters.
Example:
device# echo 1234 /dev/ttygs0
I suspect, that this might_sleep is the one called in copy_from_user().
Is the problem, that this is called inside a spin_lock_irqsave-section?
Do I have to use a local buffer in cyberjack_write, then call the
copy_from_user and the start the spin_lock_irqsave-section to copy it
into the
Al Borchers wrote:
Be sure echo is turned off, use stty -echo /dev/ttyUSB0
on the host side and stty -echo /dev/ttygs0 on the device
side. (The device names may not be quite right, I don't have
time right now to check.)
I have seen similar symptoms caused by each side echoing
characters bounce
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
Hello all,
First, a disclaimer - I am very new to driver development, so please
bear with my ignorance.
I am trying to write a device driver for a USB U401 from usbmicro.com.
The device works by sending a control packet to the device, then
receiving an interrupt packet back. I have (I think)
On Tuesday 11 November 2003 15:20, Al Borchers wrote:
host# cat /dev/usb/tts/0
1234
1^
I have seen similar symptoms caused by each side echoing
characters bounce back and forth.
Yes, that was my guess as well, but his log shows another problem i've been
facing as well: Only the first
Greg KH wrote:
That number is used because it is not a device number of any shipping
device. You should not use that device id for your device, as you are
not PSC :)
I've just pushed new vendor/product ids (0x0525/0xa4a6) into the
gadget-2.4 and gadget-2.6 BK trees, at usb-gadget.bkbits.net, so
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,
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
Hi,
I have a Pioneer DVR-106 drive housed in an external USB housing which uses the ALI
m5621 IDE-USB chipset. This connects to the PC via a NEC based USB2.0 PCI card.
Whenever I try and burn a DVD the unit fails after a few minutes. I enclose some debug
information below - please let me know
Hi all,
I am a hardware design Engineer and I am new to USB. I am designing a board
which should support a hi-speed(480Mbps) USB host controller. The board will
run linux, hence I would be requiring a host controller for which linux
driver is available. I found Philips 1561 to suit the
I am in the process of writing a device driver for a device which is a
combination vacuum flourescent display and ir receiver. The driver is
functional, but has some problems.
The device has a single configuration, and single interface with 2 endpoints.
The endpoints are transfer type
On Tue, 11 Nov 2003, Ian R. Meinzen wrote:
Hello all,
First, a disclaimer - I am very new to driver development, so please
bear with my ignorance.
I am trying to write a device driver for a USB U401 from usbmicro.com.
The device works by sending a control packet to the device, then
On Tue, 11 Nov 2003 [EMAIL PROTECTED] wrote:
Hi,
I have a Pioneer DVR-106 drive housed in an external USB housing which
uses the ALI m5621 IDE-USB chipset. This connects to the PC via a NEC
based USB2.0 PCI card.
Whenever I try and burn a DVD the unit fails after a few minutes. I
On Tue, 11 Nov 2003, Henry Culver wrote:
I am in the process of writing a device driver for a device which is a
combination vacuum flourescent display and ir receiver. The driver is
functional, but has some problems.
The device has a single configuration, and single interface with 2
On Tue, 2003-11-11 at 15:23, Alan Stern wrote:
On Tue, 11 Nov 2003, Henry Culver wrote:
I am in the process of writing a device driver for a device which is a
combination vacuum flourescent display and ir receiver. The driver is
functional, but has some problems.
The device has a
Alan,
Thanks for taking timeout to reply.
SNIP
For all the world it looks like your USB connection has
gone dead, except that there's no disconnection
notification in the log. It would be interesting to see
what happened next; the log shouldn't have stopped
there.
That's the final entry
Replying to my own post ...
I've found a way to make my code work without having to
deallocate / reallocate the urb.
It seems that after a successful call, urb-dev is getting set to 0.
In my write_callback routine I simply re-set urb-dev to its correct
value (which is stored in the private
Alan Stern wrote:
On Tue, 11 Nov 2003, Ian R. Meinzen wrote:
Hello all,
First, a disclaimer - I am very new to driver development, so please
bear with my ignorance.
I am trying to write a device driver for a USB U401 from usbmicro.com.
The device works by sending a control packet to the
21 matches
Mail list logo
