On Thu, 2005-07-07 at 11:10 +0530, Conio sandiago wrote:
> Can anyone please clarify , what is a ZERO gadget driver concept
See http://www.linux-usb.org/gadget/
Ian.
--
Ian Campbell
Current Noise: Rotting Christ - Visions Of A Blind Order
No problem is so large it can't be fit in somewhere.
Hi all,
I'm new to USB so I thought I'd dip my toe in
the water via usbfs. I'm trying to send a range
of buffer sizes using bulk transfers. When
submitting lots of very small buffers (64 byte
up to about 1k) I'm finding that the fastest
rate I can submit is about 325 per second.
Just to check tha
OK we are narrowing this down.
If I put the ctrl transfers in my driver at the PROBE they work but the
ISO transfers still fail with a -84 at the transfer buffer level in the
call back.
I wrote a script to access the device via DEVFS and generate similar
messages to the VMware log. As you can see
On Thu, 7 Jul 2005, Roel kluin wrote:
> I have applied the patch to the 2.6.13-rc1-mm1 kernel. As you can in
> the last line of my supplied dmesg the "midi: probe of 4-1:1.0 failed
> with error -5" message is still in my dmesg, but the problem with the
> mass storage device seems solved.
There's
On Thu, 7 Jul 2005, Luca Risolia wrote:
> Hello,
>
> Frames from isochrnous transfers report error code -45, which
> is "Level 2 not synchronized".
>
> Could you explain the meaning of that error and the possible
> reasons why it happens?
It looks like something relatively new in the EHCI driv
On Thu, 7 Jul 2005, Jason Flynn G7OCD wrote:
> Hi all,
> I'm new to USB so I thought I'd dip my toe in
> the water via usbfs. I'm trying to send a range
> of buffer sizes using bulk transfers. When
> submitting lots of very small buffers (64 byte
> up to about 1k) I'm finding that the fastest
>
On Thu, 7 Jul 2005, Jonathan Selby wrote:
> OK we are narrowing this down.
>
> If I put the ctrl transfers in my driver at the PROBE they work but the
> ISO transfers still fail with a -84 at the transfer buffer level in the
> call back.
>
> I wrote a script to access the device via DEVFS
You m
I have one driver serving 4 devices at a time. Can't I have one fixed
minor number for one device ?
When read() / write() into the device, how can I know which device I
am operating on ? Right now (in 2.4) I use the minor number of the
node to find out which one I am working on. Please bear wit
Hi all,
I have to integrate a host controller into Linux. This HC is very different
from {U,E,O}HCI ones.
For example, each end of transactions generate an interrupt to allow software
to initiate the start of the next transaction. There is no frame list (like
in UHCI) which allows to link transa
Hi,
moreau francis writes:
> I have to integrate a host controller into Linux. This HC is very different
> from {U,E,O}HCI ones.
>
> For example, each end of transactions generate an interrupt to allow software
> to initiate the start of the next transaction. There is no frame list (like
> in UH
Hi all,
I am using an XScale-Board (PXA255) with arm linux 2.4.19-rmk7-pxa1 (for
some reason, i know its ancient ;-)). I want to develop a usb gadget
driver to communicate with the xscale-board. Hence the question:
Is there any backport of the usb-gadget framework for 2.4.19 kernels?
Any hin
このメールは下記事業者・送信者が送信しております。
<事業者><送信者>(株) GSS inc
住所:東京都世田谷区等々力5-20-12
TEL 03-6425-2181(担当:木村)
MAIL [EMAIL PROTECTED]
特定商取引法施行規則 受け取りを希望しない場合の連絡方法
関係のない方に届きました場合お詫び申し上げます。今後一切の配信を
Sure, and I'll send this mail to the list so that the developers can see
that I'm not the only one with this issue. My guess is that it's a memory
map issue of some sort, and that the bios or kernel is mistakenly protecting
an area of RAM that the USB driver is trying to use. If I knew what ad
On Thu, 7 Jul 2005 [EMAIL PROTECTED] wrote:
> I've not been posting a lot since my current mailer config seems
> to be making linux-usb-devel reject posts to the list; happened
> rather suddenly about a week ago, unclear what changed, so I've
> been lazy tracking it down.
>
> So I suspect this wo
On Thu, Jul 07, 2005 at 10:18:37AM -0700, [EMAIL PROTECTED] wrote:
> > From: Alan Stern <[EMAIL PROTECTED]>
> > Date: Thu, 7 Jul 2005 10:08:39 -0400 (EDT)
> >
> > On Thu, 7 Jul 2005, Luca Risolia wrote:
> >
> > > Hello,
> > >
> > > Frames from isochrnous transfers report error code -45, which
> >
Greg:
This patch handles a rarely-encountered failure mode in usbcore. It's
legal for device_add to fail (although now it happens even more rarely
than before since failure to bind a driver is no longer fatal). So when
we destroy the interfaces in a configuration, we shouldn't try to delete
On Thu, 7 Jul 2005 [EMAIL PROTECTED] wrote:
> > if (start < now)
> > start += mod;
> >
> > Meant to handle sequence-space wrap-around? Does this handle actual
> > overruns correctly?
>
> What do you mean by "overrun"? It's arithmetic modulo "mod";
> and
From: Tobias Klauser <[EMAIL PROTECTED]>
The following patch removes unneeded casts for the following (void *) pointers:
- tty_struct->driver_data
- void *private argument of usb_serial_port_softint()
Signed-off-by: Tobias Klauser <[EMAIL PROTECTED]>
Signed-off-by: Domen Puncer <
Supply large quantity Telecom products with low price: Fiber optic jumper, UTP
Cat5e cable, patch cable, USB cable, Phone cable and various Telecom components.
Details pay a visit to: www.sgetek.com. Download our catalogue from:
www.sgetek.com/order.asp.
Please contact with us by: [EMAIL PROTEC
Begin forwarded message:
Date: Thu, 7 Jul 2005 23:28:26 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 4863] New: kernel opps when removing usb-stick
http://bugzilla.kernel.org/show_bug.cgi?id=4863
Summary: kernel opps when removing usb-stick
Ke
20 matches
Mail list logo