On Thu, Aug 23, 2012 at 7:23 PM, Satz Klauer wrote:
> Hi,
>
> I found libusbx via a link at project libusb-winusb-wip and I'm a bit
> confused now.
>
> Until now when using "old" libusb on Windows some WinUSB drivers have
> been mandatory (that's what I'm looking for at libusb-winusb-wip). But
> I
On Fri, Aug 24, 2012 at 4:06 AM, David Grant wrote:
> On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard wrote:
>>
>>
>> Now, due to time constraints as well as other considerations
>> (removing/deleting anything needs to be carefully considered), libwdi
>> doesn't support restoring the original driver
On Thu, Aug 23, 2012 at 1:31 PM, Pete Batard wrote:
> Be mindful that what's currently missing in libwdi is not due
> to the developers thinking that it may be too complex to implement.
> Instead, it's just the usual matter of priorities.
> Uninstallation/restore has just been (and still is) low
On 2012.08.23 21:09, David Grant wrote:
> ...and I assume this part can all be automated through some API. I know
> someone else at our company that has done the "scan for new devices"
> part programmatically. I assume that uninstall part can be done through
> setupapi.
Yes, as a driver related AP
On 2012.08.23 21:06, David Grant wrote:
> So why the need, as
> you say, to embed the original driver for the restore part?
If you read what I wrote, you'll see that what I pointed out is if you
wanted to do it with the *current* version of libwdi, i.e. one that
doesn't implement a restore featu
On Thu, Aug 23, 2012 at 1:06 PM, David Grant wrote:
> all I have to do is right-click on the file and select "uninstall" and
> when the dialog pops-up select a checkbox that says something like "delete
> driver files as well". Then I just had to "scan for new devices" and it
> picked up USBSTOR.s
On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard wrote:
>
> Now, due to time constraints as well as other considerations
> (removing/deleting anything needs to be carefully considered), libwdi
> doesn't support restoring the original driver, so unless you also embed
> the driver to restore in the lib
On 2012.08.23 11:09, Hans de Goede wrote:
> Well this is the reason why I'm using __u32 here, since our linux_usbfs.h
> is an (almost) 1 on 1 copy of linux/usbdevice_fs.h, so I think unnecessarily
> deviating from the original is not a good idea
Deviating from using platform specific custom nonsta
On 2012.08.23 12:57, sebastiank wrote:
> Pcscd does not function as expected, i.e. my app is not able to find
> the attached rfid-reader, although pcscd is recognising it and is
> logging the card insertion and removal.
>
> This is happening, when pcscd is started as daemon and
>
> - LIBUSB_D
On Wed, Aug 22, 2012 at 5:00 PM, Xiaofan Chen wrote:
> Please take note VirutalBox's USB support is not Open Source.
> You need the extension pack which is under non-open-source
> license.
> https://www.virtualbox.org/wiki/Downloads
> https://www.virtualbox.org/manual/ch01.html#intro-installing
>
On Wed, Aug 22, 2012 at 3:06 PM, Pete Batard wrote:
> On 2012.08.22 18:55, David Grant wrote:
> > It just seems like the driver swapping is the main
> > issue we need to resolve.
>
> Well, if you want to contribute a driver swapping/removal patch to
> libwdi, I'll be happy to review it.
>
>
Thank
WinUSB is available from Microsoft as part of their DDK
libusb0 & libusbk are also relatively new choices.
This project has details , and a installer.
http://sourceforge.net/projects/libwdi/
On 08/23/2012 08:03 AM, Satz Klauer wrote:
> OK...and do I still have to use the drivers from
> http://l
OK...and do I still have to use the drivers from
http://libusb-winusb-wip.googlecode.com/files/winusb%20driver.zip ?
That's the page which mentions it is outdated and refers to libusbx.
Or are there some other drivers available that are signed - especially
for 64 bit Windows?
On Thu, Aug 23, 2012
On 2012-08-22 23:16, Pete Batard wrote:
> I have now pushed Peter's patch...
THANK YOU VERY MUCH TO ALL OF YOU!!!
I have distributed the new version to the prod machines today.
While testing the new version (git mainline 1.0.12.10553) on the test
machine, I recognised the following strange behavi
You still need WinUSB for now.
http://libusbx.org/
On 08/23/2012 07:23 AM, Satz Klauer wrote:
> Hi,
>
> I found libusbx via a link at project libusb-winusb-wip and I'm a bit
> confused now.
>
> Until now when using "old" libusb on Windows some WinUSB drivers have
> been mandatory (that's what I'm
Hi,
I found libusbx via a link at project libusb-winusb-wip and I'm a bit
confused now.
Until now when using "old" libusb on Windows some WinUSB drivers have
been mandatory (that's what I'm looking for at libusb-winusb-wip). But
I can't find something like that for libusbx.
So what is needed in
Hi,
On 08/22/2012 11:52 PM, Pete Batard wrote:
> On 2012.08.22 11:21, Hans de Goede wrote:
>> I would prefer to stick with the __u32, as that is what is in the kernels
>> *userspace* headers
>
> It's 2012, C99 + stdint.h have been around for more than decade [1],
> and, unlike what may be the case
17 matches
Mail list logo
