mali
-
(PND continued from post above)
skeezix said:It's an ISO that can also be squashfs'ed.The filesystem in the pnd can be many things; iso is one, cramfs is others; its not all pnds are one type,.. its just a given pnd may be one type, and another pnd may be another type, up to developer preferences.
In theory, we can support dozens of filesystem types, but in practice we're only supporting a few right now. (its purely a 'magic' file thing, in pnd_run.sh, really.)
Even windows can make cramfs (we do it
jeff
As to post-release.. I'm not a pnd-nazi; libpnd we've made and LGPL'd, peopel can go nuts I'd liek sensible reviewed alteratins and additions .. no need to go hog wild and break it all day-2, but whatever. Extensions, changes, even long term changes.. all good.
-----------------------------------------
also..
You can just stick pnd files in any old directory you want; you don't have to use the menu or desktop auto-icon business at all .. you can stick them into /games on your SD, and then just use the file browser and double-click on the pnd you want in there to run it.
No one is forcing you into anything
What we are doing is making automagic instant easy to use behaviour an option ... seems desirable to me, but you don't have to use it
-----------------------------------------
Also, we're ignoring one of the big benefits.. pnd is drag and drop and play. PEople are really asking about.. wanting it more like windows? _Windows_? With dlls in one place, apps in another, your user data in a third place, your registry entries, and home-doir hidden stuff? And oyu have to run an installer and an uninstaller?
We have that beat Stick your pnd files in one place (or any place you want really), and your data all goes to one folder, with a subfolder per app. ITs easy to back up, easy to delete, and all automatic.
The only case I can see here, and its an interewsting idea, is to make the appdata-dir be the same dir as the pnd-file, as an option; that'd not be too hard a change, but lets leave that as a post-release feature request. Right now, all pnd user data will go to /pandora/appdata/app-name; in the future, if you want it so /games/foo.pnd writes its appdata to /games/foo/, we or someone can code it in; its a change to pnd_run.sh really, and maybe a conf file to toggle it.
As it is, its a very good system; whats going on here is 'bike shed' -- arguign over little details
(Pandora SDK)ED(tweet) said:I uploaded a YouTube video -- Pandora: Surfing the web, doing some messenging and eMailing http://youtu.be/1QUDH-Ii8Cc?a
skeezix said:I sent the 'WORK IN MOTION' set of libs to atiti there, so now you have .. CSL + usual headers + some arm libs to link against + libpnd -- so you can complete your VM (or just use cygwin, or build your own gcc, or whatever
jeff
atiti said:Hi guys,
I've torrented up the stuff skeezix has put up and its now available at:
http://www.patup.com/torrent/1841/Pandora%20Feb23%20ARM%20libs%20-%20Skeezix.html
Or a direct link to the torrent:
http://www.patup.com/dl/1841/pandora-feb24-usrlib.tgz.torrent
Happy leeching!
EDIT:
!!OH yes, please read this!!:
"This is purely a set of random ARM-built libs for pandora image;
they _will_ change (more libs coming, possibly some dropping, and likely some version changes.)
I've also done some symlinking to make them easier to link against with gcc and CSL-gcc.
I compile and link against these quite often, and drag tgh resulting binary over to real pandora devboards and works great
Combine these + Codesourcery + linux headers == win! "
P.S.: Thanks skeezix
(Cpasjuste)Pandora Sdk Installer An unofficial pandora toolchain/sdk installer for debian/ubuntuskeezix said:That's a snapshotand will change as I said
it is git/cvs pulled, with manual versions bumps..
Future os versions will only add libsand versions, not remove, and as space permitswe'll follow versions
jeffphone
(Midori CSS bug)Cpasjuste said:Hi, i did re-write my little pandora toolchain/sdk scripts for an easier and better installation.
This stuff is writed/tested for deb based distributions ( debian, ubuntu ... ), 32 and 64 bits.
It comes in 3 files :
toolchain.sh : will download and install codesourcery arm toolchain ( arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 ) and set the PNDSDK path variable ( /usr/local/pandora/arm-2007q3 ). It can be used alone to install the basic toolchain.
pnd_libs.sh : will download and install some libraries from the angstrom repository, based on the third file list. It need the "libraries.list" file.
libraries.list : a list of libraries URL from angstrom repo. So if pnd_libs.sh script isn't too crappy, we (you) should only need to update this list to update.
I encourage you to report me libraries that may miss you ( i just added a very few one for gles, x11 and sdl ), if they are part of the actual pandora base image, i'll add them to the "libraries.list" file.
The "toolchain.sh" script and "pnd_libs.sh" scripts will leave a "tmp" directory where it was launched with downloaded stuff, you can safely delete it.
toolchain.sh
pnd_libs.sh
libraries.list
(automatic clock setting)EvilDragon said:Nope, it's fixed on normal Linux desktop, just didn't make it into the Angström repo yetNa-Noo said:Did ED's vid say that there's a css bug that's been fixed in the windows version but hasn't made it to the linux version yet?
skeezix said:Elanzer said:Ideally you would want to run a shell script upon execution of each program which configures all the clocks to their optimal speeds for each emulator.
Like if SNES emulation can run fine at 300mhz OPP2 or something like that with the SGX clocked at 55mhz, you'd save a good amount of battery life, then upon closing the emulator, trigger the usual speeds needed for basic desktop/browsing type use. Likely you could keep the SGX at 55mhz and only ramp it up for things that even need 3D.
There are so much possibilities to further extend battery life beyond the 10 hours, it sounds like much more will be possible after software gets optimized.
That is in fact what happens more or less .. if a pnd-file requests 200mhz (say), and that is allowed by the user, then the system downclocks, runs the pnd, and restores clock on exit. Sort of goofy if you're running 5 apps at once, but the user knows the risk of doing that (ie: slowing down other apps, and the whole risk of running 5 apps at once, etc.) Anyway, yeah, we do that
When the LCD is closed, we turn off the screen (but leave clock alone in case you're burnjing thrugh mp3s, say.) But if your mp3 player mneeds only 100mhz, set up a pnd for it that requests that, and bam, every time you run your mp3 player, you're running at 100mhz; close the lid, and you're talking pretty low consumption
Theres lots of options..
jeff
Last edited by a moderator: