Hi Frank,
Just a couple of comments (see below)...
Frank Pagliughi wrote:
>When a bulk IRP involves more data than can fit in one maximum-sized
>data payload, all data payloads are required to be maximum size
>except for the last data payload, which will
>contain the remaining da
I guess the problem in my case is that the host is reading multiple
sectors of the mass storage device in a single READ and I am sending
sector by sector so the USB driver is inserting the empty packet in
between sectors since it thinks this is the end of the transfer (and the
sector size is a mult
Actually the behavior for Bulk Transfers is defined in section 5.8.3 of
the USB 2.0 standard, entitled, "Bulk Transfer Packet Size Constraints."
It states:
When a bulk IRP involves more data than can fit in one maximum-sized
data payload, all data payloads are required to be maximum size
Hi Sergei,
Am Dienstag, den 29.06.2010, 15:16 +0300 schrieb Sergei Gavrikov:
> On Tue, 29 Jun 2010, Manuel Borchers wrote:
> cdl_option CYGPKG_DEVS_ETH_ARM_NETX_CFLAGS_ADD {
> display "Additional compiler flags"
> flavor data
> no_define
>
On Tue, 29 Jun 2010, Manuel Borchers wrote:
Hi all,
when trying to build a network stack (OpenBSD) into my kernel, I
struggled over a missing define.
When building I got:
-- SNIP --
In file included
from
/home/manuel/Arbeit/netX-ACCOS/netx_accos/trunk/src/ecos/work/netx500_ram_standalone_eth/
Hi all,
when trying to build a network stack (OpenBSD) into my kernel, I
struggled over a missing define.
When building I got:
-- SNIP --
In file included
from
/home/manuel/Arbeit/netX-ACCOS/netx_accos/trunk/src/ecos/work/netx500_ram_standalone_eth/install/include/cyg/io/eth/eth_drv.h:62,
from
Hi Chris,
Thank you for clarifying that for me. I could not yet find any info
about the expected behavior of the bulk storage class drivers to empty
packet. I found that empty packet can be used in some specific cases but
nothing about termination of a regular data transfer phase. I think I
will i
