public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>,
	linux-kernel@vger.kernel.org
Subject: Re: How to compile module params into kernel?
Date: Wed, 8 Nov 2006 21:14:56 +0100	[thread overview]
Message-ID: <20061108201456.GD21485@lug-owl.de> (raw)
In-Reply-To: <9a8748490611081209s37e5bfa7m2ddb49a23288ffbd@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

On Wed, 2006-11-08 21:09:04 +0100, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 08/11/06, Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> > > -----Original Message-----
> > > From: Jesper Juhl [mailto:jesper.juhl@gmail.com]
> > > On 08/11/06, Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> > > > Instead of passing a module param on the cmdline I want to compile that
> > > > into the kernel, but I can't figure out how.
> > > You could edit the module source and hardcode default values.
> > Yes, but I don't want to do that since it makes maintance
> > harder.
> Well, as far as I know, there's no way to specify default module
> options at compile time. The defaults are set in the module source and
> are modifiable at module load time or by setting options on the kernel
> command line at boot tiem. So, if that's no good for you I don't see
> any other way except modifying the source to hardcode new defaults.

However, that could probably be hacked in easily. We use a similar
approach for VAX, since we're not yet regularly booting off a local
harddisk, but commonly via MOP off the network.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:           Ich hatte in letzter Zeit ein bißchen viel Realitycheck.
the second  :               Langsam möchte ich mal wieder weiterträumen können.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-08 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 18:43 How to compile module params into kernel? Joakim Tjernlund
2006-11-08 19:05 ` Jesper Juhl
2006-11-08 20:02   ` Joakim Tjernlund
2006-11-08 20:09     ` Jesper Juhl
2006-11-08 20:14       ` Jan-Benedict Glaw [this message]
2006-11-09  8:31         ` Joakim Tjernlund
2006-11-08 20:16       ` Miguel Ojeda
2006-11-08 20:22         ` Joakim Tjernlund
2006-11-08 20:59     ` Richard B. Johnson
2006-11-08 21:08       ` Jan-Benedict Glaw

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=20061108201456.GD21485@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=jesper.juhl@gmail.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-kernel@vger.kernel.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