linux-kernel - RE: How to compile module params into kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 8 Nov 2006 21:22:24 +0100
From:	"Joakim Tjernlund" <joakim.tjernlund@...nsmode.se>
To:	"'Miguel Ojeda'" <maxextreme@...il.com>,
	"'Jesper Juhl'" <jesper.juhl@...il.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: How to compile module params into kernel?

> -----Original Message-----
> From: Miguel Ojeda [mailto:maxextreme@...il.com] 
> Sent: den 8 november 2006 21:17
> To: Jesper Juhl
> Cc: Joakim Tjernlund; linux-kernel@...r.kernel.org
> Subject: Re: How to compile module params into kernel?
> 
> On 11/8/06, Jesper Juhl <jesper.juhl@...il.com> wrote:
> > On 08/11/06, Joakim Tjernlund <joakim.tjernlund@...nsmode.se> wrote:
> > > > -----Original Message-----
> > > > From: Jesper Juhl [mailto:jesper.juhl@...il.com]
> > > >
> > > > On 08/11/06, Joakim Tjernlund 
> <joakim.tjernlund@...nsmode.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.
> >
> 
> You can add parameter values at Kconfig using "int", "hex"... instead
> of tristate, and then do something like:
> 
> static unsigned int foo = CONFIG_foo;
> module_param(foo, uint, S_IRUGO);
> MODULE_PARM_DESC(foo, "foo value (uint)");

hmm, don't quite understand.
Can you rewrite that to match the cmdvar "rtc-ds1307.force=0,0x68" ? 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/