From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to compile module params into kernel?
Date: Wed, 8 Nov 2006 21:09:04 +0100 [thread overview]
Message-ID: <9a8748490611081209s37e5bfa7m2ddb49a23288ffbd@mail.gmail.com> (raw)
In-Reply-To: <02fd01c70370$d9af6700$020120ac@Jocke>
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.
> > >
> > > The module param I want compile into kernel is
> > > rtc-ds1307.force=0,0x68
> > >
> > > This is for an embeddet target that doesn't have loadable module
> > > support.
> > >
> > 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.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-11-08 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 18:43 Joakim Tjernlund
2006-11-08 19:05 ` Jesper Juhl
2006-11-08 20:02 ` Joakim Tjernlund
2006-11-08 20:09 ` Jesper Juhl [this message]
2006-11-08 20:14 ` Jan-Benedict Glaw
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=9a8748490611081209s37e5bfa7m2ddb49a23288ffbd@mail.gmail.com \
--to=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
all inboxes | Powered by JetHome®