public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: John Gilbert <jgilbert@biomail.ucsd.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATI drivers working under realtime-preempt linux
Date: Tue, 25 Jan 2005 15:59:46 -0500	[thread overview]
Message-ID: <1106686786.10845.58.camel@krustophenia.net> (raw)
In-Reply-To: <41F5CF5D.4060807@biomail.ucsd.edu>

On Mon, 2005-01-24 at 20:47 -0800, John Gilbert wrote:
> Xv isn't supported. DRI isn't supported.
> ATI (and NVIDIA) should be all over the hard-realtime kernel, as this 
> has the potential of making video and games frame accurate (never 
> missing frames, no page tears).
> The documentation from Linux user's web pages are better than ATI's.
> 
> Making this work should have been someone at ATI's job, not mine. I'm 
> working blind here.

Be patient, this stuff is very new and vendors are rightfully
conservative.  They are probably just waiting for the development to
settle down a bit before committing resources to supporting the RT
kernel.

Once some distros start to offer the RT kernel as an option I would
expect a lot of interest from hardware vendors as it really allows the
hardware pushed to its limits.  For example pro audio interfaces are
heavily marketed based on the lowest achievable latency, this will let
them put better numbers on the box, and will probably improve Linux
support a lot, because the marketing will have to be "FooAudio5000, now
featuring 0.6 ms*** usable latency (***Linux RT kernel required, 2.6 ms
under Windows/MacOS)" :-).

Lee


      reply	other threads:[~2005-01-25 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25  4:47 ATI drivers working under realtime-preempt linux John Gilbert
2005-01-25 20:59 ` Lee Revell [this message]

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=1106686786.10845.58.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=jgilbert@biomail.ucsd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox