From: Alan Cox <alan@linux.intel.com>
To: Michael Chang <mchang@novell.com>
Cc: Greg KH <gregkh@suse.de>,
error27@gmail.com, justinmattock@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/gma500: get control from firmware framebuffer if conflicts
Date: Fri, 27 May 2011 09:56:07 +0100 [thread overview]
Message-ID: <20110527095607.5b0b0b7a@bob.linux.org.uk> (raw)
In-Reply-To: <BANLkTi=DYt-Y=151knsQBjBaEJfjqn4ciQ@mail.gmail.com>
> We should let psbfb takeover framebuffer control from vesafb
> to get around this problem.
Looks good to me assuming we have stolen memory. This maybe wants to
test
if (pg->stolen_size)
although I'm not sure that adding a zero size aperture would do harm
any way ? The devices without stolen ram also won't have vesa.
Alan
next prev parent reply other threads:[~2011-05-27 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 7:04 Michael Chang
2011-05-27 8:56 ` Alan Cox [this message]
2011-05-27 9:16 Michael Chang
2011-05-27 9:32 ` Michael Chang
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=20110527095607.5b0b0b7a@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchang@novell.com \
/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
Powered by JetHome