linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nuno Santos <nsantos@edigma.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Saving kernel module parameters settings
Date: Tue, 22 Nov 2011 10:02:27 +0000	[thread overview]
Message-ID: <4ECB7333.5090202@edigma.com> (raw)
In-Reply-To: <20111121173036.GB2362@core.coreip.homeip.net>

Hi Dimitry,

Thanks for your reply.

Just to contextualize. I ended up implementing the communication between 
userspace and kernel space with binary attributes. I have only needed to 
implement two of them.

One of those binary attributes is responsible for getting the state to 
be shown on controlpanel and setting the state back to the device based 
on control panel changes.

Basicly, what I need is to have a copy of that binary attribute saved in 
order to load it into module internal state variable when module loads.

Do you think is possible to achieve this goal?

Thanks,

With my best regards,

Nuno


On 11/21/2011 05:30 PM, Dmitry Torokhov wrote:
> On Mon, Nov 21, 2011 at 09:59:16AM +0000, Nuno Santos wrote:
>> Hi,
>>
>> Is there any mechanism to save kernel module parameters/settings in
>> a persistent way?
>>
> If kernel module is built-in then you'd have to adjust kernel command
> line. If module is built as a loadable module then you can stick needed
> settings in a file in /etc/modprobe.d/
>
> Depending on the parameters (i.e. if they programmed to take effect
> immediately - as opposed to, for example, only during new device
> binding) you can have a program adjust them after you boot.
>
> Thanks.
>


      reply	other threads:[~2011-11-22 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  9:59 Saving kernel module parameters settings Nuno Santos
2011-11-21 17:30 ` Dmitry Torokhov
2011-11-22 10:02   ` Nuno Santos [this message]

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=4ECB7333.5090202@edigma.com \
    --to=nsantos@edigma.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).