From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Frame buffer mmap not working in pvops dom0
Date: Wed, 28 Jul 2010 10:29:12 -0400 [thread overview]
Message-ID: <20100728142912.GA6817@phenom.dumpdata.com> (raw)
In-Reply-To: <4C47584F.1000200@tycho.nsa.gov>
> > If that fixes your problem, are you OK with me sticking a Signed-off-by:
> > from you on this patch?
> >
>
> Yep, your version also fixes the problem, and I agree it's more
> sensible. I'm OK with signing off on that patch.
Oh, and here is the S-O-B that I missed sticking on the git tree.
Anyhow, I found out that his patch also fixes the Nvidia fb problem,
which is quite nice.
By any chance did you try to use Xserver on top of this patch? In the
past I had gotten this (from Xorg.0.log file):
==) Using config directory: "/etc/xorg.conf.d"
(XEN) mm.c:1747:d0 Bad L1 flags 400000
(XEN) mm.c:1747:d0 Bad L1 flags 400000
(XEN) mm.c:1747:d0 Bad L1 flags 400000
...
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
.. and a continuing stream of FBIOPUTCMAP's.
next prev parent reply other threads:[~2010-07-28 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 13:47 Frame buffer mmap not working in pvops dom0 Daniel De Graaf
2010-07-21 14:16 ` Pasi Kärkkäinen
2010-07-21 14:42 ` Konrad Rzeszutek Wilk
2010-07-21 14:49 ` Pasi Kärkkäinen
2010-07-21 15:26 ` Daniel De Graaf
2010-07-21 19:00 ` Konrad Rzeszutek Wilk
2010-07-21 19:12 ` Konrad Rzeszutek Wilk
2010-07-21 19:22 ` Daniel De Graaf
2010-07-21 19:50 ` Konrad Rzeszutek Wilk
2010-07-21 20:27 ` Daniel De Graaf
2010-07-28 14:29 ` Konrad Rzeszutek Wilk [this message]
2010-07-28 15:33 ` Konrad Rzeszutek Wilk
2010-07-28 18:09 ` Daniel De Graaf
2010-07-21 20:36 ` Eamon Walsh
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=20100728142912.GA6817@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).