From: Ralph Metzler <rjkm@metzlerbros.de>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Nick Piggin <piggin@cyberone.com.au>,
Jeff Garzik <jgarzik@pobox.com>,
jt@hpl.hp.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Pontus Fuchs <pof@users.sourceforge.net>
Subject: Re: Announce: ndiswrapper
Date: Thu, 20 Nov 2003 14:15:07 +0100 [thread overview]
Message-ID: <16316.48731.954740.275481@metzlerbros.de> (raw)
In-Reply-To: <200311201057.07503.ioe-lkml@rameria.de>
Ingo Oeser writes:
> We already have a second-class flavor of open source in the kernel right
> now. There are drivers that do "magic value at magic address" in a quite
> sophisticated manner. Combine this with firmware load from Windows DLLs
> and you basically HAVE closed source, since the driver is on the device
> itself and we just invoke it via i2c commands.
>
> On NVidia drivers we might complain, that we don't see, which kernel
> functions are used and for what. On these drivers we don't even see what
> is done, since the device can issue DMA at will and thus scribble over
> random kernel memory on firmware malfunction. And maybe this scribbling
> is not that lethal to Windows for some reasons (e.g. area never used or
> reserved area) so it will never be fixed.
>
> Just have a look at some DVB hardware drivers. As much as I like *what*
> is done there, I don't like how it is done.
Those drivers (at least the ones in the kernel right now) cannot issue any
DMA from inside the firmware. They also cannot crash the system, only
themselves. Basically they are like a separate computer connected via
a network-like connection (in this case dual ported RAM). The code
controlling the PCI bridge is open.
You are right that if the firmware can do things like initiating DMA
transfers this is a big problem. Of course this can also happen with
hardware which has bugs in permanently burnt-in microcode or even in the
silicon itself.
Regards,
Ralph Metzler
next prev parent reply other threads:[~2003-11-20 13:27 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 3:11 Jean Tourrilhes
2003-11-20 3:26 ` Jeff Garzik
2003-11-20 3:34 ` Jean Tourrilhes
2003-11-21 12:05 ` Vojtech Pavlik
2003-11-21 17:25 ` Jean Tourrilhes
2003-11-21 17:30 ` Jeff Garzik
2003-11-21 17:43 ` Vojtech Pavlik
2003-11-21 17:48 ` Jean Tourrilhes
2003-11-21 17:50 ` Vojtech Pavlik
2003-11-20 4:00 ` William Lee Irwin III
2003-11-20 4:16 ` Nick Piggin
2003-11-20 4:35 ` Neil Brown
2003-11-20 4:49 ` Nick Piggin
2003-11-20 4:57 ` Randy.Dunlap
2003-11-20 5:05 ` Nick Piggin
2003-11-20 6:50 ` Benjamin Herrenschmidt
2003-11-20 5:27 ` William Lee Irwin III
2003-11-20 5:36 ` Jeff Garzik
2003-11-20 5:36 ` Nick Piggin
2003-11-20 4:38 ` William Lee Irwin III
2003-11-20 4:59 ` Nick Piggin
2003-11-20 5:12 ` William Lee Irwin III
2003-11-20 5:27 ` Nick Piggin
2003-11-24 15:40 ` Rik van Riel
2003-11-20 12:41 ` Diego Calleja García
2003-11-20 13:04 ` Christoph Hellwig
2003-11-20 20:24 ` Pasi Kärkkäinen
2003-11-20 5:11 ` Valdis.Kletnieks
2003-11-20 9:56 ` Ingo Oeser
2003-11-20 13:15 ` Ralph Metzler [this message]
2003-11-20 6:52 ` Matt Mackall
2003-11-20 7:40 ` Nick Piggin
2003-11-20 10:13 ` Geert Uytterhoeven
2003-11-20 10:17 ` William Lee Irwin III
2003-11-20 22:47 ` Bill Davidsen
2003-11-20 22:59 ` William Lee Irwin III
2003-11-20 23:26 ` Oliver Hunt
2003-11-20 23:32 ` Bill Davidsen
2003-11-20 13:19 ` Gene Heskett
2003-11-20 23:15 ` Bill Davidsen
2003-11-20 5:25 ` Jeff Garzik
2003-11-20 5:26 ` William Lee Irwin III
2003-11-20 6:54 ` Benjamin Herrenschmidt
2003-11-20 17:27 ` Jean Tourrilhes
2003-11-20 23:57 ` Benjamin Herrenschmidt
2003-11-21 0:03 ` Jean Tourrilhes
2003-11-20 16:47 ` Jason Lunz
2003-11-20 17:36 ` Jeff Garzik
2003-11-20 17:24 ` Jean Tourrilhes
2003-11-20 17:48 ` Richard B. Johnson
2003-11-20 18:03 ` William Lee Irwin III
2003-11-20 23:01 ` Bill Davidsen
2003-11-21 5:48 ` H. Peter Anvin
2003-11-21 7:26 ` Linus Torvalds
2003-11-21 7:37 ` H. Peter Anvin
2003-11-21 7:47 ` Nuno Silva
2003-11-21 7:51 ` Linus Torvalds
2003-11-20 10:55 ` Pavel Machek
2003-11-20 17:22 ` Jean Tourrilhes
2003-11-20 23:04 ` Bill Davidsen
2003-11-20 23:45 ` Jean Tourrilhes
2003-11-21 17:08 ` Bill Davidsen
2003-11-23 23:13 ` Jan Rychter
[not found] <TNwv.6Lz.7@gated-at.bofh.it>
[not found] ` <TPHV.1vf.1@gated-at.bofh.it>
[not found] ` <TQXu.420.11@gated-at.bofh.it>
2003-11-21 2:53 ` Andrew Miklas
2003-11-21 10:33 ` Maciej Zenczykowski
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 23:53 Mudama, Eric
2003-11-21 0:00 ` Jean Tourrilhes
2003-11-21 1:01 ` Bob McElrath
2003-11-24 17:42 ` Pavel Machek
2003-11-21 7:58 ` Jan De Luyck
2003-11-21 8:59 ` Jamie Lokier
2003-11-18 11:02 Pontus Fuchs
2003-11-18 12:51 ` Christian Axelsson
2003-11-18 13:26 ` Maciej Zenczykowski
2003-11-18 13:37 ` Christian Axelsson
2003-11-18 13:49 ` Richard B. Johnson
2003-11-18 14:02 ` Arjan van de Ven
2003-11-18 13:59 ` Jeff Garzik
2003-11-18 14:14 ` Maciej Zenczykowski
2003-11-18 14:49 ` Jan-Benedict Glaw
2003-11-18 15:31 ` Maciej Zenczykowski
2003-11-18 14:19 ` Richard B. Johnson
2003-11-18 14:31 ` Davide Libenzi
2003-11-18 22:22 ` Pavel Machek
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=16316.48731.954740.275481@metzlerbros.de \
--to=rjkm@metzlerbros.de \
--cc=ioe-lkml@rameria.de \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=pof@users.sourceforge.net \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®