Re: [libusb] QNX support

[Andrew B. <and...@re...>]

Yeah, the testing element is what concerned me, which is why I asked about test suites.

I'm no lawyer but I would imagine that shipping a pre-configured dev board might go against QNX licensing? And to rebuild libusb for testing in the future would require access to the QNX SDP, which I'm sure requires some sort of license agreement with QNX?

Cheers
Andrew
________________________________________
From: Matthew Giassa <ma...@gi...>
Sent: 12 July 2016 03:14
To: Xiaofan Chen; Andrew Black
Cc: lib...@li...
Subject: Re: [libusb] QNX support

Hi there,

I used to work for QNX, and might be able to help out a bit. There's the
6.6 SDP and CAR2 platform which you could use for testing. They also
provide a bunch of board support packages (BSPs) for various EVM/demo
boards.

http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/BSPAndDrivers

That should allow for something better than testing with x86 vmware
images. If you have a budget for it, your best bet might be to contact
the maintainer and offer to ship a pre-configured dev board for testing
purposes, along with maybe a test device or two, after you've gotten it
working on your end.

============================================================
Matthew Giassa, MASc, BASc, EIT
Security and Embedded Systems Specialist
linkedin: https://ca.linkedin.com/in/giassa
e-mail:   ma...@gi...
website:  www.giassa.net

On 07/11/16 06:01, Xiaofan Chen wrote:
> On Mon, Jul 11, 2016 at 7:13 PM, Andrew Black <and...@re...> wrote:
>> We have implemented support for the QNX OS in libusb. We would like to push
>> these changes back upstream. Are there particular requirements that need to
>> be met for this to happen, e.g. any test suites that need to pass, etc?
>> Please let me know the best way to proceed.
>
> I think you can discuss using this mailing list on your patches.
>
> You can create a pull request in Github. Something like this.
>      https://github.com/libusb/libusb/pull/177
>
> The only problem seems to be that the maintainer can not test QNX since
> it seems not easily accessible.
>
>