On Monday 30 April 2007, Meher wrote:
>Then application will not even bother if he is a USB
> device or on board flash and just do the normal read/write from
> /dev/flashd?
"flashd" is some wierd new convention it seems. There are two basic
models for flash memory on Linux.
- The "nat
> >
> > > When application does a read or even mount of the flash device
how
> > > is that information passed on to the device driver so that it can
> > > convert that to specific Ctrl/Bulk transfer types and pass it on
to
> > > HCD?
> >
> > I believe the driver stack will look something like
Hi,
On 4/30/07, Curran, Dominic <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> > I would like to know if there is any specific API that will be
> > used by the Applications that read/write to USB devices. For example
> > if a flash device is plugged into a system then the HCD will enumerate
> > the d
>
> > When application does a read or even mount of the flash device
how
> > is that information passed on to the device driver so that it can
> > convert that to specific Ctrl/Bulk transfer types and pass it on to
> > HCD?
In my haste I forgot to put in usb-storage...
I believe the dr
> Hi,
> I would like to know if there is any specific API that will be
> used by the Applications that read/write to USB devices. For example
> if a flash device is plugged into a system then the HCD will enumerate
> the device and load the appropriate device driver for that flash
> device to
On Mon, 30 Apr 2007, Meher wrote:
> Hi,
> I would like to know if there is any specific API that will be
> used by the Applications that read/write to USB devices. For example
> if a flash device is plugged into a system then the HCD will enumerate
> the device and load the appropriate device
