On Mon, Jan 21, 2013 at 11:06 PM, Solovjev P.S. wrote:
> On 21.01.2013 16:56, Xiaofan Chen wrote:
>> Thanks. Now the debug log helps.
>>
>> 1) Firstly this is an USB composite device with 4 interfaces:
>> Interface 0: Audio Control (using control endpoint only)
>> Interface 1: Audio Streaming (EP0
On Tue, Jan 22, 2013 at 5:36 AM, Vern wrote:
> Will libusbx use the BSD License?
>
I do not think so. If you look at the copyright holders, I think it will
be difficult to convince all of them to change to BSD license from
the current LGPL 2.1 license.
https://github.com/libusbx/libusbx/blob/mast
Will libusbx use the BSD License?
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video
On 21.01.2013 16:56, Xiaofan Chen wrote:
> Thanks. Now the debug log helps.
>
> 1) Firstly this is an USB composite device with 4 interfaces:
> Interface 0: Audio Control (using control endpoint only)
> Interface 1: Audio Streaming (EP03, ISOC OUT)
> Interface 2: HID (EP81, Interrupt IN)
> Interfac
To Toby,
I do not know too much about WinCE even though some of our
product do use Intel/Marvell PXA255 and WinCE 5.0 which are
in the process of being redesigned to other RTOS and MPU due to
the obsolescence of PXA255. That product does not have USB.
But I have colleagues working on product which
On Mon, Jan 21, 2013 at 8:04 PM, Solovjev P.S. wrote:
> I sent the files as standard attachments (not as text), but apparently
> github converted attachment to the text.
> zip file attached to this email.
>
> Device descriptors are added to the attachment.
>
> Best result was with libusbx (git) +
On Sun, Jan 20, 2013 at 10:20 PM, Wander Lairson Costa
wrote:
> 2013/1/20 Xiaofan Chen :
>> On Fri, Jan 11, 2013 at 6:37 PM, Wander Lairson Costa
>> wrote:
> [1] https://github.com/walac/isochronous
>
> [2] https://github.com/walac/bmfw
Can your test your firmware against th
On Mon, Jan 21, 2013 at 2:10 AM, Wander Lairson Costa
wrote:
> Finally I found the issue. Indeed the problem was the firmware, I was
> setting up the isochronous endpoint with handshake. I have done some
> raw tests and it feels like it is working. Thank you all.
I see. I think this is a bug in T
