linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Downing, Thomas" <Thomas.Downing@ipc.com>
To: "'Stuart Longland'" <stuartl@longlandclan.hopto.org>,
	linux-kernel@vger.kernel.org
Subject: RE: fun or real: proc interface for module handling?
Date: Fri, 1 Aug 2003 09:54:24 -0400	[thread overview]
Message-ID: <170EBA504C3AD511A3FE00508BB89A920234CD6C@exnanycmbx4.ipc.com> (raw)

> -----Original Message-----
> From: Stuart Longland [mailto:stuartl@longlandclan.hopto.org]
> On Thu, Jul 31, 2003 at 02:34:01PM +0200, Måns Rullgård wrote:
> 
> | Nico Schottelius <nico-kernel@schottelius.org> writes:
> | > Modul options could be passed my
> | >   echo "psmouse_noext=1" > /proc/mods/psmouse/options
> | > which would also make it possible to change module options while
> running..
> |
> | How would options be passed when loading?  Some modules require that
> | to load properly.
> 
> Possibility, why not just have a file, /proc/mods/initial, that you
> write the initial kernel module options to, e.g.
> 
> # echo "ne2000 io=0x300 irq=11" > /proc/mods/initial
> 
> Then you load the module using:
> 
> # mkdir /proc/mods/ne2000/
> 
> although you could skip this necessity and just load the module when
> someone writes to /proc/mods/initial.
> 
> Just a thought.

>From an newbie:

How about having a dir for each available module created earliest moment
in boot process, (point where depmod is done now I guess).  Each dir has
files 'options' and 'load'.  then you could:

# echo "io=0x300 irq=11" > /proc/mods/ne2000/options

followed by

# echo "1" > /proc/mods/ne2000/load

Of course, I am probably missing the point or something :-(

td

             reply	other threads:[~2003-08-01 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 13:54 Downing, Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-31 13:51 fun or real: proc interface for module handling? John Bradford
2003-07-31 12:12 Nico Schottelius
2003-07-31 12:34 ` Måns Rullgård
2003-07-31 13:03   ` Gábor Lénárt
2003-07-31 23:15   ` jw schultz
2003-08-01  5:55     ` Stuart Longland
2003-07-31 13:13 ` Yaroslav Rastrigin
2003-07-31 13:29   ` Nico Schottelius
2003-07-31 23:59 ` Grant Miner

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=170EBA504C3AD511A3FE00508BB89A920234CD6C@exnanycmbx4.ipc.com \
    --to=thomas.downing@ipc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuartl@longlandclan.hopto.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).