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@sanjole.com> wrote:P.S. What problems were you experiencing of it running in a virtualized system, can you elaborate?
ThanksOn Mon, Jan 27, 2014 at 8:36 AM, Min Xu <mxu@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@gmail.com> 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 ChesterOn 24 January 2014 21:55, Peter Stuge <peter@stuge.se> wrote:
There is a standardised way to deal with protocol changes in USB;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.
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