Location for Linux kernel module support files

Eugene Surovegin ebs at innocent.com
Wed Oct 2 03:07:15 EST 2002


At 07:33 AM 10/1/2002, you wrote:

>David Gibson wrote:
>>On Mon, Sep 30, 2002 at 11:46:22AM -0400, Tim Moloney wrote:
>>>I have written a device driver (module) that needs a configuration
>>>file.  Where is the standard place to put such files?
>>There isn't.  Device drivers, being part of the kernel, should not be
>>reading random files from the user's file system.  If the driver needs
>>configuration, the normal method is for userland scripts (either
>>startup or hotplug) to issue commands to poke the configuration into
>>the driver at runtime.
>>>I originally put it in the same directory as the .o file but
>>>'depmod -a' complains that it's not an ELF file.
>The file the device driver needs is an FPGA program file that
>- is data that I don't want compiled into the driver wasting space
>- will initially be specified when the driver is loaded via rc script
>- that can be reloaded by a program to customize it for a particular
>   application
>I know that this isn't a a typical situation and I have only seen one
>other device driver like this.  It is a 1553 driver that creates a
>/usr/lib/<module_name> directory for its configuration file.  Is there
>a better location?

For similar situation (I also need to load FPGA on our custom board) I just
a simple "char" device (e.g. /dev/fpga).
User mode program or simple script writes into this device and
the driver sends this data to the PLD chip.

For debugging I use something like
     # cp fpga.bin /dev/fpga

With this design driver itself doesn't have any knowledge about particular
location of
the FPGA program.


  Eugene Surovegin <mailto:ebs at innocent.com>

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

More information about the Linuxppc-dev mailing list