From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ondrej Zajicek <santiago@crfreenet.org>
Cc: Krzysztof Helt <krzysztof.h1@poczta.fm>,
JosephChan@via.com.tw, akpm@linux-foundation.org,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH 1/9] viafb: VIA Frame Buffer Device Driver - Resend
Date: Thu, 8 May 2008 14:52:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805081452120.8604@anakin> (raw)
In-Reply-To: <20080508081508.GD11121@localhost.localdomain>
On Thu, 8 May 2008, Ondrej Zajicek wrote:
> On Wed, May 07, 2008 at 06:43:33PM +0200, Krzysztof Helt wrote:
> > PS. I assume that your driver will replace the existing vt8623fb (CLE266?) driver when ready. Am I right?
>
> These drivers are hardly comparable. vt8623fb supports CLE266 with VGA output only,
> but allows arbitrary resolutions and pixclocks, high-res text mode and
> (partially) suspend/resume. viafb implements fixed resolutions only and
> have no text mode and no suspend/resume support (according to my quick
> look on it).
It's a pity viafb implements fixed resolutions only. Is there any
specific reason for that?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-05-08 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 11:06 [PATCH 1/9] viafb: VIA Frame Buffer Device Driver - Resend JosephChan
2008-05-07 16:43 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-05-07 21:03 ` Andrew Morton
2008-05-08 0:58 ` JosephChan
2008-05-08 13:24 ` [Linux-fbdev-devel] " Pekka Enberg
2008-05-08 0:51 ` JosephChan
2008-05-08 8:15 ` Ondrej Zajicek
2008-05-08 12:52 ` Geert Uytterhoeven [this message]
2008-05-16 20:22 ` [Linux-fbdev-devel] " Luc Verhaegen
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=Pine.LNX.4.64.0805081452120.8604@anakin \
--to=geert@linux-m68k.org \
--cc=JosephChan@via.com.tw \
--cc=akpm@linux-foundation.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=santiago@crfreenet.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;
as well as URLs for NNTP newsgroup(s).