On 7/13/06, Greg KH <greg@xxxxxxxxx> wrote:
On Thu, Jul 13, 2006 at 06:09:56PM -0700, kewlemer wrote: > On 7/13/06, Greg KH <greg@xxxxxxxxx> wrote: > >On Thu, Jul 13, 2006 at 03:23:36PM -0700, kewlemer wrote: > >> On 7/13/06, Greg KH <greg@xxxxxxxxx> wrote: > >> >And why port a working driver to C++, which does not work in the kernel? > >> >Are you doing this for a different operating system? > >> > > >> 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. Then you know you can't use the source code from the Linux kernel in your stack, right? You better only be using it for reference.
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 for such a thing. Thanks for pointing it though. Regards, KM -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
