Hello,
We had the following questions for a peripheral controller driver. We
do have an idea about some of the answers, evidently our understanding
is not complete.
1. The gadget can ask the peripheral controller to send/receive zero
byte packets. Consider the following sub-cases:
a) req.
Hi,
I have these questions regarding the peripheral controller driver.
1. When the gadget driver queues a request for the EP0, how does one
get to know whether it is an "IN" request or an "OUT" request. I was
looking at a few implementations and I came across the following code:
if (ep_is_in(ep)
Hello,
I have a question regarding USB Gadget Implementation. The question is
regarding the zero byte packets that are sent/recvd during USB
Transfers. Assuming that I have my own peripheral driver, and am using
a mass storage functionality on it. Who is responsible to send zero
byte packets in th
> g_file_storage reads and writes data to/from the card, as you would
> expect.
> > Is there some user-space daemon running?
> Only if you start one up.
Got it, just one point for discussion. I just saw the file storage
code and realized that things are implemented as a kernel thread and
the read/
Hello,
We are implementing a USB peripheral controller driver for our
proprietary hardware, an ARM based SOC. I have read the Linux gadget
page on the linux usb website. A few things that I could conclude
were:
1. We should be using the Linux gadget framework for the same, like
the way its done f
> > I have a usb hardware on my ARM based board. I want to develop a usb
> > function driver so that I can view the file-system on the host side. I
> > guess such kind of functionality is exposed in the mass-storage class.
>
> No.
>
> > Can somebody guide me as to how to proceed? Are there any samp
Hello,
I have a usb hardware on my ARM based board. I want to develop a usb
function driver so that I can view the file-system on the host side. I
guess such kind of functionality is exposed in the mass-storage class.
Can somebody guide me as to how to proceed? Are there any sample
drivers availab
Hi,
The windows host enumerates my proprieatry device (running linux & my
driver) in the following sequence:
1. Reset
2. Get Dev Desc 64 bytes
3. Reset
4. Set Address
5. Get Dev Desc 18 bytes
6. Get Config Desc 9 bytes
7. Get Config Desc 0xff bytes
8. Get Device Qualifier Desc
9. Get Dev Desc 18
On 7/11/06, Steve Calfee <[EMAIL PROTECTED]> wrote:
> > >Date: Mon, 10 Jul 2006 20:07:05 +0530
> > >From: "Ajay Jain" <[EMAIL PROTECTED]>
> > >To: linux-usb-devel@lists.sourceforge.net
> > >Hi,
> > >Am using a windows host and a
Hi,
I am seeing a very very strange behavior. I ported linux-2.6.14 on our
platform & the Makefile confims its version number. Then sometime back
I had to download the raw source again from kernel.org. I see that the
usb directories of both the versions differ remarkably. The
differences are attach
On 7/11/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Jul 2006, Ajay Jain wrote:
>
> > > Remember the definitions of reset and suspend. Reset is an SE0 signal,
> > > which is the default bus state when no device is attached or the device's
> >
On 7/10/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 10 Jul 2006, Ajay Jain wrote:
>
> > Hi,
> > Am using a windows host and a proprietary device as a function. This
> > is the pre-enumeration stage that I am talking about. I see a very
> > different
Hi,
Am using a windows host and a proprietary device as a function. This
is the pre-enumeration stage that I am talking about. I see a very
different behavior with what is written in the standard or with the
way windows is supposed to enumerate. The following are the
observations with CATC protocol
Hi,
I am writing a usb function driver for our own usb h/w. I am not very
clear on what is to be done when I receive a reset, suspend & resume.
What is expected from my driver/device when I detect a reset given by
windows host, similarly what should be my behavior on suspend. And
what about resume.
Hi,
We are using usb function exposed as a serial device. It is our own
proprietary hardware (running linux) exposed as a serial device. The
host side (windows) identifies our serial device with the driver
"wceusbsh.sys". The enumeration goes successfully and we get to see
our device in the device
Greg KH wrote:
> On Wed, Dec 14, 2005 at 02:30:46PM -0800, Ajay Jain wrote:
>
>>Hi,
>>
>>I am doing bulk out transfers using my own usb host-controller driver on
>>linux 2.4.21. The device being used is a usb-serial device of type pl203.
>>I sometimes see tha
Hi,
I am doing bulk out transfers using my own usb host-controller driver on
linux 2.4.21. The device being used is a usb-serial device of type pl203.
I sometimes see that I get all packets of size zero for a bulk out
transfer, after an initial valid size. I complete the first bulk
transfer succes
Ajay Jain wrote:
> I am using my own usb host driver and trying to run a serial device on
> that. 1 out of 5 times, I get an error "kernel panic, aiee, scheduling
> in interrupt handler". The device in question is pl2303. From
> usbserial.c, the function serial_write_roo
Hi,
I am using my own usb host driver and trying to run a serial device on
that. 1 out of 5 times, I get an error "kernel panic, aiee, scheduling
in interrupt handler". The device in question is pl2303. From
usbserial.c, the function serial_write_room is called. The error comes
on doing
do
Hi,
I am working on usb host driver on linux on arm. I have been able to
enumerate a standard key board and carry out the interrupt transactions.
I can see the data coming from the keyboard in the usb host driver's
isr. I want to see the same data on my console also. My console is
diverted to ttys
Ajay Jain wrote:
> Hi,
>
> I am working on a USB host driver on my proprietary h/w on linux 2.4. I
> am facing issues after enumeration of a key board. I see that the client
> driver gets loaded and I get the following messages.
>
> hid-core.c: HID probe called for ifnum 0
Hi,
I am working on a USB host driver on my proprietary h/w on linux 2.4. I
am facing issues after enumeration of a key board. I see that the client
driver gets loaded and I get the following messages.
hid-core.c: HID probe called for ifnum 0
input0
hid-core.c: USB HID v1.00 Keyboard [Silitek IBM
Alan Stern wrote:
> On Thu, 24 Nov 2005, Ajay Jain wrote:
>
>
>>Alan Stern wrote:
>>
>>
>>>On Wed, 23 Nov 2005, Ajay Jain wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I am doing a USB Host driver for my h
Alan Stern wrote:
> On Wed, 23 Nov 2005, Ajay Jain wrote:
>
>
>>Hi,
>>
>>I am doing a USB Host driver for my h/w on an arm board on linux. My
>>question is regarding interrupt urbs. Are these things periodic? I mean
>>if I get an interrupt urb done from
24 matches
Mail list logo
