Hello
I meet across some problems, when I port USB Gadget from 2.6 to 2.4 kernel.
I move these files to 2.4 kernel in gadget directory: usbstring.c,
config.c,epautoconf.c ,omap_udc.c and ether.c. There are codes to register
omap_udc driver and ether driver , but there are no codes to
hi,
Is someone know how to get the input and output hid report size ?
I managed to do that under M$, but I don't know how to do with linux !
thanks
fabien M
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September
Hi
I try to upgrade my x2s_usb 2.4 kernel driver
(https://sourceforge.net/projects/x2susbsfwkit) to 2.6.
The system is a prototyping board with ezusb and Xilinx FPGA.
On 2.4 the driver had 6 /dev entries (via devfs)
/dev/x2s/firmware - for FPGA desing update
/dev/x2s/io0 - for first memory
On Tue, 23 Aug 2005, David Brownell wrote:
Considering that _only_ the last byte of that response was garbage,
and the others looked just fine, there's no reason to think this is
anything other than some kind of peripheral bug.
There is indeed such a reason. Craig reported that the device
On Wed, 24 Aug 2005, Peter Urbanec wrote:
Will an USBDEVFS_BULK with
usbdevfs_bulktransfer.len = 0 have the same effect?
In principle it ought to. If the ioctl works then it will have the same
effect. However it might not work, since the usbdevfs code doesn't really
expect to see
On Tue, 23 Aug 2005, Dave North wrote:
Alan Stern wrote:
Have you seen this patch?
http://marc.theaimsgroup.com/?l=linux-usb-develm=112439094723976w=2
This started quite a bit of extracurricular activity (I installed the
patch and enumeration started in 2.6.12.3; previously it would
On Tue, 23 Aug 2005, Singh, Brijeshkumar wrote:
Hi,
Two CD-ROM's (from same vendor) are connected on Linux machine, running
2.4.20 kernel. I am not able to relate the topology of individual CD-ROMs.
# cat /proc/bus/usb/devices
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3
Hi there,
I have installed a sniffer in windows to catch the USB packet sent by the USB
driver on Windows. That is to note what Windows USB driver is doing which my
Linux driver is not doing.
First observation was, for every one byte command it was sending four bytes of
information. That
On Tue, 23 Aug 2005, craig qu wrote:
The log shows everything worked okay (if you ignore
the problem of the
illegal status codes) until the computer tried to do
a 127 KB write. Some
devices don't like to transfer more than 120 KB at a
time, maybe that's
the problem you're seeing
Hi Alan,
Thanks for help.
Unfortunately my system has four USB bus. Hence I am not to use the method you
suggested. I was exploring possibility of adding little additional information
in /proc/scsi/usb-storage-A/B. The information should be something like:
[EMAIL PROTECTED] usb]# cat
I saw an entry in your log where the status was
0xcd. It was for the
second READ_10 command.
You are right. It happens from time to time especially
when read the partition table and mount the device.
However, md5sum a file will give the correct result
always.
Or maybe something fishy
On Wed, 24 Aug 2005, Singh, Brijeshkumar wrote:
Hi Alan,
Thanks for help.
Unfortunately my system has four USB bus. Hence I am not to use the method
you suggested. I was exploring possibility of adding little additional
information in /proc/scsi/usb-storage-A/B. The information should
Alan thanks for quick response.
By index I mean local index variable in drive/usb/device.c [function
usb_device_dump]. As if I understand, the below snippet from
drive/usb/device.c writes topology;
static ssize_t usb_device_dump(char **buffer, size_t *nbytes, loff_t
*skip_bytes, loff_t
On Wed, 24 Aug 2005, Dave North wrote:
On Aug 24, 2005, at 7:17 AM, Alan Stern wrote:
Actually I asked you to set CONFIG_USB_STORAGE_DEBUG=y. It's a
different,
independent setting.
Oh crap. My bad.
I set that, and unset CONFIG_USB_DEBUG=y. Haven't even previously
noted the
On Wed, 24 Aug 2005, Singh, Brijeshkumar wrote:
Alan thanks for quick response.
By index I mean local index variable in drive/usb/device.c [function
usb_device_dump]. As if I understand, the below snippet from
drive/usb/device.c writes topology;
static ssize_t usb_device_dump(char
On Saturday 13 August 2005 2:04 pm, David Brownell wrote:
Among other things, this will speed up the TX path for minidrivers
that need extra headers.
This has a few other minor cleanups now too.
This starts to prepare the core of usbnet to know less about various
framing protocols that map
On Saturday 13 August 2005 2:12 pm, David Brownell wrote:
These run Linux inside, but rather gratuitously they all
break the CDC standards they claim to conform to.
This moves usbnet support for Zaurus and compatibles into its own module.
Other than exporting a couple of helper functions,
On Saturday 13 August 2005 2:09 pm, David Brownell wrote:
The most significant of these being some LapLink products.
This version fixes some problems in the earlier version,
and notes that the chip's EOL notice seems to have been
posted. (I've not seen it, so I don't know if the last
On Saturday 13 August 2005 2:01 pm, David Brownell wrote:
Following this are nine patches to split the usbnet driver into
smaller driver modules wrapped around the reusable core, adding
the RNDIS driver along the way. This makes it easier to maintain,
and reduces the memory footprint by not
On Saturday 13 August 2005 2:07 pm, David Brownell wrote:
Sometimes it's almost trivial to write a driver ... so in a feat of
apalling lack-of-originality they go into simple.c.
The more appropriate name, this time around, is cdc_subset.c.
This patch creates the first of several separate
On Saturday 13 August 2005 2:13 pm, David Brownell wrote:
This supports various cable modems and Linux-USB gadgets,
and exports functions used by some proprietary protocols.
Makes the CDC Ethernet support live in a separate driver module.
This module is a bit special since it exports utility
On Saturday 13 August 2005 2:18 pm, David Brownell wrote:
This driver is EXPERIMENTAL, new, and only lightly tested.
But it ought to be useful. :)
Renamed from rndis.c to rndis_host.c; that's clearer,
even if the old name is _not_ the cause of those strange
linker problems on older systems.
On Saturday 13 August 2005 2:19 pm, David Brownell wrote:
This should still be bug-compatible with the Linux 2.2 code, but
it'd be nice if someone finally sorted out the handshaking issues.
This wraps up the conversion of the usbnet driver structure, by
moving the Prolific PL-2201/2302
From: Дмитрий Сергеев [EMAIL PROTECTED]
Date: Wed, 24 Aug 2005 09:12:59 +0400
Hello.
I try connect my ARM linux device to host with Windows XP by USB serial
gadget ACM.
Driver setup normally, and my device is detected properly.
But I don`t know how to send data and receive data? All
From: Subhash Reddy Peddamallu [EMAIL PROTECTED]
Date: Fri, 19 Aug 2005 13:48:12 -0400 (EDT)
I recently implemented a platform bus glue for on-chip EHCI host
controller (ARCs EHCI) which has roothub with built in TT. This uses most
of the existing EHCI driver code. When I built kernel with
From: driversbin driversbin [EMAIL PROTECTED]
To: [EMAIL PROTECTED],
linux-usb-devel@lists.sourceforge.net
Subject: [linux-usb-devel] usbnet: no pings
Date: Tue, 23 Aug 2005 01:38:13 -0700 (PDT)
You do know that cross-posting to large lists is
not appreciated, right? Hence my
From: zhouyf [EMAIL PROTECTED]
Subject: [linux-usb-devel] [help] porting USB Gadget from 2.6 to 2.4 kernel
Date: Wed, 24 Aug 2005 16:56:49 +0800
Hello
I meet across some problems, when I port USB Gadget from 2.6 to 2.4 kernel.
I move these files to 2.4 kernel in gadget directory:
From [EMAIL PROTECTED] Thu Aug 18 23:01:46 2005
From: Дмитрий Сергеев [EMAIL PROTECTED]
To: linux-usb-devel@lists.sourceforge.net
Subject: [linux-usb-devel] Linux USB Ethernet Gadget/RNDIS connection to
Windows Host problem
Date: Fri, 19 Aug 2005 09:51:07 +0400
Hello, everybody!
I am
Date: Fri, 19 Aug 2005 14:13:08 -0400 (EDT)
From: Alan Stern [EMAIL PROTECTED]
There was a discussion about this a while back, but I can't locate the
messages in the archives or remember what the objections were.
The only objections I recall were someone needs to make the
time to change
From: driversbin driversbin [EMAIL PROTECTED]
Date: Tue, 23 Aug 2005 01:38:13 -0700 (PDT)
Hi,
I am using host-host cable having prolific chip with
vendor id 0x067b and product id 0x0001.i am using
2.6.11 kernel patched with 2.6.12-rc5 patch.
I have enabled , USB gadget support
From: xiaohuaw [EMAIL PROTECTED]
Date: Thu, 18 Aug 2005 18:16:09 +0800
What's the pre-compilation* option with *driver/usb/gadget/ether.c to
implete usbnet under linux.
Erm, there's the Kconfig CONFIG_USB_ETH option, which is the only
pre-compilation option. (Other than adding RNDIS
On Wed, 24 Aug 2005, David Brownell wrote:
Date: Fri, 19 Aug 2005 14:13:08 -0400 (EDT)
From: Alan Stern [EMAIL PROTECTED]
There was a discussion about this a while back, but I can't locate the
messages in the archives or remember what the objections were.
The only objections I
I've been experimenting with the OHCI interface on the Zaurus SL-C3000
(Spitz) and have found a few things I wouldn't mind opinions on.
I'll even correlate them to your questions. :)
Firstly, the NDP register in roothub.a on the PXA270 isn't standard and
the number of ports is really the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Stern wrote:
You can get more information by turning on the USB Mass-Storage verbose
debugging option in the kernel configuration (CONFIG_USB_STORAGE_DEBUG)
and rebuilding the usb-storage driver. That will add lots of debug info
to the
Alan, thanks for input.
I made the respective changes in scsiglue.c for displaying bus and
device number.
driver/usb/storage/scsiglue.c as follows:
static int proc_info (char *buffer, char **start, off_t offset, int
length,int hostno, int inout)
{
SPRINTF(Bus:
Alan:
I mean occasionally I get kernel oops. The proc_info () looks as below
static int proc_info (char *buffer, char **start, off_t offset, int
length,
int hostno, int inout)
{
struct us_data *us;
char *pos = buffer;
/* if someone is sending us data,
Alan,
I fixed the problem. It was my logical mistake. One can access
bus/device number _only_ when device is connected hence I need to do
something like
If(us-pusb_dev) {
/* show device topology field */
SPRINTF( Bus: %d\n,us-pusb_dev-bus-busnum);
SPRINTF(
My original reply to this doesn't seem to have made it to the list...
From: vishal [EMAIL PROTECTED]
Subject: [linux-usb-devel] USB OTG Patches for Linux 2.6.X ???
Date: Thu, 11 Aug 2005 13:05:20 +0530
Hi All,
I am wondering if there are any on going efforts to implement USB OTG
38 matches
Mail list logo
