From: Will Drewry <wad@dataspill.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] X11 vfb forward ported to 3.2
Date: Thu, 21 Jun 2012 15:56:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20120621T174831-991@post.gmane.org> (raw)
In-Reply-To: 4F3C1B06.7080506@nagafix.co.uk
Antoine Martin <antoine <at> nagafix.co.uk> writes:
>
> Whilst I was looking at all the docs and patches that I have for the
> wiki/uml website, I found the old x11-fb patch from Gerd Knorr's and
> forward ported it to 3.2
> Got as far as the point where it builds and shows a window when you
> start the kernel with:
> ./vmlinux x11=800x600
> As reported at the time of the original patch, all I get is a black
> window... I'll try to see if I can figure out why it's not updating.
> Here it is if you want to try it / comment / help:
> http://uml.devloop.org.uk/vfb-3.2.patch
I was just playing with this the other evening. I tweaked your/Gerd's patch in a
few places (using it on 3.5.0-rc2), but the main non-porting related change
seems to be in the nopage helper. It uses pgoff as if it were the virtual
address instead of as a direct offset for the VMA. Fixing that got me a working
fb.
I've only tested with the test program from here:
http://cep.xor.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-
testingframebuffer.html
which draws a gradient.
Here's the tiny tweak (which is not stylistically correct, etc):
@static int
@x11_fb_vm_nopage(struct vm_area_struct *vma, struct vm_fault *vmf)
@{
...
->-------int pgnr = (vmf->pgoff - vma->vm_start) >> PAGE_SHIFT;
+>-------unsigned long pgnr = vmf->pgoff;
Not sure if anyone still cares, but if I end up getting it more cleaned up, I'll
post a 3.5 port in a weekend in the near future :)
cheers!
will
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2012-06-21 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 20:52 [uml-devel] X11 vfb forward ported to 3.2 Antoine Martin
2012-06-21 15:56 ` Will Drewry [this message]
2012-06-21 18:26 ` richard -rw- weinberger
2012-06-21 19:45 ` Will Drewry
2012-06-21 20:07 ` richard -rw- weinberger
2012-06-22 19:26 ` Will Drewry
2012-06-23 19:46 ` Will Drewry
2012-06-22 8:28 ` Ron Yorston
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=loom.20120621T174831-991@post.gmane.org \
--to=wad@dataspill.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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