From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: torvalds@linux-foundation.org
Cc: Paul Mundt <lethal@linux-sh.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fbdev@vger.kernel.org
Subject: [GIT PULL] viafb updates
Date: Sun, 22 May 2011 18:59:21 +0000 [thread overview]
Message-ID: <4DD95D51.6010100@gmx.de> (raw)
Hi Linus,
as Paul Mundt, the fbdev maintainer, has been inactive for several weeks now, I
ask you to pull these viafb updates for 2.6.40 from
git://github.com/schandinat/linux-2.6.git viafb-next
They contain major cleanups, a better PLL/clock management and some notable
changes for users like write-combining speeding userspace apps up to a factor
around 6 (on newer hardware) and other things making viafb more likely to work.
Also some important changes to make it work on OLPC XO 1.5 (again).
This stuff has been in linux-next for some time.
Thanks,
Florian Tobias Schandinat
Daniel Drake (1):
viafb: Automatic OLPC XO-1.5 configuration
Florian Tobias Schandinat (26):
viafb: move initialization code
viafb: no need to write CRTC values twice
viafb: kill crt_setting_information
viafb: allow some pll calculations
viafb: remove unused max_hres/vres
viafb: call viafb_get_clk_value only in viafb_set_vclock
viafb: prepare for PLL separation
viafb: add clock source selection and PLL power management support
viafb: add primary/secondary clock on/off switches
viafb: split clock and PLL code to an extra file
viafb: add VIA slapping capability
viafb: add engine clock support
viafb: gather common good, old VGA initialization in one place
viafb: some small cleanup for global variables
viafb: replace custom return values
viafb: delete clock and PLL initialization
viafb: fix OLPC DCON refresh rate
viafb: fix OLPC XO 1.5 device connection
viafb: reduce OLPC refresh a bit
viafb: add X server compatibility mode
Merge branch 'viafb-olpc' into viafb-next
Merge branch 'viafb-cleanup' into viafb-next
Merge branch 'viafb-pll' into viafb-next
viafb: use write combining for video ram
viafb: try to map less memory in case of failure
viafb: remove unused CEA mode
drivers/video/Kconfig | 11 +
drivers/video/via/Makefile | 2 +-
drivers/video/via/chip.h | 6 -
drivers/video/via/dvi.c | 160 +----------
drivers/video/via/dvi.h | 2 +-
drivers/video/via/global.c | 4 -
drivers/video/via/global.h | 2 -
drivers/video/via/hw.c | 630 ++++++++++++++---------------------------
drivers/video/via/hw.h | 15 +-
drivers/video/via/lcd.c | 23 +-
drivers/video/via/lcd.h | 2 +-
drivers/video/via/share.h | 17 +-
drivers/video/via/via-core.c | 9 +-
drivers/video/via/via_clock.c | 349 +++++++++++++++++++++++
drivers/video/via/via_clock.h | 76 +++++
drivers/video/via/viafbdev.c | 62 +++--
drivers/video/via/viafbdev.h | 4 -
drivers/video/via/viamode.c | 46 +---
drivers/video/via/viamode.h | 9 -
19 files changed, 723 insertions(+), 706 deletions(-)
create mode 100644 drivers/video/via/via_clock.c
create mode 100644 drivers/video/via/via_clock.h
reply other threads:[~2011-05-22 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DD95D51.6010100@gmx.de \
--to=florianschandinat@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).