From: Tim Moloney <moloney@mrsl.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Location for Linux kernel module support files
Date: Mon, 30 Sep 2002 11:46:22 -0400 [thread overview]
Message-ID: <3D9871CE.7010607@mrsl.com> (raw)
I have written a device driver (module) that needs a configuration
file. Where is the standard place to put such files?
I originally put it in the same directory as the .o file but
'depmod -a' complains that it's not an ELF file.
--
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road \ /
Sarasota, FL 34232 .________\(O)/________.
(941) 377-6775 x208 ' ' O(.)O ' '
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-09-30 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 15:46 Tim Moloney [this message]
2002-10-01 0:32 ` Location for Linux kernel module support files David Gibson
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=3D9871CE.7010607@mrsl.com \
--to=moloney@mrsl.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).