I am not lawyer, but my understanding, porting GPL'd software onto QNX should not be a problem.

The plan is to let people in community to be able to share their code with others, via a public project, or private 
project. But these things haven't all sorted out yet. The best you can do for now, if probably asking create a project 
in "General" Forum.

Linux driver often need to be re-written, to port into QNX "network subsystem". There is  "Driver Development Kit" 
document here (http://www.qnx.com/developers/docs/6.3.0SP3/ddk_en/network/about.html), you can take a look and get a 
feeling.

I assume you are due boot between Linux and QNX, maybe you can install VMWare for Linux, use QNX in VMware, also include
 the physical harddisk in vmware so you can access the QNX partition as well. You can access network and do development,
 but at the end, you still have to boot back into QNX to test your new driver...

 

> -----Original Message-----
> From: Regan Russell [mailto:regan_russell@hotmail.com] 
> Sent: September 15, 2007 6:49 PM
> To: ostech-core_os
> Subject: MCP51 Ethernet Controller
> 
> Hi.

[ A tale of unsupported HW snipped ]
 
> if I attempt to hack in code from the Linux driver, if at all 
> possible, do I voilate anything in regards to:
> The New QNX Hybrid Software Model: Combining open source and 
> proprietary benefits for embedded systems
> 
> If I get something that compiles but doesn't work, can I 
> share with others and get people to help finish it...? How..? 
> Can I/someone branch the SVN repository..?

You don't violate anything in the QNX license terms.  Where you 
will run into a barrier is if you wanted the driver incorporated
back into the QNX source repository which is the basis for the 
commercial product.  

Since we are committed to providing our customers with a license
clean product and source base, the driver won't be incorporated
in the main QNX distribution.

The bazaar project is one location where you could conceivably
put this software, but it is more likely that if it is a technology
specific driver, that it would be incorporated into that project.

Since we are still in the early days, we haven't got the details
fully figured out (heck, we haven't even published the general
networking drivers or stack source yet!), but if you get started,
we'll find a way to make it work.
 
> How adaptable is the Linux driver code to be kludged into 
> anything else, how different are the driver models between 
> Linux and QNX...?  
> 
> I can't access the network, therefore I will have to svn 
> update from Linux, burn a CD, rebuild under QNX as proc is 
> broken under Linux at this stage.

You could also use a different host to build stuff on.  You don't
need to rebuild the kernel/process manager to get a network card
driver to work.  One of the joys of the ukernel is that this kind
of stuff is totally decoupled.

Hope this helps,
 Thomas