From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: James Simmons <jsimmons@linux-fbdev.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: fbcon slowness [was NTP on 2.4.2?]
Date: Sun, 1 Apr 2001 23:35:53 +0200 [thread overview]
Message-ID: <20010401233553.A15813@pcep-jamie.cern.ch> (raw)
In-Reply-To: <Pine.LNX.4.31.0104010752420.736-100000@linux.local>
In-Reply-To: <Pine.LNX.4.31.0104010752420.736-100000@linux.local>; from jsimmons@linux-fbdev.org on Sun, Apr 01, 2001 at 07:54:35AM -0700
James Simmons wrote:
> >No, it's the Trident Cyber9525
>
> Sorry. I only have a early driver for trident 9750 and 9850. Their is a
> gropup working on trident framebuffers.
Is it possible that "jump scroll" would provide more performance benefit
than an accelerated driver anyway?
Seeing as you bring up this topic of writing a 9525 driver. It seems to
me rather wasteful that you (collectively linux framebuffer authors),
XFree86 and Berlin are all writing drivers for the same, hugely diverse
class of hardware, to support more or less the same ops on the hardware.
Isn't possible to pool the development effort of video drivers? Doesn't
X require basically the same set of operations as the kernel? I.e.,
initialise the card and video mode (usually the very complex part); do
some rendering ops (usually fairly simple). Sure, X provides a few more
kinds of rendering op, but that part of the code is usually much simpler
and smaller than the initialisation code.
Sorry if this sounds insulting -- it isn't intended that way. I don't
really know what is involved in writing video drivers. All I am seeing
is an _apparent_ reinventing of a rather complex wheel, when it's hard
enough as it is to keep up with all the different cards.
thanks,
-- Jamie
next prev parent reply other threads:[~2001-04-01 21:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 14:54 James Simmons
2001-04-01 21:35 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-05 3:04 James Simmons
2001-04-05 12:03 ` Eric W. Biederman
2001-04-05 12:12 ` Geert Uytterhoeven
2001-04-05 13:15 ` Maciej W. Rozycki
2001-04-05 18:20 ` Eric W. Biederman
2001-04-06 10:09 ` Ivan Kokshaysky
2001-04-06 13:19 ` Eric W. Biederman
2001-04-06 17:27 ` Maciej W. Rozycki
2001-04-06 18:34 ` Andrea Arcangeli
2001-04-06 19:31 ` Maciej W. Rozycki
2001-04-06 17:13 ` Maciej W. Rozycki
2001-04-08 18:11 ` Ivan Kokshaysky
2001-04-09 10:02 ` Maciej W. Rozycki
2001-04-09 11:05 ` Ivan Kokshaysky
2001-04-06 17:07 ` Maciej W. Rozycki
2001-04-03 2:04 James Simmons
2001-03-31 4:15 James Simmons
2001-03-31 4:11 James Simmons
2001-04-02 22:44 ` Alan Cox
2001-04-03 6:23 ` Geert Uytterhoeven
2001-04-03 12:21 ` Alan Cox
2001-04-04 7:50 ` Eric W. Biederman
2001-04-04 8:47 ` Jamie Lokier
2001-03-31 3:47 James Simmons
2001-03-31 14:15 ` Jamie Lokier
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=20010401233553.A15813@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=jsimmons@linux-fbdev.org \
--cc=linux-fbdev-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®