Re: [PATCH] char drivers: Ram oops kernel configuration parameters

From: Sergiu Iordache
Date: Thu Jun 23 2011 - 16:43:57 EST


On Thu, Jun 23, 2011 at 12:59 PM, <Valdis.Kletnieks@xxxxxx> wrote:
> On Thu, 23 Jun 2011 11:36:00 PDT, Sergiu Iordache said:
> > Ramoops currently has module parameters for setting the configuration
> > variables (ram start, ram size and dump oopses). This makes it difficult to
> > configure when the module is compiled as a builtin.
>
> Can't you add 'ramoops.ram_start=128M ramoops.ram_size=64M' or similar
> to your kernel cmdline?

You can but the problem is that when you're using the module as a
builtin managing the command line is harder than managing Kconfig
files. Instead of having different platform dependent config files
(which already exist in most of the cases) under source control you
would have to have different scripts which run the kernel with
different parameters.

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