From: Andy Lutomirski <luto@MIT.EDU>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 0/4] efifb speedup and fixes
Date: Thu, 26 May 2011 14:13:30 +0000 [thread overview]
Message-ID: <cover.1306418703.git.luto@mit.edu> (raw)
Fbcon over efifb is so slow that I thought I needed a faster modem.
It turns out that scrolling boot messages at 1024x768 pixels with
uncached accesses can take longer than every other step of kernel
bootup *combined*.
Fixing it is a one-liner, but I found some bugs while I was digging
around. One is a mismatched resource release (although not on my
box), one is a harmless compiler warning, and one fixes all manner of
badness that happens if you manually bind or unbind the efifb driver.
The speedup may or may not be 2.6.40 material, but the other fixes
should probably go in. (2/4 and 4/4 are possibly -stable candidates.)
Andy Lutomirski (4):
efifb: Enable write-combining
efifb: Fix mismatched request/release_mem_region
efifb: Fix an integer-to-pointer size warning
efifb: Disallow manual bind and unbind
Andy Lutomirski (4):
efifb: Enable write-combining
efifb: Fix mismatched request/release_mem_region
efifb: Fix an integer-to-pointer size warning
efifb: Disallow manual bind and unbind
drivers/video/efifb.c | 39 +++++++++++++++++++++++++--------------
1 files changed, 25 insertions(+), 14 deletions(-)
--
1.7.5.1
next reply other threads:[~2011-05-26 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 14:13 Andy Lutomirski [this message]
2011-06-02 8:20 ` [PATCH 0/4] efifb speedup and fixes Paul Mundt
2011-06-02 17:04 ` Peter Jones
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=cover.1306418703.git.luto@mit.edu \
--to=luto@mit.edu \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).