devfs
[Top] [All Lists]

Re: using modules +/- CONFIG_DEVFS_FS

To: Robert Manchester <rmanches@xxxxxxxxxx>
Subject: Re: using modules +/- CONFIG_DEVFS_FS
From: Jeremy Brown <mee@xxxxxxxxxxxxxxxxxx>
Date: Thu, 12 Apr 2001 17:09:47 -0700
Cc: devfs@xxxxxxxxxxx
In-reply-to: <20010412162915.A7239@lester.vmware.com>; from rmanches@vmware.com on Thu, Apr 12, 2001 at 04:29:15PM -0700
References: <20010412223023.9BB6E7288@lester.vmware.com> <20010413005658I.siemer@panorama.hadiko.de> <20010412162915.A7239@lester.vmware.com>
Sender: owner-devfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
To solve this problem, I would suggest looking at NVIDIA's Linux driver on
their site (www.nvidia.com). They distribute binary-only modules for common
distributions, as well as a source rpm that contains open-source wrapper code
and a binary-only library that is compiled into a kernel module.

Of course, this whole problem goes away if your driver is open-source. :)

Jeremy Brown
SGI

On Thu, Apr 12, 2001 at 04:29:15PM -0700, Robert Manchester wrote:
> * Robert Siemer (Robert.Siemer@xxxxxx) [010412 15:59]:
> > From: rmanches@xxxxxxxxxx (Robert Manchester)
> > 
> > > I would like to compile one module for kernel version xxx have it work
> > > on both devfs and non devfs systems.  Is there something inherently
> > > wrong in doing this that I am missing?
> > 
> > Kernel modules are not intended to work for different kernel
> > configurations (even in the same kernel version).
> 
> How am I supposed to release binary modules if they only work on the
> machine that I compiled them on?
> 
> -rob

<Prev in Thread] Current Thread [Next in Thread>