From: Filip Navara <filip.navara@gmail.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PXA2xx LCD vs. dedicated framebuffer
Date: Fri, 19 Jun 2009 16:26:01 +0200 [thread overview]
Message-ID: <5b31733c0906190726obea19d3sf0d0a241ad545c97@mail.gmail.com> (raw)
In-Reply-To: <20090619100412.GA5683@avionic-design.de>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Fri, Jun 19, 2009 at 12:04 PM, Thierry Reding <
thierry.reding@avionic-design.de> wrote:
> I'm working on adding support to QEMU for some of the boards that the
> company
> I work for develops. The boards have a PXA270 and an FPGA to implement
> additional functionality, such as a dedicated graphics controller. The
> problem I'm facing now is that whenever the dedicated graphics controller
> is
> initialized in QEMU it registers as a secondary DisplayState because the
> PXA2xx LCD is already present.
>
> Is there a way to make QEMU ignore the PXA2xx LCD or prefer the dedicated
> controller as primary DisplayState? The only way I could find was to
> comment
> out the PXA2xx LCD initialization or patch the sources to disable the LCD
> using a flag during PXA2xx setup.
>
> Thierry
As far as I know there's currently no way to achieve it except for
commenting out the code or changing the order of initialization. Note that
once the "devtree" patch is merged and the PXA2xx code is migrated to it
then it will be possible to create a machine description that will not
contain the LCD controller. Such machine description doesn't require
recompiling of whole QEMU to use it.
Best regards,
Filip Navara
[-- Attachment #2: Type: text/html, Size: 1598 bytes --]
next prev parent reply other threads:[~2009-06-19 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 10:04 [Qemu-devel] PXA2xx LCD vs. dedicated framebuffer Thierry Reding
2009-06-19 14:26 ` Filip Navara [this message]
2009-06-22 6:37 ` Thierry Reding
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=5b31733c0906190726obea19d3sf0d0a241ad545c97@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=thierry.reding@avionic-design.de \
/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).