On 2013.06.29 13:02, Peter Stuge wrote:
> Xiaofan Chen wrote:
>> Take note now that libusbx/libusb will be merged
>
> Xiaofan, please hold off on reporting about the future until it has
> actually happened.
For the sake of people following this list, since there is a complete
agreement between AL
On Sat, Jun 29, 2013 at 8:02 PM, Peter Stuge wrote:
> Xiaofan Chen wrote:
>> Take note now that libusbx/libusb will be merged
>
> Xiaofan, please hold off on reporting about the future until it has
> actually happened.
Indeed you are right, the merging has not happened yet.
But to the community,
Xiaofan Chen wrote:
> Take note now that libusbx/libusb will be merged
Xiaofan, please hold off on reporting about the future until it has
actually happened.
The behavior of just about everyone involved in the libusbx fork
continues to blow my mind, but let's stay on topic.
Of course writing abo
On Fri, Jun 28, 2013 at 5:47 PM, Paul Fertser wrote:
> On Fri, Jun 28, 2013 at 11:36:15AM +0200, Andreas Fritiofson wrote:
>> But as Xiaofan said, libusb-compat-0.1 doesn't build out of the box
>> on Windows today.
>
> If I had a windows box handy, I'd prove that's quite easy to fix.
Yes it can b
On Fri, Jun 28, 2013 at 11:36:15AM +0200, Andreas Fritiofson wrote:
> But as Xiaofan said, libusb-compat-0.1 doesn't build out of the box
> on Windows today.
If I had a windows box handy, I'd prove that's quite easy to fix.
Sorry folks for such a lengthy and useless discussion, especially
given
On Fri, Jun 28, 2013 at 10:41 AM, Paul Fertser wrote:
> On Fri, Jun 28, 2013 at 04:15:33PM +0800, Xiaofan Chen wrote:
> > As mentioned before, there is no libusb-compat-0.1 as the libusb
> > 0.1 API provider for Windows,
>
> Why can't be OpenOCD linked against libusb-compat-0.1 which would be
> l
On Fri, Jun 28, 2013 at 04:15:33PM +0800, Xiaofan Chen wrote:
> As mentioned before, there is no libusb-compat-0.1 as the libusb
> 0.1 API provider for Windows,
Why can't be OpenOCD linked against libusb-compat-0.1 which would be
linked against libusbx which would just use WinUSB? Call me stupid,
On Tue, Jun 25, 2013 at 9:32 PM, Paul Fertser wrote:
> By unifying the API I just meant that a packager (Freddie) might want
> to compile OpenOCD against the compat-layer so that OpenOCD binaries
> would use only libusbx to communicate with the OS services (not both
> libusb-0.1 and libusbx as it
Yes, I agree too that porting to libusb-1.0 will be the best to unify
the USB API.
Regards,
Laurent
http://www.amontec.com
Amontec JTAGkey-2 High-Speed USB JTAG with RTCK
Amontec JTAGkey-2P High-Speed USB JTAG with RTCK and with Power
Le 28.06.2013 10:06, Xiaofan Chen a écrit :
> On Tue,
On Tue, Jun 25, 2013 at 9:02 PM, Andreas Fritiofson
wrote:
> If we want to unify the API, I see no reasonable option other than porting
> the remaining drivers you listed over to the libusb-1.0 API, replacing the
> common layer in drivers using it with it's libusb-1.0 version and then
> ditching t
Hi,
On Tue, Jun 25, 2013 at 03:02:25PM +0200, Andreas Fritiofson wrote:
> If we want to unify the API, I see no reasonable option other than porting the
> remaining drivers you listed over to the libusb-1.0 API, replacing the common
> layer in drivers using it with it's libusb-1.0 version and then
On Tue, Jun 25, 2013 at 12:03 PM, Paul Fertser wrote:
> Hello,
>
> On Tue, Jun 25, 2013 at 05:36:24PM +0800, Xiaofan Chen wrote:
> > And right now the best supported driver for libusbx
> > is still WinUSB, so yes it makes sense to recommend
> > users to use Zadig to install WinUSB drivers.
>
> Bu
Hello,
On Tue, Jun 25, 2013 at 05:36:24PM +0800, Xiaofan Chen wrote:
> And right now the best supported driver for libusbx
> is still WinUSB, so yes it makes sense to recommend
> users to use Zadig to install WinUSB drivers.
But for the instructions to be fully streamlined
(i.e. adapter-independe
On Tue, Jun 25, 2013 at 10:34 AM, Xiaofan Chen wrote:
> On Mon, Jun 24, 2013 at 7:17 PM, Paul Fertser wrote:
>> Moreover, have you seen my commit
>> 6be2a55bde5531de9897fd844c6db13e49213ae8? For the usual Windows builds
>> it'll make jlink, osbdm, opendous and aice use libusb-1.x api (via the
>>
On Mon, Jun 24, 2013 at 7:17 PM, Paul Fertser wrote:
> I think I'm starting to understand what you mean (finally :)).
>
> My idea was that a typical OpenOCD user shouldn't be bothered to
> install different drivers for different kind of adapters and that the
> procedure can be made unambiguous by
On Mon, Jun 24, 2013 at 02:47:10PM +0800, Xiaofan Chen wrote:
> On Mon, Jun 24, 2013 at 11:49 AM, Paul Fertser wrote:
> > So for OpenOCD users it looks like always installing plain
> > WinUSB driver and employing libusb-compat-0.1 for the older
> > code would be a fine solution, or am I still miss
On Sun, Jun 23, 2013 at 4:34 AM, Paul Fertser wrote:
> So my untested proposal for the future windows OpenOCD releases is to:
>
> 1. Remove all libusb-win32 files from the distribution archive;
>
> 2. Compile OpenOCD using libusb-compat for those drivers that are not
> ported to libusb-1.x or the
On Mon, Jun 24, 2013 at 11:49 AM, Paul Fertser wrote:
> On Mon, Jun 24, 2013 at 09:15:28AM +0800, Xiaofan Chen wrote:
>> On Sun, Jun 23, 2013 at 11:20 PM, Paul Fertser wrote:
>> > On Sun, Jun 23, 2013 at 11:00:04PM +0800, Xiaofan Chen wrote:
>> >> Take note there is no libusb-compat under Windows
On Mon, Jun 24, 2013 at 09:15:28AM +0800, Xiaofan Chen wrote:
> On Sun, Jun 23, 2013 at 11:20 PM, Paul Fertser wrote:
> > On Sun, Jun 23, 2013 at 11:00:04PM +0800, Xiaofan Chen wrote:
> >> Take note there is no libusb-compat under Windows, only
> >> libusb-win32.
> >
> > Eh, now that's strange. I
On Sun, Jun 23, 2013 at 11:20 PM, Paul Fertser wrote:
> On Sun, Jun 23, 2013 at 11:00:04PM +0800, Xiaofan Chen wrote:
>> Take note there is no libusb-compat under Windows, only
>> libusb-win32.
>
> Eh, now that's strange. I was sure libusb-compat is a thin emulation
> layer to allow using libusb-0
Hi,
On Sun, Jun 23, 2013 at 11:00:04PM +0800, Xiaofan Chen wrote:
> On Sun, Jun 23, 2013 at 4:34 AM, Paul Fertser wrote:
> > Hi Freddie,
> >
> > Today my coworker called me complaining he can't use OpenOCD on his
> > Windows XP (yeah, lame!) with an Olimex adapter.
>
> So you are talking about t
On Sun, Jun 23, 2013 at 4:34 AM, Paul Fertser wrote:
> Hi Freddie,
>
> Today my coworker called me complaining he can't use OpenOCD on his
> Windows XP (yeah, lame!) with an Olimex adapter.
So you are talking about the Windows binary provided by Freddie,
right?
> In the end it appeared he was co
Hi Freddie,
Today my coworker called me complaining he can't use OpenOCD on his
Windows XP (yeah, lame!) with an Olimex adapter.
In the end it appeared he was confused by all the possible driver
options (and I can easily see it happening with the other regular
users too).
So my untested proposa
23 matches
Mail list logo
