From: Ondrej Zary <linux@rainbow-software.org>
To: Ondrej Zajicek <santiago@crfreenet.org>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] s3fb: various changes
Date: Tue, 01 Mar 2011 19:17:59 +0000 [thread overview]
Message-ID: <201103012018.01607.linux@rainbow-software.org> (raw)
This patch set adds new hardware support, fixes some display problems and also
improves performance of s3fb driver.
Everything was tested on various Trio32, Trio64V+, Trio64V2/DX, Virge,
Virge/DX, Trio3D and Trio3D/2X cards.
It assumes that David Miller's "Make SVGA oriented FBs work on multi-domain
PCI" patch set is applied.
Signed-off-by: David S. Miller <davem@davemloft.net>
--
Ondrej Zary
WARNING: multiple messages have this Message-ID (diff)
From: Ondrej Zary <linux@rainbow-software.org>
To: Ondrej Zajicek <santiago@crfreenet.org>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] s3fb: various changes
Date: Tue, 1 Mar 2011 20:17:59 +0100 [thread overview]
Message-ID: <201103012018.01607.linux@rainbow-software.org> (raw)
This patch set adds new hardware support, fixes some display problems and also
improves performance of s3fb driver.
Everything was tested on various Trio32, Trio64V+, Trio64V2/DX, Virge,
Virge/DX, Trio3D and Trio3D/2X cards.
It assumes that David Miller's "Make SVGA oriented FBs work on multi-domain
PCI" patch set is applied.
Signed-off-by: David S. Miller <davem@davemloft.net>
--
Ondrej Zary
next reply other threads:[~2011-03-01 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 19:17 Ondrej Zary [this message]
2011-03-01 19:17 ` [PATCH 0/5] s3fb: various changes Ondrej Zary
2011-03-22 6:51 ` Paul Mundt
2011-03-22 6:51 ` Paul Mundt
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=201103012018.01607.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.