mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Whitwell <keith@tungstengraphics.com>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Ian Romanick <idr@us.ibm.com>, Dave Airlie <airlied@linux.ie>,
	"DRI developer's list" <dri-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: DRM function pointer work..
Date: Fri, 06 Aug 2004 18:20:00 +0100	[thread overview]
Message-ID: <4113BDC0.6050604@tungstengraphics.com> (raw)
In-Reply-To: <20040806171641.14189.qmail@web14928.mail.yahoo.com>

Jon Smirl wrote:
> --- Keith Whitwell <keith@tungstengraphics.com> wrote:
> 
>>Ian Romanick wrote:
>>
>>>Jon Smirl wrote:
>>>
>>>
>>>>The only case I see a problem is when drm-core is compiled into
>>>>the kernel. Why don't we just change the Makefile to default to
>>>>copying the CVS code into the kernel source tree and tell the 
>>>>user to rebuild his kernel? 
>>>
>>>
>>>I don't think that will fly with Joe-user that just wants to
>>>upgrade his graphics driver.  The other problem case is if the 
>>>user has two graphics cards in his system.  He wants to upgrade
>>>the driver for one of them (or install a new driver for a new 
>>>card), but the interface between the device-independent 
>>>(in-kernel) layer and the device-dependent (in-kernel) layer 
>>>has changed.
> 
> 
> fbdev is in exactly this model and it isn't causing anyone problems.
> The simple rule is that if you want to upgrade fbdev past the current
> version you have to do it in entirety. You do that for fbdev but
> pulling bk://fbdev.bkbits.net/. But Joe user doesn't do that, that is
> something only developers do.
> 
> Distributions release new kernels all of the time. If Joe wants to
> upgrade he graphics driver he should wait until we push it into the
> kernel and it arrives via his distribution. If he really wants to be
> bleeding edge he can copy the entirety of the DRM CVS into his kernel
> tree. 
> 
> Linux doesn't have a stable driver binary interface. It isn't meant for
> you to be able to upgrade one module while keeping the core and an
> older module.
> 
> The key here is that distributions release new kernels at a rapid pace.
> This is not X where we get a new release every five years. The standard
> mechanism for upgrading device drivers in Linux is to add them to the
> kernel and wait for a release.  If DRM uses that mechanism for
> distribution we won't have problems.

Sorry, I don't buy it.  Graphics drivers are a special case and people upgrade 
them with a passion...  No new interfaces, thankyou.

Keith


  reply	other threads:[~2004-08-06 17:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040806024907.13024.qmail@web14923.mail.yahoo.com>
2004-08-06 16:32 ` Ian Romanick
2004-08-06 16:54   ` Keith Whitwell
2004-08-06 17:16     ` Jon Smirl
2004-08-06 17:20       ` Keith Whitwell [this message]
2004-08-06 17:46         ` Jon Smirl
2004-08-07 22:42           ` Dave Jones
2004-08-06 17:24       ` Keith Whitwell
2004-08-06 17:48         ` Jon Smirl
2004-08-07  0:11       ` Dave Airlie
2004-08-07 14:47         ` Christoph Hellwig
2004-08-07 13:31       ` Alan Cox
2004-08-07 14:48         ` Christoph Hellwig
2004-08-07 14:46     ` Christoph Hellwig
     [not found] <Pine.LNX.4.58.0408031427540.31513@skynet>
     [not found] ` <Pine.LNX.4.58.0408041201490.30393@skynet>
     [not found]   ` <41128B90.5070702@us.ibm.com>
     [not found]     ` <Pine.LNX.4.58.0408052338010.9947@skynet>
     [not found]       ` <4112C09B.1070603@us.ibm.com>
2004-08-05 23:54         ` Dave Airlie
2004-08-07 14:43           ` Christoph Hellwig

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=4113BDC0.6050604@tungstengraphics.com \
    --to=keith@tungstengraphics.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.com \
    --cc=jonsmirl@yahoo.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

Powered by JetHome