Ref to Tim's question to OSR NTDEV list and the answer from Microsoft.
http://www.osronline.com/showthread.cfm?link=251465
There is no new WinUSB coinstaller in the 8.1 kit to install downlevel. nothing
in there is tied to
strictly to umdf, so that is not the reason there is no downlevel in
Closed #162 via 805cc3ec40b5b6314e8cef8fb8cd9f8d4e95f293.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/162--
Rapidly troubleshoot problems before they affect your business.
I appreciate it. I can certainly help with updates or requests w.r.t. VS2013,
especially if there is notification e.g. "I updated X project, please sync
others". I just didn't want to sign up as a full maintainer at this stage.
---
Reply to this email directly or view it on GitHub:
https://githu
@pbatard Fair enough! Thanks for explaining. I wasn't trying to be pushy or
jump in line. Just wanted to make sure I was on the right track for getting the
enhancement into the main repo, eventually.
So libusb and libusbx are going to unfork and become one project again? Were
all the philosophi
On Thu, 12 Dec 2013, Tim Roberts wrote:
> Hans de Goede wrote:
> >
> > "the isoc endpoint is only created when changing to alt setting 1"
> >
> > Ah, that is what saves your bacon then, most devices have the isoc eps
> > in altsetting 0 too, with a maxpacketsize of 0.
> >
>
> No, they don't. Or
OK, if it's that much of an annoyance to you, I'll add the VS2013 project files.
However, I may ask you to update them if we change options or add new sources
in VS2012.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/162#issuecomment-30462966--
> What is the libusb/libusbx merge? Pulling changes from libusb into libusbx,
> or the other way, or both?
It's merging libusbx and libusb back together into a single website, git
repository and so on. This is something that we'd said we'd do more than 9
month ago, so now's probably a good time
> Pete wrote:
> Well, if I'm the one doing it, integration of libusbK isoc support is not
> going to happen before libusb and libusbx are merged back and Windows hotplug
> support is in.
> Considering that I had to leave Windows hotplug on standby for a few months
> now (I'll come back to it onc
> > Those components have dependencies on other Win 8.1 components, so they
> > cannot be copied to earlier systems.
Which is fine and all, but still doesn't say much about whether a Windows 7
compatible version of the ISOC WinUSB driver could be sorted out, if Microsoft
really wanted to...
lib
I understand you want to avoid sync issues and don't expect any maintainers
will be using VS2013.
> Your second proposal is pretty much the same as the first one, but in
> disguise (instead of having 2x the vcxproj files, with half of them going
> untested, we have vcxproj files that are twice
Tim Roberts wrote:
> Pete Batard wrote:
>>
>> Now that I think about it, and especially as I still have some hope
>> that it might be possible to pick the Windows 8.1 WinUSB driver and
>> install it on Windows 7 & Windows 8.0 machines, the right way to find
>> if WinUSB isoc is supported is to use
> I'm not sure it's that easy, and I'll tell you why.
That would explain why I've been having all the trouble in the world getting
Windows 7 accept the Windows 8.1 WinUSB driver and DLL last time I tried it
(can't remember the error I was getting, but Windows 7 sure didn't seem happy
with it).
Hans de Goede wrote:
>
> "the isoc endpoint is only created when changing to alt setting 1"
>
> Ah, that is what saves your bacon then, most devices have the isoc eps
> in altsetting 0 too, with a maxpacketsize of 0.
>
No, they don't. Or at least they aren't supposed to. Alt setting 0
should not
Pete Batard wrote:
>
> Now that I think about it, and especially as I still have some hope
> that it might be possible to pick the Windows 8.1 WinUSB driver and
> install it on Windows 7 & Windows 8.0 machines, the right way to find
> if WinUSB isoc is supported is to use |GetProcAddress()| on the
"the isoc endpoint is only created when changing to alt setting 1"
Ah, that is what saves your bacon then, most devices have the isoc eps in
altsetting 0 too, with a maxpacketsize of 0.
Besides me no one else seems to be complaining, I guess most people don't use
isoc with libusb.
Anyways as s
@jwrdegoede Yes, my device has two alt settings for the interface and the isoc
endpoint is only created when changing to alt setting 1.
The API design issue makes sense now, thanks for explaining further. On the
other hand, that issue is not affecting me personally, and I do not have any
other
16 matches
Mail list logo
