From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Location for Linux kernel module support files
Date: Tue, 1 Oct 2002 10:32:23 +1000 [thread overview]
Message-ID: <20021001003223.GJ10265@zax> (raw)
In-Reply-To: <3D9871CE.7010607@mrsl.com>
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.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-01 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 15:46 Location for Linux kernel module support files Tim Moloney
2002-10-01 0:32 ` David Gibson [this message]
2002-10-01 14:33 ` Tim Moloney
2002-10-01 16:25 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 17:07 Eugene Surovegin
2002-10-01 19:06 ` Tim Moloney
2002-10-02 3:25 ` Michael Heironimus
2002-10-02 7:54 ` Ethan Benson
2002-10-02 8:06 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021001003223.GJ10265@zax \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.