On 7/14/06, kewlemer <kewlemer@xxxxxxxxx> wrote:
On 7/13/06, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote: > > > > > It's actually going to be a userland driver for the C++ stack I am > > > > working on. It runs on QNX and Montavista Linux. > > > > > > Is your C++ stack released under the GPL? > > > > > Unfortunately not. > > Have you talked to a lawyer then about what exactly you can and cannot > do with GPL code? I know lawyers will get very nervous about things like > this... It's just for the register settings I am using it as a reference. The software developer manual does well to point of *what* each register does, but not so well when explaining *what all* and *how* registers need to be changed to get a particular functionality. I think it's best to buy support from Intel (I already might have) for such a thing. Thanks to you and Greg for pointing it though. Regards, K
Just to add and make it clear, should not have used the term 'porting' I think. I already have a perfectly working C++ user land driver and was just adding the forced settings functionality to it. The register settings for this was what causing the problems and when the developer manual proved insufficient, I looked at how e1000 was doing it. Besides I just found that we have a NDA and support contract with Intel. But boy, I learnt something more than programming from this ! :) Thanks again folks. -K -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
