From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Whatever happened to the real mode driver idea?
Date: Mon, 10 Jan 2005 16:19:31 -0500 [thread overview]
Message-ID: <cruqp5$c59$1@gatekeeper.tmr.com> (raw)
There has been some discussion of some "universal real mode" driver to
allow hardware without an open source driver to operate with Linux. It's
been about a year since this came up, and as I recall the last
discussion ended with people opposed to using that as a reverse
engineering tool, due to possible legal issues.
But I have a technical question, wouldn't a real mode use of BIOS code
be more secure that the current situation of tainted drivers running in
the kernel? Please take political discussion elsewhere, I'm curious
about the safty issue, not the legal or advocacy issues.
Being an old MULTICS guy, my first though when protection rings came out
was that the drivers should be out of ring zero.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
reply other threads:[~2005-01-11 0:53 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='cruqp5$c59$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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