From: Jon Smirl <jonsmirl@yahoo.com>
To: Keith Whitwell <keith@tungstengraphics.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, 6 Aug 2004 10:46:45 -0700 (PDT) [thread overview]
Message-ID: <20040806174645.77462.qmail@web14924.mail.yahoo.com> (raw)
In-Reply-To: <4113BDC0.6050604@tungstengraphics.com>
--- Keith Whitwell <keith@tungstengraphics.com> wrote:
>
> Sorry, I don't buy it. Graphics drivers are a special case and
> people upgrade them with a passion... No new interfaces, thankyou.
I get a new kernel from Redhat about every two weeks. Redhat is at
2.6.7 and Linus is at 2.6.8. Nobody releases graphics drivers faster
than that. Why do you want to build a new release mechanism that
bypasses the kernel one?
If people are upgrading faster that every two weeks I would classify
them as developers or people that can deal with broken drivers. That
class of person can deal with pulling the code from CVS and copying it
into their kernel tree.
There are three main ways to get a driver:
1) vendor release - most stable, I get one every two weeks
2) Linus bk - very up to date, not as well tested, once a day
3) copy DRM CVS into Linus bk - bleeding edge, hope you know what you
are doing.
Besides, DRM drivers are relatively stable. It's the user space stuff
that is volatile.
>
> Keith
>
>
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-08-06 17:48 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
2004-08-06 17:46 ` Jon Smirl [this message]
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=20040806174645.77462.qmail@web14924.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.com \
--cc=keith@tungstengraphics.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
all inboxes | Powered by JetHome®