From: Nuno Santos <nsantos@edigma.com>
To: linux-input@vger.kernel.org
Subject: Restoring kernel input driver state on boot
Date: Mon, 28 Nov 2011 10:20:32 +0000 [thread overview]
Message-ID: <4ED36070.8080700@edigma.com> (raw)
Hi,
Since is not possible for a kernel driver to save anything to a file I
need to know how could I achieve that using other technic.
Someone mentioned earlier in this list that I could use udev to load
settings on a kernel module.
Since my module state depends on a whole structure the best thing I can
remember to achieve this goal is someting like this:
- In user space (and since i'm always exchanging that data from and to
the kernel module within my device control panel) I could save to a
fixed place a file with that state.
- With a custom and small utility I could load (using the binnary
attributes) that state to the kernel module on it's initialization using
for that udev.
Since my understanding of udev at this point is almost null, I would
like to know if this is possible, and in what functionality of udev I
should put my effort on.
If someone could give me an expert advice about I would really
appreciate it.
Thanks in advance,
With my best regards,
Nuno Santos
reply other threads:[~2011-11-28 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ED36070.8080700@edigma.com \
--to=nsantos@edigma.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).