Hello Tim
On 25/05/2012 18:25, Tim Roberts wrote:
>
> When news of this limitation first came out 5 or 6 years ago, the USB
> team at Microsoft sent out a blast saying "We will add this if you have
> a legitimate use case for it. Let us know." No one has let them know,
> or at least no one that
g...@novadsp.com wrote:
>> please be aware that the Windows driver we use at the
>> moment doesn't support isoch (see "Known Restrictions" for WinUSB at
>> [1]),
> Indeed. Why on earth make WinUSB without isoch support.
Microsoft's answer is because (1) it's hard to abstract it in a
reasonable and
On Fri, May 25, 2012 at 8:12 PM, g...@novadsp.com wrote:
>> The libusb0 and libusbK drivers are signed and work fine on x64.
>
> Yes. Might I ask how this all ties in (if at all) with Zadig? I have
> been using this to great effect for firmware testing (thanks!).
The signing for libusb0.sys and l
On 2012.05.25 13:12, g...@novadsp.com wrote:
>> The libusb0 and libusbK drivers are signed and work fine on x64.
>
> Yes. Might I ask how this all ties in (if at all) with Zadig? I have
> been using this to great effect for firmware testing (thanks!).
Zadig was designed to help Windows users of th
Hello Pete
>
> Note that the code pointed out by Peter is _NOT_ the one that is going
> to be used by libusbx.
>
> The reasons are:
> 1. It is too old (more than 2 years) and hasn't been updated at all
> 2. It doesn't support libusbK, only libusb0
> 3. The author didn't address some shortcomings an
On 2012.05.25 11:46, g...@novadsp.com wrote:
>> Sure, and there is an implementation, but the implementation needed
>> further work before being added into the Windows backend and the
>> author didn't work with Pete on that.
Note that the code pointed out by Peter is _NOT_ the one that is going
t
Hello Pete
> Sure, and there is an implementation, but the implementation needed
> further work before being added into the Windows backend and the
> author didn't work with Pete on that.
>
> My http://git.stuge.se/?p=libusb-stuge.git;a=shortlog;h=libusb0 branch
> has two snapshots of the downstre
On Fri, May 25, 2012 at 3:19 AM, g...@novadsp.com wrote:
> Hello Pete,
>
>> please be aware that the Windows driver we use at the
>> moment doesn't support isoch (see "Known Restrictions" for WinUSB at
>> [1]),
>
> Indeed. Why on earth make WinUSB without isoch support.
It is a low priority for M
g...@novadsp.com wrote:
> Why on earth make WinUSB without isoch support.
I think Microsoft felt that C/B/I was good enough.
> > though we're planning to add drivers that support isoch in the
> > future.
>
> Has anyone started working on this?
Sure, and there is an implementation, but the impl
Hello Pete,
> please be aware that the Windows driver we use at the
> moment doesn't support isoch (see "Known Restrictions" for WinUSB at
> [1]),
Indeed. Why on earth make WinUSB without isoch support.
> though we're planning to add drivers that support isoch in the future.
Has anyone started
Fix to reduce the severity of the log message above has now been pushed
to git.
Regards,
/Pete
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has
On 2012.05.22 16:36, g...@novadsp.com wrote:
> Thanks, your call. I've only been using the library for a few hours, not
> yet noticed the ability to set logging levels.
Yes, basically all of the messages generated by libusbx (if logging is
enabled) are tagged with a severity, and when calling on
Hello Pete
On 22/05/2012 16:21, Pete Batard wrote:
>
> Unless there are objections, I'll produce a patch to do just that.
> Currently, I think I'll go with info, but if anyone has a strong
> preference for another severity level, let me know.
>
Thanks, your call. I've only been using the library
On 2012.05.22 15:25, g...@novadsp.com wrote:
>> That seems to be a USB hub. Is it?
>> http://www.ixitools.com/hwcat/_b8139c20-cf94-11d5-aef7-0002b30625c5_vid_05e3_pid_0608/devinfo19476.html
>
> Good call. It is a hub but it is not showing up as borked in Windows.
> I'll ignore it.
We've been seein
Hello Xioafan
On 22/05/2012 15:15, Xiaofan Chen wrote:
> On Tue, May 22, 2012 at 9:52 PM, g...@novadsp.com wrote:
>
> That seems to be a USB hub. Is it?
> http://www.ixitools.com/hwcat/_b8139c20-cf94-11d5-aef7-0002b30625c5_vid_05e3_pid_0608/devinfo19476.html
>
Good call. It is a hub but it is no
On Tue, May 22, 2012 at 9:52 PM, g...@novadsp.com wrote:
> Agreed. However the complaint is not about my device - the VID/PID is
> for something else. What I'm trying to establish is which slice in the
> stack is sending the warning.
In that case, that is just a warning about another device and
Hello Pete.
>> Fun! Did you already verify the USB part of the firmware, or is this
>> part of what you are doing right now?
Err. Yes :) Blackfin not my favourite for this kind of gig!
USB firmware all good. I want to use libusbx for the bulk pipe in what
will be a composite device. Essentially
Hello Pete.
>> Fun! Did you already verify the USB part of the firmware, or is this
>> part of what you are doing right now?
Err. Yes :) Blackfin not my favourite for this kind of gig!
USB firmware all good. I want to use libusbx for the bulk pipe in what
will be a composite device. Essentially
g...@novadsp.com wrote:
> I've got a custom USB bulk device (Blackfin based with my own firmware
> for what it's worth).
Fun! Did you already verify the USB part of the firmware, or is this
part of what you are doing right now?
> I run xdev face:feed (our VID/PID) and all device info gets repor
19 matches
Mail list logo
