30 Jan
2014
30 Jan
'14
10:47 p.m.
That does make sense to me since I had issues where before I changed the
usb header, the host was sometimes merging multiple req_ctx into a single
usb read.
I am attaching a tar.gz file containing all my changes as separate git
commits / format-patches and hopefully it will get committed to the
repository. This includes the latest change to the usb header as well as a
change (as Peter suggested) to the bDeviceProtocol in
usb_descriptors_openpcd.h, setting the new value to 0.
Best Regards
On Thu, Jan 30, 2014 at 6:21 AM, Dean Chester <dean.g.chester(a)gmail.com>wrote;wrote:
It was mostly the lost bytes/scrambled data with a
variety of handsets
that i'd tested with, compared with ubuntu running natively.
Dean
On 27 January 2014 18:37, Min Xu <mxu(a)sanjole.com> wrote:
P.S. What problems were you experiencing of it
running in a virtualized
system, can you elaborate?
Thanks
On Mon, Jan 27, 2014 at 8:36 AM, Min Xu <mxu(a)sanjole.com> wrote:
I am contributing it to the project. Once I
incorporate Peter Stuge's
suggestion, hopefully within the next few weeks I will submit another
commit.
Best Regards
On Mon, Jan 27, 2014 at 1:05 AM, Dean Chester <dean.g.chester(a)gmail.com>wrote;wrote:
Thanks Min it works a treat it also fixes the
issues running in a
virtualised environment which I do for Ubuntu.
Is your new firmware under the same licence as the original?
Kind Regards,
Dean Chester
On 24 January 2014 21:55, Peter Stuge <peter(a)stuge.se> wrote:
> Min Xu wrote:
> > I would be happy to send them the USB protocol changes. However,
> > it will be INCOMPATIBLE with earlier firmware based SIMTrace boards.
>
> There is a standardised way to deal with protocol changes in USB;
> change either the bDeviceProtocol field in the device descriptor or
> the bInterfaceProtocol field in the interface descriptor, and make
> host software do the appropriate thing based on the descriptors of
> the connected device.
>
> Of course only new host software will work with the new protocol, but
> this way new host software still continues to work with the old
> protocol.
>
>
> //Peter
>
>