From: Greg KH <gregkh@suse.de>
To: Sergiu Iordache <sergiu@chromium.org>
Cc: Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
Samo Pogacnik <samo_pogacnik@t-2.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Randy Dunlap <randy.dunlap@oracle.com>,
Marco Stornelli <marco.stornelli@gmail.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char drivers: Ram oops kernel configuration parameters
Date: Thu, 23 Jun 2011 14:33:15 -0700 [thread overview]
Message-ID: <20110623213315.GB4347@suse.de> (raw)
In-Reply-To: <BANLkTiko9PvSDHEnbjCAvcAReLytWwg7qSoZGv778xuj3tqW=g@mail.gmail.com>
On Thu, Jun 23, 2011 at 01:43:49PM -0700, Sergiu Iordache wrote:
> On Thu, Jun 23, 2011 at 12:59 PM, <Valdis.Kletnieks@vt.edu> 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.
Then why not make the sysfs files writable?
Stuff like this should not be picked from the configuration build if at
all possible. The fact that you feel changing the Kconfig is easier
than your boot command line shows a problem in your overall system
configuration.
greg k-h
next prev parent reply other threads:[~2011-06-23 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 18:36 [PATCH] char drivers: Ram oops kernel configuration parameters Sergiu Iordache
2011-06-23 18:39 ` Marco Stornelli
2011-06-23 19:59 ` Valdis.Kletnieks
2011-06-23 20:43 ` Sergiu Iordache
2011-06-23 21:33 ` Greg KH [this message]
2011-06-23 22:07 ` Mandeep Singh Baines
2011-06-24 10:49 ` Marco Stornelli
2011-06-24 17:06 ` Mandeep Singh Baines
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=20110623213315.GB4347@suse.de \
--to=gregkh@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=darwish.07@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=samo_pogacnik@t-2.net \
--cc=seiji.aguchi@hds.com \
--cc=sergiu@chromium.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