All of lore.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Re: [Dri-devel] Re: [Linux-fbdev-devel] DRM and pci_driver conversion
Date: Mon, 27 Oct 2003 09:01:42 -0500	[thread overview]
Message-ID: <20031027140142.GA2832@ncsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0310251116140.4083-100000@home.osdl.org>

On Sat, Oct 25, 2003 at 11:37:05AM -0700, Linus Torvalds wrote:
> Face it, a good graphics driver needs more than just "set up the ROM". It
> needs DMA access, and the ability to use interrupts. It needs a real 
> driver.
> 
> It basically needs something like what the DRI modules tend to do.

On Tue, 16 Jan 1996, Linus Torvalds wrote:
> X goes to hardware directly, but that's just because it should do it. 
> And exactly _because_ it's an application, it can be just about as
> complex as it wants (and needs) to be.  So you have a user-level device
> driver: is that not a good idea? The microkernel people are jumping up
> and down and wetting themselves in excitement over things like that. 

Its not that I dont think you are entitled to change your mind.  Its just
that the second version is so quotable that it has stuck in my mind oh
these many years.

Jim

  parent reply	other threads:[~2003-10-27 14:01 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  2:31 DRM and pci_driver conversion Eric Anholt
2003-10-23 19:04 ` [Linux-fbdev-devel] " Kronos
2003-10-23 19:04   ` Kronos
2003-10-23 21:10   ` [Linux-fbdev-devel] " Eric Anholt
2003-10-23 21:31     ` Jon Smirl
2003-10-23 23:23       ` [Dri-devel] " Linus Torvalds
2003-10-23 23:23         ` Linus Torvalds
2003-10-23 23:46         ` Eric Anholt
2003-10-24  1:19         ` Jeff Garzik
2003-10-24  1:19           ` [Dri-devel] " Jeff Garzik
2003-10-24  1:52           ` [Dri-devel] Re: [Linux-fbdev-devel] " Jon Smirl
2003-10-24  3:47           ` Multiple drivers for same hardware:, was: " Jon Smirl
2003-10-24  3:47             ` Jon Smirl
2003-10-24  4:40             ` Linus Torvalds
2003-10-24  4:40               ` Linus Torvalds
2003-10-28 18:00               ` James Simmons
2003-10-28 18:00                 ` James Simmons
2003-10-24 16:44           ` [Dri-devel] Re: [Linux-fbdev-devel] " Linus Torvalds
2003-10-24 16:44             ` [Dri-devel] " Linus Torvalds
2003-10-24 16:57             ` [Dri-devel] Re: [Linux-fbdev-devel] " Petr Vandrovec
2003-10-24 17:59               ` Linus Torvalds
2003-10-24 17:59                 ` Linus Torvalds
2003-10-24 18:34                 ` Jon Smirl
2003-10-24 19:45                   ` Ivan Kokshaysky
2003-10-24 19:45                     ` [Dri-devel] " Ivan Kokshaysky
2003-10-24 19:08               ` [Dri-devel] Re: [Linux-fbdev-devel] " Ivan Kokshaysky
2003-10-24 19:08                 ` [Dri-devel] " Ivan Kokshaysky
2003-10-24 17:06             ` [Dri-devel] Re: [Linux-fbdev-devel] " Jeff Garzik
2003-10-24 17:06               ` [Dri-devel] " Jeff Garzik
2003-10-24  1:50         ` [Dri-devel] Re: [Linux-fbdev-devel] " Jon Smirl
2003-10-24  1:50           ` [Dri-devel] " Jon Smirl
2003-10-25 17:29         ` [Dri-devel] Re: [Linux-fbdev-devel] " Egbert Eich
2003-10-25 17:29           ` [Dri-devel] " Egbert Eich
2003-10-25 18:37           ` [Dri-devel] Re: [Linux-fbdev-devel] " Linus Torvalds
2003-10-25 18:37             ` Linus Torvalds
2003-10-25 19:17             ` Jeff Garzik
2003-10-25 19:17               ` [Dri-devel] " Jeff Garzik
2003-10-27 14:37               ` Ingo Oeser
2003-10-27 14:37               ` [Dri-devel] Re: [Linux-fbdev-devel] " Ingo Oeser
2003-10-27 15:43                 ` Jeff Garzik
2003-10-27 15:43                   ` [Dri-devel] " Jeff Garzik
2003-10-28 10:53                   ` [Dri-devel] Re: [Linux-fbdev-devel] " Ingo Oeser
2003-10-27 15:14               ` Keith Whitwell
2003-10-27 15:14                 ` [Dri-devel] " Keith Whitwell
2003-10-27 15:38                 ` Jeff Garzik
2003-10-27 15:38                 ` [Dri-devel] Re: [Linux-fbdev-devel] " Jeff Garzik
2003-10-27 15:50                   ` [Dri-devel] " Keith Whitwell
2003-10-27 15:50                   ` [Dri-devel] Re: [Linux-fbdev-devel] " Keith Whitwell
2003-10-25 21:02             ` Jon Smirl
2003-10-25 21:02               ` [Dri-devel] " Jon Smirl
2003-10-25 22:07             ` [Dri-devel] Re: [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-25 22:07               ` [Dri-devel] " Benjamin Herrenschmidt
2003-10-27 14:01             ` jlnance [this message]
2003-10-27 15:10             ` [Dri-devel] Re: [Linux-fbdev-devel] " Eric W. Biederman
2003-10-27 15:10               ` [Dri-devel] " Eric W. Biederman
2003-10-27 15:10             ` [Dri-devel] Re: [Linux-fbdev-devel] " Keith Whitwell
2003-10-27 15:10               ` [Dri-devel] " Keith Whitwell
     [not found]             ` <20031027114006.A66611@xfree86.org>
2003-10-27 19:38               ` Ian Romanick
2003-10-27 21:32                 ` Linus Torvalds
2003-10-27 23:55                   ` Benjamin Herrenschmidt
2003-10-28  2:13                     ` Linus Torvalds
2003-10-28  3:27                       ` Philip Brown
2003-10-28 19:40                       ` James Simmons
2003-10-28 21:35                         ` Benjamin Herrenschmidt
2003-10-28 22:09                           ` Jon Smirl
2003-10-28 22:26                             ` Benjamin Herrenschmidt
2003-10-28 22:54                         ` Linus Torvalds

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=20031027140142.GA2832@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.