From: TimO <hairballmt@mcn.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] DRM OS
Date: Sun, 16 Dec 2001 23:10:56 -0700 [thread overview]
Message-ID: <3C1D8C70.A6811F@mcn.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10112121959320.8479-100000@www.transvirtual.com> <Pine.LNX.4.10.10112140107130.8630-100000@master.linux-ide.org> <20011214163235.A17636@vitelus.com>
Aaron Lehmann wrote:
>
> On Fri, Dec 14, 2001 at 01:15:48AM -0800, Andre Hedrick wrote:
> > CPU(crypto)<->Memory(crypto)<->Framebuffer(crypto)
> > ata(clean)<->diskcontroller(crypto)<->Memory(crypto)<->CPU(crypto)
> > scsi(crypto)<->diskcontroller(crypto)<->Memory(crypto)<->CPU(crypto)
> > CPU(crypto)<->Bridge(crypto)<->Memory(crypto)
> >
> > Just watch and see!
>
> Why would crypto help at all?
> -
To prevent us from sniffing the bus to figure out proprietary protocols
like we do with USB devices. ...and other things, of course.
--
===============
-- TimO
--------------------==============++==============--------------------
No Cool .sig
next prev parent reply other threads:[~2001-12-17 6:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 4:00 [OT] DRM OS James Simmons
2001-12-13 4:07 ` Matt
2001-12-13 13:38 ` Rik van Riel
2001-12-14 9:15 ` Andre Hedrick
2001-12-15 0:32 ` Aaron Lehmann
2001-12-17 6:10 ` TimO [this message]
2001-12-18 16:17 ` Alan Cox
2001-12-18 18:54 ` James Simmons
2001-12-18 19:06 ` Andre Hedrick
2001-12-18 19:53 ` Aaron Lehmann
2001-12-18 20:05 ` Dave Jones
2001-12-18 20:10 ` Aaron Lehmann
2001-12-18 20:25 ` Dave Jones
2001-12-18 20:45 ` H. Peter Anvin
2001-12-19 10:39 ` Helge Hafting
2001-12-18 20:44 ` Rik van Riel
2001-12-18 20:56 ` Gábor Lénárt
2001-12-19 21:49 ` Thomas Dodd
2001-12-20 22:40 ` Marco Ermini
2001-12-21 16:38 ` Brendan Pike
2002-01-02 22:13 ` Chris Friesen
2002-01-02 22:30 ` Alan Cox
2002-01-03 1:52 ` Andre Hedrick
2002-01-03 11:10 ` Henning P. Schmiedehausen
2001-12-13 14:21 Thomas Hood
2001-12-13 15:33 Jesse Pollard
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=3C1D8C70.A6811F@mcn.net \
--to=hairballmt@mcn.net \
--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;
as well as URLs for NNTP newsgroup(s).