From: Magnus Damm <magnus.damm@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: jayakumar.lkml@gmail.com, damm@opensource.se,
linux-kernel@vger.kernel.org, armbru@redhat.com, jeremy@goop.org
Subject: Re: [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag.
Date: Fri, 4 Dec 2009 16:42:58 +0900 [thread overview]
Message-ID: <aec7e5c30912032342h1c5b6128jbc28adccc86e5e38@mail.gmail.com> (raw)
In-Reply-To: <1259854318-16907-2-git-send-email-konrad.wilk@oracle.com>
On Fri, Dec 4, 2009 at 12:31 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> Most users (except sh_mobile_lcdcfb.c) get their framebuffer from
> vmalloc. Setting VM_IO is not necessary as the memory obtained
> from vmalloc is System RAM type and is not susceptible to PCI memory
> constraints.
> ---
> drivers/video/fb_defio.c | 4 +++-
> include/linux/fb.h | 1 +
> 2 files changed, 4 insertions(+), 1 deletions(-)
I just tested this on a Migo-R board which is using sh_mobile_lcdcfb.c
in deferred io mode. No problem.
Tested-by: Magnus Damm <damm@opensource.se>
/ magnus
prev parent reply other threads:[~2009-12-04 7:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 15:31 [PATCH] fb-defio: Inhibit setting VM_IO flag if FBINFO_VIRTFB is set Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 2/3] xen pvfb: Inhibit VM_IO flag to be set on vmalloc-ed framebuffers Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 3/3] fb-defio: " Konrad Rzeszutek Wilk
2009-12-04 0:35 ` Jaya Kumar
2009-12-04 0:52 ` Jeremy Fitzhardinge
2009-12-04 1:13 ` Jaya Kumar
2009-12-03 18:50 ` [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag Jeremy Fitzhardinge
2009-12-03 18:56 ` Konrad Rzeszutek Wilk
2009-12-03 19:05 ` Jeremy Fitzhardinge
2009-12-04 0:34 ` Jaya Kumar
2009-12-04 7:42 ` Magnus Damm [this message]
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=aec7e5c30912032342h1c5b6128jbc28adccc86e5e38@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=armbru@redhat.com \
--cc=damm@opensource.se \
--cc=jayakumar.lkml@gmail.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--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®