Search results

Yes, so the first thing to be done is setting up a forum section for pyra firmware dev. Everyone shouting random stuff in one thread obviously doesn't work. And this thread was meant to set up the large scale stuff first, not for fighting about implementation details. There is an awful lot of...

Of course it's difficult to pull off, that's why you have to start early with these things. And these things don't have to be taken to extreme levels, just that there must be some way for a complete outsider to join in. Take the .next stuff for example. Despite beeing something hardly anyone...

Well this thread is a start, and there are already people offering their help and ideas. Of course there's a big difference between doing a bit of complaining on a forum, and actually doing stuff, but we should be able to come up with a few more people. Just because things didn't that smoothly...

This thread was meant as call to set up the whole development movement, and to point out what imo is the most important bit of a new device. Talk about details like pnd successors and the other things should be happening in a development section on the pyra forums, which should have been set up...

Yes, hence the "Attracting as many people as possible" bit. :) Not to mention trying to keep them involved.. a lot of the people who did stuff for the pandora firmware in the beginning have never done anything for it after that. Dumping some old firmware in a chroot is the worst option...

With all this talk here about how great and wonderful the hardware will be, it means nothing if there isn't a solid software foundation to run on it. Although I did see a few topics about software, they're mostly general "which distro" and "which apps to include" posts. As we saw with the...

already fixed the problem, added libpng12 to the packagegroup for the image, and firefox works.

look in tmp/pndrun*.out in this case it's /tmp/pndrun_hdonk_firefox_001.out XPCOMGlueLoad error for file /mnt/utmp/hdonk_firefox_001/lib/firefox-26.0/libxul.so: libpng12.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. So more upgraded library fun, with the...

Image built, uploaded, opkg update/upgrade, reboot, and networkmanager appears to work.

pulled in, and creating a new image.. i also synced the setup-scripts with angstrom, nothing major in there, but you'll need to pull those in to get the most recent layers.txt. Also, consider joining #openpandora on freenode, i'm usually there, and it makes communicating a bit faster than a...

and there's this : http://projectne10.github.io/Ne10/ Haven't used it myself though

pulled them in and it's now building the image... it'll be a while since it thinks it has to rebuild all of qt4

and it's not just pnds, running the networkmanager config also triggers it, but i already mentioned that a few posts ago

It might be, i didn't spend too much time trying to get rid of the warning, but since some stuff just depends on mesa it's not going to be any fun. It's been a while so i'm not entirely sure, but i think you even got that warning when using the drivers from meta-ti

I still have to dig into that, the gles stuff did work before the move to 2013.06 , so it might be something broke there

They won't work on all pandoras. The problem there is that they don't care about the driver for anything other than the latest chip revision. They just make sure you get a somewhat working driver if you buy a new chip from them, for old stuff, you're just lucky if it still works at all. Only...

.next already has all the proper recipes for most of that, it's the main reason the whole thing was started. It avoids most of it by making the 3.2 kernel the default, and ignoring the 2.6 one.

Anyway, I did manage to build a working image, with a lot of hacking about. I'm currently trying to find some nicer solutions for some things. There are only a few major problems, mostly perl-native , squashfs-tools and some dsp related stuff, and the easy solution there is just to not have...

it should be the nokia branch, but i can't find a reference to it in any of the recipes.. either i'm not looking hard enough, or it's manually built and extracted on top of the finished image by the magical tgz file. edit: make that magical tar.bz2 , and it seems it does get built outside of...

I'm documenting all the fails and hacks to get past them, proper fixes will take a bit longer, but first i want to see what fails. I do remember getting some serious problems later on, but then again, that was years ago and i'm slightly more familiar with oe now thanks to all the .next work.