From: Otto Wyss <otto.wyss@orpatec.ch>
To: "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: How to check for the framebuffer device and the right kernel module
Date: Sat, 19 Jun 2004 22:57:36 +0200 [thread overview]
Message-ID: <40D4A8BF.DFDB48AC@orpatec.ch> (raw)
I've written a simple app which checks if the framebuffer device is
correct installed (see
"http://wyodesktop.sourceforge.net/index.php?page=checkapp.html"). I do
it by more less just using the device. My little check app is working
but shouldn't there be a more correct way?
I'm also not sure what results are produced when the device exists but
without the right kernel module. How can I check for a kernel module to
inform the user about it?
O. Wyss
PS. I welcome any feedback (e-mail) how this little app behaves on
anyones system.
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
next reply other threads:[~2004-06-19 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 20:57 Otto Wyss [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 19:32 How to check for the framebuffer device and the right kernel module Otto Wyss
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=40D4A8BF.DFDB48AC@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--cc=linux-kernel@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