xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Suriyan Ramasami <suriyan.r@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	xen-users@lists.xen.org
Subject: XEN/ARM XENFB howto
Date: Mon, 18 Aug 2014 11:03:43 -0700	[thread overview]
Message-ID: <CANoR_ODEpsKk1YrrBkVofQgw+huOGSaCruUOvG3fz7gY9A8s5Q@mail.gmail.com> (raw)

Hello,
   This possibly could be a resend, as I did not see my post (that I
emailed out on Aug 17).
   I am looking for documentation on how to use XENFB on ARM. I did
see a post dated Dec 2013 from Peter
(http://lists.xen.org/archives/html/xen-users/2013-12/msg00061.html)
and discussions with Steffano and
Ian on how to achieve it. But, its not clear to me.

   I am trying to achieve this on the Odroid-XU (ARM based Exynos
5410). I am looking for the following:

1. qemu compilation upstream - I believe this has all the bits to
achieve it. Are there any special compile options. I ask this, as
qemu-system-arm seems to be spawned in dom0 with -M xenpv and I am not
able to compile this machine in qemu.
I do configure to build qemu with --enable-xen --target-list
arm-softmmu and the other options as mentioned in
http://wiki.xen.org/wiki/QEMU_Upstream#Building_your_own_qemu.

Note that I am not trying to cross compile but am compiling qemu natively.

2. What are the options in the domU2 config file to achieve this.

3. Any thing else ... Like when domU2 is created, what mice/keyboard/fb
messages to look for, or in dom0 what backend driver output to look
for. Does this need a xorg.conf file etc ...

Thanks in advance
- Suriyan

             reply	other threads:[~2014-08-18 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 18:03 Suriyan Ramasami [this message]
2014-08-21 22:22 ` XEN/ARM XENFB howto Stefano Stabellini
2014-08-23  4:26   ` Suriyan Ramasami
2014-08-23 19:16     ` Stefano Stabellini

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=CANoR_ODEpsKk1YrrBkVofQgw+huOGSaCruUOvG3fz7gY9A8s5Q@mail.gmail.com \
    --to=suriyan.r@gmail.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.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).