Okay, as mentioned, I took my time tonight to look why X is so much
faster with the Yocto image compared to Debian, and I think I found the
reason.
First, I changed the Debian installation to use the driver "omap"
instead of fbdev and copied the configuration over from the Yocto
rootfs.
That sped things up a bit and made xrandr usable, but it was still
slower then on Yocto.
With xrandr I could switch the resolution to 1280x720 and even 640x480,
but it didn't increase the speed. Moving windows around was still
stuttery, so it doesn't seem like a memory / bandwidth issue.
Checking /var/log/Xorg.0.log revealed what the real issue is:
On Debian, there is only the basic omap driver installed.
It lacks DRI, DRI2 and PVR2D / XV drivers from TI.
It clearly says it in the logfile ("XV not initialized" "Couldn't load
submodule omap_pvr", etc.)
On the Yocto, it successfully initializes XV, DRI2, etc.
Unfortunately, Yocto uses X 1.11 and Debian 1.15, so I couldn't copy
over the modules for testing.
It means however, that the slowness comes from missing OMAP driver
modules, so we'd need to include them.
Seems like there's an Ubuntu Package:
https://gitorious.org/ubuntu-omap/pvr-omap5/source/7b9f231fb44c03bc02f42b6b…
There's also a prebuilt-OMAP5-Debian-Image available:
http://elinux.org/BeagleBoardDebian#OMAP5432_uEVM
Haven't checked whether they have the drivers included or not though.
--
Mit freundlichen Grüßen,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
ICQ: 15691903
MSN: EvilDragon1717(a)hotmail.com
eMail: info(a)openpandora.de
Hi,
before we start, we need some kind of working GIT and Bugtracker setup.
Right now, on my server, we got basic GIT and gitweb running, but
setting up different users and giving them access is a bit of a pain in
the ass - and Flyspray doesn't seem to be the best bugtracker as well.
Something like our own GITHub, where we can easily setup GITs for the
packages and have an issue tracker built-in as well might be good.
DJWillis mentioned Allura and Gitorious here:
https://forge-allura.apache.org/p/allura/git/ci/master/tree/http://www.getgitorious.com/
Maybe anyone here has other ideas? Allura seems to be run on
VirtualBox... possible, but maybe a bit overkill...?
Let me know what you think would be best and I'll set it up.
--
Mit freundlichen Grüßen,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
ICQ: 15691903
MSN: EvilDragon1717(a)hotmail.com
eMail: info(a)openpandora.de
Hi,
I installed the official TI Yocto Demo image and started it on the
OMAP5 EVM, mainly as X is running very slow on Debian right now and I
wanted to see whether this is Debian or already a hardware limitation.
The default Yocto doesn't have much installed (need to test more
tonight), but I ran X with openbox and a terminal which I could move
around.
FullHD with 1920x1080.
X needed about 0-4% CPU time (a lot better than on Debian) and moving
windows around was blazing fast (and needed about 10% CPU time for a
very short period of time).
Moving the window around like hell increased the CPU time to 40% but
still was without stuttering or hangs, whereas on Debian, even doing
that with small windows increased the CPU time of X to 80 - 90% and it
was really slow.
So it seems something seems to be wrongly setup with our current
rootfs, but I'll check that.
Tonight, I'll try to install XFCE on the yocto image and test again.
I'll also check their X config to see if we can reuse it for Debian.
Right now it seems something slows down our Debian X a lot.
--
Greetings,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
ICQ: 15691903
MSN: EvilDragon1717(a)hotmail.com
eMail: info(a)openpandora.de
Hi,
well, it seems DJWillis can now finally receive the mailing list as
well (at least he got the welcome-eMail), so time to start with setting
up the server for the OS.
We also got a new member: ati from the boards (nothing to do with the
graphic card ;)), and I wish to welcome him as well.
I'll try to summarize what we plan to do (aTc, please correct me if
something is wrong, I'm not sure yet I understood it all completely).
The goal is:
Get a flashable Debian image with a default configuration for the Pyra
(or the devboard, to begin with).
To do that, we'll use the Debian Multistrap way.
We plan to stick as close with standard Debian as possible.
We will have our own repository which has Pyra-optimized packages as
well as our own stuff (like libpnd, helper scripts / tools, etc.).
With patched packages, we need to think about how to name them:
1. Name the different than the original packages but have the same
PROVIDEs (i.e. libSDL-pyra)
Not sure how apt-get handles this if you want to install a package
though which has a libSDL-dependency. Would it ask whether to install
libSDL-pyra or libSDL, could we set it up to automatically prefer the
one from our repository, or will it bring an error because two
different packages have the same PROVIDE?
2. Name it the same as the original package, but give our repository a
higher priority.
Would work, but I think this is a bit unclean - so I guess 1. is the
way to go.
Each package we patch or provide will have its own GIT (as Debian
git-package wants it like that).
Now comes the part where I'm not sure I understood it correctly, so
please correct me where need be :)
The OMAP5-Devboard at my place at home will clone the GITs with the
packages, compile the changed / new ones and upload the finished
packages into our repository.
What I'm not sure is how to create a finished rootfs from that, and how
and where we define which packages should be included, etc.
The first step should be setting it up so we can get an automatically
created basic rootfs for the devboard, and then continue to add patches
and packages.
Does that sound like a good approach?
--
Greetings,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
ICQ: 15691903
MSN: EvilDragon1717(a)hotmail.com
eMail: info(a)openpandora.de