> This must have been a high-speed connection -- there's no way to get those
> transfer rates using full-speed!
>
> I don't know why g_file_storage is slower than g_ether. There are many
> factors that could be involved, both on the host and on the gadget. For
> instance, Windows might waste a
Add .owner initialisation to the device drivers
in drivers/usb/host so that when built as module
the device_driver refers to the owning module
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
diff -urN -X ../dontdiff linux-2.6.14-rc3-git8/drivers/usb/host/ehci-hcd.c
linux-2.6.14-rc3-git8-usb/drivers
Initialise the .owner field of the driver with
the module that owns it, to aid in linking
drivers to modules.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
--- linux-2.6.13-simtec3a/drivers/usb/host/ohci-s3c2410.c 2005-10-02
18:48:15.0 +0100
+++ linux-2.6.13-simtec3b/drivers/usb/host
On Sun, 9 Oct 2005 17:22:39 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> But when would you call kthread_start?
> What happens if the thread calls request_module too soon?
I did not see an oops or deadlock, but the storage module fails to
resolve symbols which it needs from libusual, such
On Sun, 9 Oct 2005, Pete Zaitcev wrote:
> > I converted libusual to use the kthread API.
>
> Hmm. The new API looks promising with the explicit starting and
> stopping. This is a good idea, but I have to revisit it separately.
I'm not sure that the explicit starting will help you very much.
On Sun, 9 Oct 2005, Alan Stern wrote:
> On Sun, 9 Oct 2005, jinzhcheng wrote:
>
> > Hello!
> >
> > I have some question about file-storage gadget function, and can you
> > help me? Thank you!
> >
> > I used linux-2.4.31/usb/gadget/file-storage function to connect my
> > omap730 board to winxp,
On Sun, 9 Oct 2005 12:47:33 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> When assigning the flags value in usb-storage, the extra
> usb_usual module-type information should be masked out.
OK
> Apparently ub's probe routine won't accept any devices unless
> libusua
Hi everybody,
I boughta Logitech Quickcam Fusion in the hope that it would comply with the
USB Video Class, as the comments in the Windows drivers seemed to imply:
lvuvc.sys=1 ; USB Video Class driver
lvmjpeg.sys= 1 ; MJPEG kernel decoder
Unfortunately, the camera reports a vendor class.
Hi!
I have acquired a PCMCIA CardBus USB2.0 controller. It came with a power
cable whose one end plugs into the fat part of the card that sticks out
and has the USB plugs on it, and the other end plugs into a USB port.
I plugged everything in (the card into the PCMCIA slot and the power
adaptor a
On Sun, 9 Oct 2005, jinzhcheng wrote:
> Hello!
>
> I have some question about file-storage gadget function, and can you
> help me? Thank you!
>
> I used linux-2.4.31/usb/gadget/file-storage function to connect my
> omap730 board to winxp, and now i can transfer files from winxp host to
> my SD C
On Sat, 8 Oct 2005, Pete Zaitcev wrote:
> This patch adds a shim driver libusual, which routes devices between
> usb-storage and ub according to the common table, based on unusual_devs.h.
> The help and example syntax is in Kconfig.
>
> Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
>
> ---
>
On Sun, 9 Oct 2005, Duncan Sands wrote:
> Hi Alan, thanks for your clear answer.
>
> > > The max packet size of the iso in endpoint is 640 bytes.
> > > The data comes in as successive 53 byte long "ATM cells".
> > > So I set the iso packet length to 636 bytes, which is
> > > a multiple of 53. Ho
Hi Alan, thanks for your clear answer.
> > The max packet size of the iso in endpoint is 640 bytes.
> > The data comes in as successive 53 byte long "ATM cells".
> > So I set the iso packet length to 636 bytes, which is
> > a multiple of 53. However I regularly see iso packets
> > with actual len
On Sun, 9 Oct 2005, Duncan Sands wrote:
> The max packet size of the iso in endpoint is 640 bytes.
> The data comes in as successive 53 byte long "ATM cells".
> So I set the iso packet length to 636 bytes, which is
> a multiple of 53. However I regularly see iso packets
> with actual length 636 a
The max packet size of the iso in endpoint is 640 bytes.
The data comes in as successive 53 byte long "ATM cells".
So I set the iso packet length to 636 bytes, which is
a multiple of 53. However I regularly see iso packets
with actual length 636 and status -EOVERFLOW (uhci host
controller). Presu
On Sat, 8 Oct 2005 19:14:13 -0700, Matthew Dharm <[EMAIL PROTECTED]> wrote:
> But, I'm not sure this is much better. It's certainly different, but I
> fear that we're going to spend a lot of time explaining to end-users a new
> and less-than-totally-obvious system.
Devices continue to default to
16 matches
Mail list logo
