https://pandorawiki.org/api.php?action=feedcontributions&feedformat=atom&user=GlennPandora Wiki - User contributions [en]2026-04-23T16:19:22ZUser contributionsMediaWiki 1.32.0-alphahttps://pandorawiki.org/index.php?title=Software_projects&diff=2017Software projects2010-01-10T21:02:17Z<p>Glenn: +cat</p>
<hr />
<div>See the [[Port Requests]] article for open-source projects which ''could'' be ported but have not been taken on by anyone yet.<br />
<br />
== Operating Systems ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Android Omap<br />
|[http://elinux.org/Android_on_OMAP Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|Angstrom Linux<br />
|[http://www.angstrom-distribution.org/ Link]<br />
|Working build, not completed<br />
|<br />
|<br />
|-<br />
|AROS Arm<br />
|[http://projects.powerdeveloper.org/project/imx515/735 Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|FreeBSD<br />
|[http://wiki.freebsd.org/FreeBSD/arm/OMAP Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|Fedora ARM<br />
|[http://fedoraproject.org/wiki/Architectures/ARM Link]<br />
|wip<br />
|<br />
|<br />
|<br />
|-<br />
|Gentoo Linux<br />
|[http://gentoo.openpandora.org Link]<br />
|Working build, not completed<br />
|javaJake, Viridior<br />
|IRC: (FreeNode) #gentoo-pandora<br />
|-<br />
|HaikuOS<br />
|[http://www.haiku-os.org Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|RISC OS<br />
|[http://www.riscosopen.org Link]<br />
|wip<br />
|Uwe Kall, Jeffrey Lee<br />
|BeagleBoard port available for download and testing<br />
|-<br />
|Ubuntu ARM<br />
|[http://www.ubuntu.com/products/whatisubuntu/arm Link]<br />
|wip<br />
|<br />
|}<br />
<br />
== Games ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Abuse<br />
|[http://abuse.zoy.org/ Link]<br />
|working build<br />
|Cpasjuste<br />
|2D Platform<br />
|-<br />
|Aleph One<br />
|[http://www.youtube.com/watch?v=1zQ7Fbwhb5I/ Link]<br />
|WIP<br />
|Pickle<br />
|FPS<br />
|-<br />
|Battle for Wesnoth v1.6.2<br />
|[http://www.gp32x.com/board/index.php?showtopic=47936 Link]<br />
|working build<br />
|Cpasjuste<br />
|Strategy<br />
|-<br />
|BattleJewels<br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Skeezix<br />
|Logical<br />
|-<br />
|BlobWars<br />
|[http://www.parallelrealities.co.uk/projects/blobWars.php Link]<br />
|working build<br />
|Cpasjuste<br />
|2D Platform<br />
|-<br />
|Caster<br />
|[http://www.gp32x.com/board/index.php?showtopic=46813 Link]<br />
|Working build (tested on PC)<br />
|Svartalf<br />
|RPG<br />
|- <br />
|CDogs<br />
|<br />
|WIP<br />
|Pickle<br />
|Top down Shooter<br />
|-<br />
|Chaotic Vortex<br />
|[http://www.gp32x.com/board/index.php?/topic/49754-chaotic-vortex-dual-stick-arena-shooter Link]<br />
|WIP<br />
|Ruben<br />
|Dual stick 2D shooter<br />
|-<br />
|Descent 1 (d1x-rebirth engine)<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1032 Link]<br />
|Working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Descent 2 (d2x-rebirth engine)<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1032 Link]<br />
|Working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Eternity 6: The Waterphoenix<br />
|[http://www.gp32x.com/board/index.php?/topic/50772-eternity-6-the-waterphoenix/ Link]<br />
|WIP<br />
|Darien<br />
|Side Scroller / Beat 'Em Up<br />
|-<br />
|FHeroes Port (Heroes Of Might And Magic 2)<br />
|[http://www.gp32x.com/board/index.php?showtopic=47553 Link]<br />
|Working build<br />
|Pickle<br />
|Strategy<br />
|-<br />
|FreeCiv 2.1.9<br />
|[http://freeciv.wikia.com/wiki/Main_Page Link]<br />
|Working build<br />
|Cpasjuste<br />
|Strategy<br />
|-<br />
|Galactic Artifact<br />
|[http://www.gp32x.com/board/index.php?showtopic=46836 Link]<br />
|Working build<br />
|Trevor Bradley<br />
|Strategy<br />
|-<br />
|GemRB (Infinity Engine)<br />
|<br />
|wip<br />
|Adventus<br />
|open-source implementation of Bioware's Infinity Engine, supports games including Baldurs Gate 2 and Planescape Torment.<br />
|-<br />
|Giannas Return<br />
|[http://www.gianas-return.de/ Link]<br />
|Working<br />
|Giannas Team<br />
|Arcade<br />
|-<br />
|Gravity Blocks<br />
|[http://www.gp32x.com/board/index.php?showtopic=47662 Link]<br />
|wip (early in developement)<br />
|Awekening<br />
|Arcade<br />
|-<br />
|Homeworld Port<br />
|[http://www.gp32x.com/board/index.php?showtopic=47565 Link]<br />
|wip<br />
|LinuxHacker<br />
|Simulation<br />
|-<br />
|Human Condition (was TINCS)<br />
|[http://www.gp32x.com/board/index.php?showtopic=46487 Link1][http://www.youtube.com/user/ButtermanHimself Link2]<br />
|wip<br />
|Butterman<br />
|FPP<br />
|-<br />
|Lerp<br />
|[http://grapefruitopia.com/lerp/ Link]<br />
|working build<br />
|benjymous<br />
|2D physics puzzle platformer<br />
|-<br />
|Lord of the Rings Port<br />
|[http://www.gp32x.com/board/index.php?showtopic=46792&hl= Link]<br />
|Unknown<br />
|Daeglin<br />
|RPG<br />
|-<br />
|Mental<br />
|<br />
|Working build, tested on PC<br />
|Colin Jones (xentalion)<br />
|2D Horror Survival Adventure<br />
|-<br />
|Monster!<br />
|[http://christophsdevblog.blogspot.com/ Link]<br />
|wip<br />
|Chris R<br />
|Arcade<br />
|- <br />
|Ms Driller<br />
|<br />
|WIP<br />
|Wally<br />
|Arcade<br />
|-<br />
|NAEV<br />
|[http://code.google.com/p/naev/ Link]<br />
|wip (waiting for pandora to finish and test)<br />
|bobbens<br />
|Action/RPG/Sim<br />
|-<br />
|Nails Adventure<br />
|[http://www.gp32x.com/board/index.php?showtopic=46961 Link]<br />
|wip<br />
|jsmtux/Mr. Gonzo<br />
|<br />
|-<br />
|OpenLiero (Liero)<br />
|<br />
|working build, need to be polished<br />
|Pickle<br />
|Shoot'Em Up<br />
|-<br />
|OpenTyrian<br />
|[http://code.google.com/p/opentyrian/ Link]<br />
|working build<br />
|Cpasjuste<br />
|Shoot'Em Up<br />
|-<br />
|Pandora Panic!<br />
|[http://www.youtube.com/watch?v=y9d6UXhQP6o Link]<br />
|Working build<br />
|PokeParadox / GP32X Community<br />
|Arcade<br />
|-<br />
|Pandora Pool Panic<br />
|[http://www.gp32x.com/board/index.php?showtopic=46996 Link]<br />
|Almost Finished<br />
|Unfathomable Depths<br />
|Arcade<br />
|-<br />
|PanMMO - Pandora MMO Game via Internet<br />
|[http://www.youtube.com/user/enirya Link]<br />
|wip<br />
|Enirya<br />
|RPG<br />
|-<br />
|PanDjoust<br />
|[http://www.gp32x.com/board/index.php?/topic/51192-pandjoust-a-new-simple-platformer/ Link]<br />
|Early Stages<br />
|MarkoeZ<br />
|Platformer<br />
|-<br />
|Powermanga<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|Quake 1<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Quake 2<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Quake 3<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|FPP<br />
|-<br />
|Quake 3<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Reminiscence (flashback)<br />
|[http://cyxdown.free.fr/reminiscence/ Link]<br />
|working build<br />
|Cpasjuste<br />
|Action/Adventure<br />
|-<br />
|Rise of The Triad<br />
|[http://www.gp32x.com/board/index.php?showtopic=47931 Link]<br />
|wip<br />
|arrrgh<br />
|FPS<br />
|-<br />
|Slitherlink<br />
|[http://www.gp32x.com/board/index.php?/topic/50756-slitherlink/ Link]<br />
|WIP<br />
|Mia<br />
|Puzzle<br />
|-<br />
|Super Lumenal<br />
|[http://www.youtube.com/watch?v=sZHi3YT3xuE&feature=channel_page Link]<br />
|wip<br />
|Adventus<br />
|Arcade<br />
|-<br />
|SuperTux 1<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1040 Link]<br />
|working build<br />
|Pickle<br />
|Platform<br />
|-<br />
|SuperTux 2<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1040 Link]<br />
|working build<br />
|Pickle<br />
|Platform<br />
|-<br />
|Tecnoballz<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|Working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|Teeworlds<br />
|[http://www.teeworlds.com/ Link]<br />
|wip<br />
|<br />
|Arcade<br />
|-<br />
|The Mana World<br />
|[http://www.themanaworld.org/ Link]<br />
|Working build<br />
|Cpasjuste<br />
|MMORPG<br />
|-<br />
|uHexen2: Hammer of Thyrion <br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Adventus<br />
|FPP<br />
|-<br />
|Ur-Quan Masters<br />
|[http://www.gp32x.com/board/index.php?showtopic=43625&st=165&p=673047&#entry673047 Link]<br />
|Working build<br />
|<br />
|Space Exploration<br />
|-<br />
|Warioland-inspired game<br />
|[http://www.gp32x.com/board/index.php?/topic/48680-warioland-inspired-game/ Link]<br />
|wip<br />
|foxblock<br />
|Platformer<br />
|-<br />
|We Come In Peace<br />
|[http://www.gp32x.com/board/index.php?showtopic=43655 Link]<br />
|working build<br />
|Otaco<br />
|Strategy<br />
|-<br />
|Where in world is...<br />
|[http://www.openpandora.pl Link]<br />
|Wip<br />
|StreaK<br />
|Casual<br />
|-<br />
|Wizzley Presto and the Mysterious Time Machine<br />
|[http://www.30daygame.com/ Link]<br />
|wip<br />
|Craigix, Zodttd, Ruckage<br />
|Arcade, 30 Day Game Competition<br />
|-<br />
|Wolf4SDL (Wolfenstein 3D)<br />
|<br />
|working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Wandor<br />
|[http://www.gp32x.com/board/index.php?/topic/48680-wandor-working-title/ Link]<br />
|WIP<br />
|foxblock<br />
|Side Scroller<br />
|-<br />
|XSwing Plus<br />
|[http://www.gp32x.com/board/index.php?s=&showtopic=43655&view=findpost&p=733021 Link]<br />
|wip<br />
|Tobse<br />
|Arcade<br />
|-<br />
|ZEQ2Lite<br />
|[http://www.gp32x.com/board/index.php?showtopic=47623&hl= Link]<br />
|Work in progress<br />
|MDave<br />
|Dragonball Z Third Person Fighter/Shooter<br />
|-<br />
|Zdoom <br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Adventus<br />
|FPP<br />
|-<br />
|Zombd<br />
|[http://www.gp32x.com/board/index.php?showtopic=46933 Link]<br />
|Wip<br />
|iprice/Mr Gonzo<br />
|Shoot'Em Up<br />
|}<br />
<br />
== Emulators ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Emulated System<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Caprice32<br />
|Amstrad CPC<br />
|[http://www.gp32x.com/board/index.php?showtopic=48140 Link1] [http://www.caprice32.cybercube.com/ Link2]<br />
|wip<br />
|hdonk<br />
|<br />
|-<br />
|DosBox<br />
|x86 DOS<br />
|<br />
|working build<br />
|Pickle<br />
|<br />
|-<br />
|FinalBurnAdvance<br />
|CPS1/2/3/taito...<br />
|[http://www.youtube.com/watch?v=06hjDLMBaf8 Link]<br />
|<br />
|Squidge<br />
|<br />
|-<br />
|Frotz<br />
|Z-Machine interpreter<br />
|[http://www.cosam.org/computers/pandora/frotz-2.43.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|Fuse<br />
|ZX Spectrum<br />
|[http://www.cosam.org/computers/pandora/fuse-0.9.0.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|GnGeo<br />
|SNK NeoGeo<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|gpSP<br />
|Nintendo GBA<br />
|<br />
|wip<br />
|ZodTTD<br />
|<br />
|-<br />
|Hatari<br />
|Atari ST<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|Jzintv<br />
|Mattel Intellivision<br />
|[http://www.gp32x.com/board/index.php?showtopic=48035 Link]<br />
|<br />
|WizardStan<br />
|<br />
|-<br />
|[[MAME4ALL]]<br />
|Arcade<br />
|[http://www.youtube.com/user/franxism Link]<br />
|<br />
|Franxis<br />
|<br />
|-<br />
|Mupen64plus<br />
|Nintendo 64<br />
|[http://www.gp32x.com/board/index.php?/topic/49358-mupen64plus/ Link]<br />
|working build<br />
|Ari64<br />
|Adventus ported graphics plugin<br />
|-<br />
|NeoPop<br />
|SNK NeoGeo Pocket<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|NullDC<br />
|Sega Dreamcast<br />
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910 Link]<br />
|Wip<br />
|Zezu / drkIIraziel<br />
|<br />
|-<br />
|PandaSNES<br />
|Nintendo SNES<br />
|[http://www.gp32x.com/board/index.php?showtopic=43213 Link]<br />
|wip<br />
|Squidge<br />
|<br />
|-<br />
|Pandora-PSP<br />
|Sony Playstation Portable<br />
|[http://jayfoxrox.bplaced.net/pandora-psp/ Link]<br />
|wip<br />
|[[User:JayFoxRox|JayFoxRox]]<br />
|<br />
|-<br />
|PAtari<br />
|Atari 800<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|PicoDrive<br />
|Sega Genesis/CD/32x<br />
|[http://www.youtube.com/watch?v=QDbLQI91510 Link]<br />
|working build<br />
|Notaz<br />
|Fullspeed emulator<br />
|-<br />
|PSMS<br />
|Sega Master System<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|PSnes<br />
|Nintendo SNES<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|[[PSX4Pandora]]<br />
|Sony PlayStation<br />
|[http://www.zodttd.com Link]<br />
|Not Status, working build<br />
|ZodTTD<br />
|<br />
|-<br />
|ScummVM<br />
|x86 Scumm engine games<br />
|<br />
|Working build<br />
|DJ Willis<br />
|Fullspeed emulator<br />
|-<br />
|SIMH<br />
|old hardware<br />
|[http://www.cosam.org/computers/pandora/simh-3.8.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|Temper<br />
|NEC PC Engine<br />
|[http://exophase.devzero.co.uk/ Link]<br />
|wip<br />
|Exophase<br />
|Fullspeed emulator<br />
|-<br />
|Tempest<br />
|Atari Jaguar<br />
|[http://www.gp32x.com/board/index.php?showtopic=43119 Link]<br />
|<br />
|Firefox<br />
|<br />
|-<br />
|[[UAE4ALL]]<br />
|Amiga<br />
|[http://www.gp32x.com/board/index.php?showtopic=44100 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|XMAME<br />
|Arcade<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|<br />
|Cpasjuste<br />
|<br />
|}<br />
<br />
== Graphic Engines ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|GLES2D<br />
|<br />
|Wip<br />
|Cpasjuste<br />
|OpenGL ES 2D library<br />
|-<br />
|GL-WES-v2.0<br />
|[http://code.google.com/p/gl-wes-v2/ link] <br />
|Working Build<br />
|Adventus<br />
|Opensource OpenGL 2.0 driver built on OpenGL ES 2.0.<br />
|-<br />
|Irrlicht<br />
|[http://irrlicht.sourceforge.net/] [http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=32538&start=45]<br />
|working build<br />
|Hybrid<br />
|3D game engine<br />
|-<br />
|NSS Engine<br />
|[http://www.nosiestastudios.com/wiki/ Link1] [http://www.youtube.com/user/Prompt84 Link2]<br />
|<br />
|No Siesta Studios<br />
|<br />
|-<br />
|OGRE Engine<br />
|[http://www.gp32x.com/board/index.php?showtopic=46706 Link1] [http://www.youtube.com/watch?v=LDtUE5PIhV0 Link2]<br />
|<br />
|<br />
|3D real-time renderer<br />
|-<br />
|Otaco Glost Engine<br />
|[http://www.youtube.com/user/otacogloost Link1], [http://www.gp32x.com/board/index.php?/topic/48393-i-did-stuff/page__p__736650&#entry736650 Link2]<br />
|working<br />
|Otaco<br />
|<br />
|-<br />
|Quad-Ren 2D<br />
|[http://quad-ren.sourceforge.net/index.php Link]<br />
|Working<br />
|Hessiess<br />
|Version 0.5 <br />
|-<br />
|SDL GLES<br />
|[http://github.com/Cpasjuste/sdl-1.2.13_gles/tree Link]<br />
|working<br />
|Cpasjuste<br />
|<br />
|-<br />
|XreaL<br />
|[http://xreal.sourceforge.net/xrealwiki/ Link]<br />
|<br />
|Pickle [?]<br />
|<br />
|-<br />
|Stratagus<br />
|[http://stratagus.sourceforge.net/ Link]<br />
|working build<br />
|Cpasjuste<br />
|RTS Engine<br />
|}<br />
<br />
== Other programs ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|AbiWord - Word Processor<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|Claws Mail<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|Epiphany Web Bowser<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|FireFox - Internet Browser<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GIMP - Image Editor<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GMenu<br />
|[http://www.youtube.com/watch?v=VYzi8gziC7E Link]<br />
|Working build<br />
|Pandora Team<br />
|<br />
|-<br />
|Gnumeric Spreadsheet - Spreadsheet<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GoView<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Image Gallery<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Inside The Box<br />
|[http://www.openpandora.pl Link1] [http://www.youtube.com/watch?v=uLMmJBDEs2E Link2]<br />
|wip<br />
|StreaK<br />
|Pandora e-zine<br />
|-<br />
|IRC Client<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|LeafPad<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Matchbox Shell / GUI<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|MPlayer<br />
|[http://www.gp32x.com/board/index.php?showtopic=41420 Link1] [http://www.youtube.com/watch?v=v9RAPNa-55k Link2]<br />
|Working build<br />
|Squidge<br />
|<br />
|-<br />
|Math-NEON<br />
|[http://code.google.com/p/math-neon/ Link1]<br />
|Wip<br />
|Adventus<br />
|cmath like library optimised for ARM NEON coprocessor.<br />
|-<br />
|Pandaphone<br />
|[http://www.gp32x.com/board/index.php?/topic/48327-pandaphone/ Link]<br />
|<br />
|jb0yx<br />
|A project to incorporate the Open Pandora handheld device with cell phone technology<br />
|-<br />
|Pandora Sync Suite<br />
|[http://www.openpandora.pl Link]<br />
|Working build<br />
|StreaK<br />
|for Windows 9x/NT<br />
|-<br />
|Pangea GUI<br />
|[http://www.gp32x.com/board/index.php?showtopic=45631&hl=pangea Link]<br />
|WIP<br />
|efegea<br />
|Gmenu alternative<br />
|-<br />
|Panorama<br />
|[http://www.gp32x.com/board/index.php?/topic/51076-panorama/ Link]<br />
|WIP<br />
|dflemstr<br />
|Gmenu alternative<br />
|-<br />
|PDM<br />
|[http://github.com/Cpasjuste/pdm/tree Link]<br />
|<br />
|Cpasjuste<br />
|Light desktop manager for Pandora<br />
|-<br />
|PGui<br />
|[http://github.com/Cpasjuste/pgui/tree Link]<br />
|<br />
|Cpasjuste<br />
|Standard emulator fronted for Pandora<br />
|-<br />
|Pidgin - IM (for Angstrom OpenPandora)<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|PMenu<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|<br />
|Cpasjuste<br />
|Minimal Menu for Pandora<br />
|-<br />
|PND Maker (for Windows 9x/NT)<br />
|[http://www.openpandora.pl Link]<br />
|Working build<br />
|StreaK<br />
|<br />
|-<br />
|Qemu<br />
|[http://www.nongnu.org/qemu/status.html Link]<br />
|testing build<br />
|Fabrice Bellard<br />
|open source machine emulator and virtualizer<br />
|-<br />
|Scale<br />
|[http://www.youtube.com/user/Zoxc64 Link]<br />
|wip<br />
|Zoxc64<br />
|Minimal Menu for Pandora<br />
|-<br />
|Simple Dev Studio for Pandora<br />
|[http://www.openpandora.pl Link]<br />
|Wip<br />
|StreaK<br />
|for Windows 9x/NT<br />
|-<br />
|[[TINXL]]<br />
|[[TINXL]]<br />
|<br />
|<br />
|Application stack for multiplayer internet games<br />
|-<br />
|[[TS2A]]<br />
|[[TS2A]]<br />
|Documentation only<br />
||[[User:JayFoxRox|JayFoxRox]]<br />
|Teamspeak 2 Alternative Client / Server, Needs developer<br />
|-<br />
|XMMS<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|ZiB Emulator Frontend<br />
|[http://www.gp32x.com/board/index.php?showtopic=47203 Link1] [http://www.youtube.com/watch?v=UJvON8lCM3M Link2]<br />
|<br />
|Aimless_E<br />
|<br />
|}<br />
<br />
== Demos / Technical Demos for OpenPandora ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|OpenGL Cell Shading<br />
|[http://www.youtube.com/watch?v=cpAj0jHglGw Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|OpenGL Demo with MP3 Playback<br />
|[http://www.youtube.com/watch?v=hkx18kruRJs Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|OpenGL Skull Demo<br />
|[http://www.youtube.com/watch?v=qG7EDaZpyOo Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|WaveDemo<br />
|[http://www.youtube.com/watch?v=4wgEHFCq9Lo Link]<br />
|Working<br />
|Otaco<br />
|<br />
|}<br />
<br />
[[Category:Development]]<br />
[[Category:Software]]</div>Glennhttps://pandorawiki.org/index.php?title=Combining_OpenGL_ES_1.1_and_SDL_to_create_a_window_on_the_Pandora&diff=2011Combining OpenGL ES 1.1 and SDL to create a window on the Pandora2010-01-10T20:53:20Z<p>Glenn: catchg</p>
<hr />
<div>There is a special SDL source code for pandora with OpenGL ES capability <br />
available here : http://github.com/Cpasjuste<br />
<br />
The screen initialisation is now easy as this : SDL_SetVideoMode(800, 480, 16, SDL_OPENGLES)<br />
<br />
An SDL/GLES exemple is also available on the git repository.<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=User_manual&diff=2004User manual2010-01-10T20:45:45Z<p>Glenn: +cat</p>
<hr />
<div><div style="border-top:1px solid gray; border-bottom:1px solid gray; padding-top:5px; padding-bottom:5px; margin-bottom:20px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;''This page is an unofficial community project, and OpenPandora Ltd. is not responsible for its content.''</div><br />
<br />
[[Image:PandoraFront.jpg|Right|thumb|360px|Pandora FTW!]]<br />
So your Pandora just arrived after being in the post for two months. Jolly good! But now that it's actually here, what on earth do you do with it? '''Don't panic!''' Let's take a look at what's included in the box(so you don't miss anything!) and then hop on over to setting it up for that extended Ms. Pacman marathon I know you've been waiting for!<br />
<br />
Also, don't forget to hit up [http://www.gp32x.com/board/index.php?/forum/61-pandora/ GP32X] for questions/info/apps/fun/discussion!<br />
<br />
<br />
== Safety Information ==<br />
Warning: Choking Hazard, do not let children under the age of 3 come close to your Pandora console.<br />
The Pandora Contains small parts that can be eaten by those children.<br />
<br />
The battery of Pandora must be charged by the charger included with the Pandora(see package contents)<br />
and we at OpenPandora Ltd. cannot be responsible for people using third party chargers. Please be aware that some third party chargers compatible with the Pandora have a fake CE logo and are highly dangerous (they will burst into flames).<br />
<br />
Keep the Pandora in normal temperatures under 140F/60C (Recommended temperatures are in the range between -10C and 40C){{Citation needed}}. The battery is standard Lithium Polymer battery. Do not keep near fire or water. Do not disassemble, destroy or damage the battery, or it may explode! Do not short circuit external contacts! Dispose of it properly, please. <br />
<br />
All third party modifications and hardware/software can damage your Pandora, OpenPandora Ltd cannot be responsible for damage caused by this. Trusted software can be recognised by a OP-member in the Pandora Appstore. See the “OP-Team Trusted” image in the app store to see if the software application can be trusted{{Citation needed}}.<br />
<br />
The Pandora has a 4.3-inch Touchscreen. You can touch the screen to trigger an action. Although this is a touch screen, you cannot punch it. Always touch the screen gently – this will be more then enough to trigger the action you want.<br />
<br />
The Pandora has an protective design, making it hard to break. Of course, you should never drop your Pandora, wash it, or try anything that can harm your Pandora. This will void your warranty.<br />
<br />
== Warranty Information ==<br />
By law there is a one year warranty, and the device will be replaced/repaired if it is faulty. LCDs with noticeable dead pixels will also be replaced (Note: Pixels are small squares aligned in a grid to make up the image on your screen. A "Dead Pixel" is one that doesn't work anymore and remains black or any other static color).<br />
<br />
== Box Contents ==<br />
When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you may or may not be surprised to find a:<br />
*Pandora console<br />
*Stylus (located in stylus slot on the side of the Pandora)<br />
*Battery<br />
*DC Wall Charger<br />
*TV-Out Cable (ONLY if you ordered it separately)<br />
*Carrying Case (ONLY if you ordered it separately)<br />
*Extra Battery (ONLY if you ordered it separately)<br />
After you take those things out, you may find a sliver of Hope left over. It's best to keep it, as you never know when you could use some Hope.<br />
<br />
== Specifications ==<br />
==== Highlights ====<br />
{{citation needed}}<br />
* ARM® Cortex™-A8 600Mhz+ CPU running Linux*<br />
* 430-MHz TMS320C64x+™ DSP Core<br />
* PowerVR SGX OpenGL 2.0 ES compliant 3D hardware<br />
* 800x480 4.3" 16.7 million colours touchscreen LCD<br />
* Wifi 802.11b/g, Bluetooth & High Speed USB 2.0 Host<br />
* Dual SDHC card slots & SVideo TV output<br />
* Dual Analogue and Digital gaming controls<br />
* 43 button QWERTY and numeric keypad<br />
* Around 10+ Hours battery life**<br />
<br />
:<small><nowiki>*</nowiki>The 600Mhz+ can be higher or lower. This can be controlled by software designed for the device.</small><br />
:<small><nowiki>**</nowiki>Is affected by use. (example turn bluetooth on or off during play time)</small><br />
<br />
==== Advanced Specifications ====<br />
* Texas Instruments OMAP3530 processor at 600MHz (officially)<br />
* 256MB DDR-333 SDRAM<br />
* 512MB NAND FLASH memory<br />
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)<br />
* ARM® Cortex™-A8 superscalar microprocessor core<br />
* PowerVR SGX530 (110MHz officially) OpenGL ES 2.0 compliant 3D hardware<br />
* integrated Wifi 802.11b/g (up to 18dBm output)<br />
* integrated Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)<br />
* 800x480 resolution LTPS LCD with resistive touch screen, 4.3" widescreen, 16.7 million colors (300 cd/m2 brightness, 450:1 contrast ratio)<br />
* Dual analog controllers<br />
* Full gamepad controls plus shoulder buttons<br />
* Dual SDHC card slots (up to 64GB of storage currently)<br />
* headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)<br />
* TV output (composite and S-Video)<br />
* Internal microphone plus ability to connect external microphone through headset<br />
* Stereo line level inputs and outputs<br />
* 43 button QWERTY and numeric keypad<br />
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device<br />
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)<br />
* up to two externally accessible UARTs and/or four PWM signals for hardware hacking, robot control, debugging, etc.<br />
* un-brickable design with integrated boot loader for safe code experimentation<br />
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go<br />
* Runs on the Linux operating system (2.6.x)<br />
* Dimensions: 140x83.4x27.5mm<br />
* Weight: 335g (with 4200mAh battery)<br />
<br />
==== Features ====<br />
The Pandora is a mixture between a PC and a gaming console (similar to classic computers such as the Amiga). That's why it has gaming controls (Buttons, DPad and analogue nubs). It is fast enough to emulate many other systems, run a full desktop, access the internet via Firefox and play games such as Quake3. However, it is not as big as a netbook. Believe it or not, it will fit in your pocket. It's a bit bigger than the Nintendo DS. (See Applications section of this manual to see what applications your Pandora will come with.)<br />
Remember that your Pandora console will get better with every application installed!<br />
<br />
== First Time Use ==<br />
Now that you've opened the box, let's set this thing up! Place the battery inside the battery compartment on the back of the Pandora, making sure the contacts touch(the little silvery metal bits, it's easy). Snap on the battery cover and you're all set!<br />
==== Charging ====<br />
Charge your Pandora 8 hours before disconnecting it from the wall charger. This will improve the lifetime of your battery. To charge the Pandora, insert the power cable end in the Pandora and the other end into your wall socket.<br />
<br />
The battery comes pre-charged at 40%, and that level might have decreased during shipping. To be on the safe side, we recommend that you charge the Pandora before you use it. Simply plug in your wall charger into an outlet, or optionally use a mini-USB cable connected to a computer or wall adapter. For extreme silliness, plug your Pandora into an ''already charged Pandora,'' and charge it from that! But not really.<br />
<br />
==== First Boot ====<br />
Once your Pandora is ready, turn it on. The OS will take some time to boot up for the first time (about 10 minutes, this is only for the first boot, and is normal). After it has booted, a series of settings dialogs will pop up in the shape of a "Boot Wizard" allowing you to alter your Pandora's settings to your liking.<br />
<br />
There are a total of 3 parts to the Boot Wizard guide:<br />
===== System configuration =====<br />
The first thing you will have to do is to calibrate the Pandora's touch screen. Only do this if the screen isn't calibrated already.<br />
You will have the option for touchscreen calibration the first time you boot up your Pandora console.<br />
<br />
Note: "Calibrating the touch screen" is a term used to describe the process of matching coordinates given by the touch layer with the underlying screen. A badly calibrated screen will register your push elsewhere on the screen, perhaps half a centimeter to one side. As there are sometimes slight variations in the production of the touch layer, you the user can improve the accuracy by matching the two layers manually.<br />
<br />
===== User setup =====<br />
After calibrating your screen, you will have to enter your full name. This is what you will see in any user selection dialogs or when the system needs to address you, so enter whatever you are most comfortable with. Then follows your username. It is recommended to choose an all-lowercase, one-word username here, since you will have to enter this name every time you log in. Once you've entered your username, a password input dialog appears. You will have to enter the password you want to use twice here. If you don't want to have a password for your device, simply leave both fields empty. If, however, you decide to enter a password, something hard to guess and between 8 and 16 characters long is preferred.<br />
<br />
===== Network and security settings =====<br />
You will now have to enter a name for your Pandora. This will be the Pandora's host name, so you have two options in this situation:<br />
<br />
# If you don't have a domain you want to connect to, simply enter any name here. It should not contain any spaces.<br />
# If you ''do'' have a domain you want to connect to, enter a name in the form of "pandoraname.domainname.tld". Note that you may never have a use for this.<br />
<br />
Then, you'll have to choose whether you want to automatically log in on your Pandora when it boots, or if you should be given the opportunity to log in as a different user, or enter your password. It is recommended to disable auto login if you want to protect your user data, but if you're often in a hurry, then you can enable auto login here.<br />
<br />
The final thing you will have to choose, is whether you want to use the full desktop Xfce environment or the gaming-oriented PMenu environment as your default environment in the Pandora. It is recommended to choose Xfce here if you want to gain access to the Pandora's full potential. This option can be changed later at any point.<br />
<br />
==== Calibrating The Touchscreen ====<br />
The touchscreen in your new Pandora device isn't psychic! You have to tell it what to do, and in order to do that effectively, you need to calibrate it. Simply navigate to settings→screen→calibration wizard{{Verify credibility}} and follow the onscreen instructions. You may have to recalibrate the screen from time to time as well.<br />
<br />
During the first boot wizard, you will be offered the option to calibrate the touchscreen. By default it may well work okay, but the option is there. If calibration is far off, use the keyboard to select the calibration option.<br />
<br />
== Basic Use ==<br />
<br />
===Pmenu===<br />
<br />
===Desktop style environment===<br />
<br />
====On the Desktop====<br />
<br />
The desktop will contain icons for numerous locations (such as each mounted SD card), as well as any auto-discovered pnd-applications located on SD cards or internal NAND.<br />
<br />
====In the menu====<br />
On the bottom left you have your applications menu, similar to the Windows start menu. Clicking it brings up a list of all installed applications and pnd-applications in the appropriate location on your SD cards.<br />
<br />
====Miscellaneous====<br />
To the right may be some icons, these serve as shortcuts to commonly used applications. Next to that you have your taskbar which, as you might have guessed, lists all running applications in your current workspace. To the right of the taskbar you have your workspaces, think of these as multiple desktops. By default you have two to switch between. Applications running in one workspace will not be visible in the other, so you can effectively hide your Ms. Pacman game from your boss at work, because there's no way you're not going to go for the gold, even at work! Finally there are a few more icons that deal with TV-Out, network connectivity, etc. and some running applications may place an icon there as well. And to the right of THOSE, you have your time. Because time flies when you're using your Pandora! Badum tsh. And to the right of that, you have a little icon which, when clicked, displays all running applications.<br />
<br />
Finally, I'd just like to reiterate this--EVERYTHING is customizable! We'll get to that section later, but for now, let's just check out the applications on your Pandora.<br />
<br />
===Buttons===<br />
<br />
====Xfce menu====<br />
<br />
The Pandora button will bring up the applications menu, letting you quickly enter a search to locate an application to run or perform operations against running applications.<br />
<br />
===Power Modes===<br />
<br />
Without switching the device entirely off, it may be placed into low power mode or regular power mode; simply pressing the power button will toggle modes.<br />
<br />
Consider low power mode to be akin to turning off a PDA or cellphone -- the screen is off, the CPU is clocked down and so on, but the device is still silently on, allowing for alarms to go off or it to be turned on again instantly. Regular power mode is for normal usage.<br />
<br />
Low power mode is probably going to be used as the normal "off" for most people, with true off (device powered down entirely, unable to respond to alarms or wake up quickly) available to conserve battery power. Turning the Pandora off completely is the best option if you don't plan on using it for few weeks or longer. <br />
<br />
Closing the lid will turn off the display but otherwise leave the device operating - handy for audio playing; turning off the display lowers power use.<br />
<br />
The actual behaviour of buttons and events can be customized.<br />
<br />
== Basic Linux user guide ==<br />
New to the wonderful world of Linux? No problem! You don't need mad terminal skills to open a web browser, but it can be nice to know what you're doing once in a while.<br />
==== The structure of the file system ====<br />
If you're used to the file system of e.g. MS Windows, you will find that a Linux file system is rather different from what you're used to. In this section, we will go through everything you have to know in order to feel comfortable with using the Pandora's file system.<br />
===== Basic philosophy =====<br />
In Windows, you have multiple file system roots, called "drives", that are labeled with different letters, like "C:" or "D:". In Linux, there aren't multiple root directories, but rather just one root directory, called "/". All other directories are inside of this directory, including other drives.<br />
<br />
===== Common directories =====<br />
Inside of the root directory ("/") are quite a lot of other directories. Here are the most important ones:<br />
* "/home" - This is where all of the files that are owned by all users are stored. Users do not generally have write-access to anything outside of this directory.<br />
* "/home/username" - Here are the personal files of user "username". In this directory, you will find a directory called "Documents", "Pictures", "Desktop" etc. that correspond to that users personal directories. This directory is also called "username"'s home directory, and can be abbreviated with "~/" (if you're currently logged in as username) or "~username/".<br />
* "/boot" - This is the directory where the Linux kernel is stored, and other files that are needed at boot time can be accessed. Do not touch this directory (You can't even do it if you wanted to)!<br />
* "/bin", "/lib" - System binaries and libraries are stored here. Most of the terminal commands mentioned below can be found inside of "/bin". You should generally never have to touch this directory, either.<br />
* "/usr" - Here is where you'll find programs and files installed by the user. Core applications such as the web browser, media player, and other applications that are available the first time you start your Pandora are stored here. If you decide to install anything via the "ipkg" command (covered later), this is where the files needed by those installations will end up.<br />
* "/etc" - System-wide configuration. Should only be touched by power-users.<br />
* "/media/*" - If you connect USB drives, SD cards or other external media, you will find that the contents of that media have been placed here.<br />
<br />
Don't worry if this doesn't make any sense; It was thought up by bearded engineers back in the seventies. They liked the idea that everything would be in a predictable place, but this is no longer completely the case.<br />
<br />
==== The File Manager ====<br />
==== Killing Applications ====<br />
==== Basic Terminal Commands ====<br />
Note: Linux is case sensitive. This applies to filenames and directories too. "/home/me/stuff" is a different folder than "/home/me/STUFF", you can actually have both. You can have "/home/me/Stuff" too if you like, and all three are separately recognised directories.<br />
<br />
=====Navigation=====<br />
In the terminal, you are always in some folder. Think of it like being in a file manager: you can see the contents of the directory you're in, you can do things with those files, or you may decide to go to some other folder and continue your work there.<br />
<br />
There are a few essential commands that are used to navigate around your system via the terminal:<br />
<br />
* "pwd" - Print the current working directory (will print e.g. "/home/user")<br />
* "ls" - List directory contents (similar to "Dir" in Dos, and the Linux command "dir" will actually emulate the DOS command if you want to!)<br />
* "cd <directory name>" - Change to a different directory, eg. "cd music" or "cd /home/me/music"<br />
* "cd .." - Go up one directory level (similar to "cd.." in Dos)<br />
* "cd" - Go back to your home directory (similar to My Documents in Windows)<br />
* "cd -" - Go back to the previous directory you were in (handy if you forget)<br />
<br />
=====Controlling Running Apps=====<br />
* "top" - View running processes (like the Task Manager in Windows) press "q" to quit<br />
* "killall [program name] - Stops running process (use with care)<br />
<br />
=====File Manipulation=====<br />
* "rm <filename>" - Remove a file, eg. "rm somefile.txt" or "rm /home/me/randomfiles/somefile.txt"<br />
* "rmdir <directory>" - Will remove a directory, but **only** if it is empty!<br />
* "rm -r <directory>" - Will remove a directory and its contents ("-r" means recursive)<br />
* "rm -rf <directory>" - Will remove a directory, all of its contents, without asking you first. Use with extreme care. ("-f" means force)<br />
* "mv <original filename> <new filename>" - Moves a file to a new place, also used for renaming, eg. "mv somefile.txt somefile_backup.txt" will rename it, but "mv somefile.txt /home/me/backup/somefile.txt" will move it. This will also work for directories.<br />
* "cp <file to copy> <new filename>" - Copy a file, eg. "cp twoweeks.txt twomonths.txt" copies into current directory, while "cp twomonths.txt /home/me/ihaveadream/twoweeks.txt" copies to another directory.<br />
* "cp -r <directory to copy> <new directory name>" - Copy a directory and all of its contents to another location.<br />
* "touch <new file name>" - Makes a new (empty) file<br />
* "mkdir <new directory name>" - Makes a directory<br />
<br />
=====Misc.=====<br />
* "cat <filename>" - Prints the contents of a file, eg. "cat hellolo.txt"<br />
* "clear" - Clears screen, terminal input begins at the top again<br />
* "date" - Your friend, the terminal will tell you the date<br />
* "cal [month] [year]" - Makes a pretty calendar, eg. "cal 12 2009" or "cal * 2010" or "cal 1 2010 > fingers_crossed.txt" sends output to file<br />
* "history" - Gives a list of the recent commands you have run. Running !number (e.g. !15) will rerun that numbered command in the history list<br />
<br />
History Search: Press CTRL-R. As you type, BASH will try and find the command in your recent history that most closely matches what you are typing. To get back to the prompt, press CTRL-C.<br />
<br />
Autocompletion: Press TAB. The terminal (also called the shell) will attempt to intelligently figure out what you're trying to type. It needs something to work with however, so try pressing TAB half way through a command or location.<br />
<br />
eg. "cd /home/me/pandora_suc" *TAB* will complete it as "cd /home/me/pandora_success" or with a filename "cat /home/me/letters/i_want_the_pandora_to_fa" *TAB* will turn into "cat /home/me/letters/i_want_the_pandora_to_fall_into_my_hands"<br />
<br />
Directory aliases: There are some special directory names you can use to refer to a directory that would be too long to type otherwise, or that you simply don't know the name of.<br />
* "~" - Refers to your home directory e.g. "/home/user".<br />
* "~seconduser" - Refers to someone else's home directory.<br />
* "." - Refers to the current directory, or the "same directory" in a path. What this means, is that if you type "cd .", nothing will happen since you already are in ".", and if you type "cd somedir/././././././.", you will simply go to "somedir", since the "."-directories that come after it are the "same directory" as the one before them.<br />
* ".." - Refers to the directory in which the current directory is, or the "parent directory" in a path. If you type "cd .." you will come to the parent directory of your current directory, and if you type "cd s1/s2/s3/../../..", nothing will happen, since the path you specified cancels itself out.<br />
<br />
== Applications ==<br />
<br />
Many applications will come preinstalled into the internal NAND; these will be regular Linux applications (not packaged into pnd files, since they do not need to be redistributed to anyone.)<br />
<br />
Additional applications may be found as pnd-files (see below, a packaged up single file representing an entire application) or as regular Linux files (an application likely being made up of many files and possibly needing installation.)<br />
<br />
==== What Is Included? ====<br />
* Ångström Linux: Lightweight beautiful Linux-based operating system for the Pandora.<br />
* Xfce: A full featured window manager for Linux.<br />
* Midori: A full features web browser, designed to be lighter and faster than a full desktop style browser.<br />
* OpenOffice: Full desktop document managing. Edit, create and manage your documents on the go. (really??)<br />
{{Volume needed}}<br />
<br />
==== Where Can I Get More Apps? ====<br />
There are many ways to get more applications onto your Pandora.<br />
<br />
*The easiest way is to browse the [http://doesnotexistyet.com Pandora App Store], where you can download a selection of free or commercial applications. To download, navigate to an app, pay for it if you must, and hit the 'download' button. Select where you want to save it, and you're done!<br />
<br />
*There is the good ol' [http://dl.openhandhelds.org/cgi-bin/pandora.cgi Pandora File Archive].<br />
<br />
*There are nice repositories, such as the [http://www.angstrom-distribution.org/repo Angstrom ARM Repository], or...<br />
<br />
*The Pandora includes the package manager [http://en.wikipedia.org/wiki/Ipkg ipkg].<br />
<br />
*Also, people may upload their apps to weird crevices in the net, so be on the lookout! (or use a search engine)<br />
<br />
== Introduction To .PNDs ==<br />
==== What Are .PNDs? ====<br />
<br />
A .pnd ("pandora") file is an application (game, word processor, emulator, whatever.) More accurately, it is a full application bundled up into a single file; think of it like a zip, with a relatively well defined internal structure.<br />
<br />
The pnd-file system was designed so you could use an application without the hassle of installation or uninstallation, or even having to organize it yourself if you don't want to. You just download or obtain the pnd-file, and use it. <br />
<br />
If you remember classic computers such as the Amiga - where you inserted a disk and then launched the applications read by Workbench (the Amiga's operating system) - then this is similar: when you insert an SD card into one of the two slots, the (Linux based) Pandora OS will scan it for your PND program files. Any program it finds will either turn up on the desktop or the application menu (just like in Windows).<br />
<br />
More details can be found in the "libpnd hub" part of the wiki, but that is more oriented to techies and developers.<br />
<br />
==== How do I run a PND-application? ====<br />
<br />
Put your pnd-files in your SD (see below for some suggestions where.)<br />
<br />
A pnd-file is usually invoked in one of the following ways<br />
<br />
* browse to the file using the directory browser, and click to run it. (.pnd files are file-associated to another program, pnd_run which knows how to run them.) This lets you organize pnd-files in directories of your choice on the device NAND or SD.<br />
<br />
* in PMenu, the applications will be shown by name; you can just select and run them from the menu<br />
<br />
* for pnd-files placed into /pandora/menu on SD, the application will be shown in the Start menu on the device; use your stylus or buttons to invoke it<br />
<br />
* for pnd-files placed into /pandora/desktop or /pandora/apps on SD, they will show up automatically on your desktop; invoke them with the stylus, your finger, or controls as you see fit<br />
<br />
==== Where Do .PNDs Go? ====<br />
<br />
Put .pnd-files into specific directories if you want them to show up in the Start menu or on your Pandora desktop, or in Pmenu. <br />
<br />
You can put them anywhere you like in internal NAND or SD, if you wish to organize them yourself and launch them with taps.<br />
<br />
/pandora/desktop -> pnd files show up on the desktop<br />
<br />
/pandora/menu -> show up in the Applications menu (by the developers suggested categories.)<br />
<br />
/pandora/apps -> show up in the desktop, and in Pmenu<br />
<br />
These locations are not written in stone. The "libpnd" config files are in /etc/pandora/conf in the NAND. Generally you will never need to alter these files, but you certainly can if you wish. In theory, obliterating the files will still leave the system working, and they are easily restored. One file, /etc/pandora/conf/desktop defines the "search paths" to look for .pnd files, and where to put ".desktop" files when they are found. The searchpaths says where to find them (such as /pandora/desktop), and where to put the application link - /usr/share/applications is where the menu items are pulled from. IF you wish to put pnd files somewhere not in the searchpath, just add the directory to the search-path and you're good to go.<br />
<br />
==== Where does my data go? How do I make files visible to the applications? ====<br />
<br />
An application normally will see what is contained within the pnd-file, or your personal data created with the tool; it can of course look anywhere on the SD or device internal memory. For example a Quake port might expect to see extra level files in /quake, or give you a way of selecting a path to put files in.. or it might just expect it to be in your personal data folders, or in the pnd-file itself. Its up to the application, with suggestions in the pnd-guidelines for developers.<br />
<br />
The first time a pnd-application is run, an "app data" directory is created for it; anything that app data folder contains will be visible to the application as if it was in the pnd-file (and in fact, this lets you override files in the pnd-file without modifying the .pnd itself, which could be handy.) If your app creates a file "foo", it'll show up in /pandora/appdata/appname-id as "foo". The actual appdata folder name depends on the name used by the developer, but should generally look like application-name and some funny number afterwards. It should be easy to spot.<br />
<br />
ex: Quake 1 will probably put score or save data in /pandora/appdata/quake1-123/ or somesuch.<br />
<br />
It will always be helpful to read the description or readme file included.<br />
<br />
===== Q: How do I make ROMs available to an emulator? =====<br />
<br />
For something like ROMs, hopefully a developer consensus will lead either to a canonical location, or a convention of having a directory picker or browser present, so that ROMs can be stored in SD locations of your choice; doesn't strike me as something that should be in a pnd-file, or to be pretended to be in a pnd-file with appdata tricks.<br />
<br />
===== Q: How do I make pak-files available to Quake? =====<br />
<br />
For some add-ons or data needed for a game, the developer may require it to be 'in the main application path'; as mentioned above, just drop it into the appdata folder and the app will just see it.<br />
<br />
==== How Do I Make .PNDs? ====<br />
==== More Info About .PNDs ====<br />
Visit [[libpnd_hub]] for more information!<br />
== Configuration ==<br />
==== Updating The Firmware ====<br />
<br />
Given a working firmware, you might wish to patch it with official Open Pandora patches; you might also wish to just grab an application from the Angstrom repository, say. <br />
<br />
In both of these cases, an ipk file will be made available. (In the future, an automated system may offer to patch up your device or auto-download patches. TBD.)<br />
<br />
An ipk file is a compressed installable package.<br />
<br />
It should be easily used, but from the Terminal if you wish to manually apply an ipk to patch the firmware, install or update an Angstrom application, it is simple: '''opkg install foo.ipk'''<br />
<br />
==== Replacing the Firmware ====<br />
<br />
Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware.<br />
<br />
==== Booting a Firmware from SD ====<br />
<br />
The hardware is capable of booting entirely from SD; if the device is bricked or otherwise has a blank NAND, this could be an option. furthermore you're able to try out alternative operating systems without needing to reinstall your primary operating system.<br />
<br />
Steps include:<br />
<br />
* Preparing the SD card(s)<br />
* Setting up the firmware on the SD card<br />
<br />
=====Preparing the SD card=====<br />
<br />
There are two main approaches:<br />
<br />
* Setting up the firmware on on SD card (meaning you need two partitions - a boot partition, and a firmware partition), and<br />
* Setting things up across two SD cards - meaning you boot from one SD card, and have the firmware on the other.<br />
<br />
Operating from one SD card provides you the option of still being able to use the other; operating across two cards provides you he option to have a regular boot-SD, and flip between multiple other SDs for the actual firmware, should you wish to cycle between many operating systems (say.)<br />
<br />
The boot partition generally must be FAT32, and then the kernel, MLO and other files need to be unpacked upon it.<br />
<br />
The firmware partition must be either ext2fs or ext3fs; under Linux, such a partition can be easily created:<br />
<br />
'''mkfs.ext2 -L LABELNAME /dev/mmcblk0p2'''<br />
- assuming LABELNAME for the partition<br />
- assuming /dev/mmcblk0p2 for your SD device; you'd better check this carefully ;)<br />
<br />
==== Setting Up WiFi ====<br />
==== Setting Up Blutooth ====<br />
==== Adjusting Brightness/Contrast ====<br />
==== Changing Your Theme ====<br />
== Oops! I Borked My Pandora! ==<br />
Fear not, young netizen! Your Pandora was designed to be unbrickable, so unless you used the ancient art of alchemy to physically turn your Pandora into a brick (or you just broke the hardware inside), you should be okay!<br />
==== Restore The Original Firmware ====<br />
==== Boot From SD or USB ====<br />
== Pandora FAQ ==<br />
Silly goose, go to the [[FAQ]] page for more detailed information.<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=USB_compatibility_list&diff=2003USB compatibility list2010-01-10T20:45:11Z<p>Glenn: +cat</p>
<hr />
<div>==Devices==<br />
===HSDPA (3G) Modems===<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Device<br />
! Driver<br />
! Connector<br />
! Supported standard<br />
! Current draw<br />
! Suggested connection to Pandora<br />
! Tested in Linux<br />
! Tested on Pandora<br />
! Additional comments<br />
|-<br />
| Huawei E160<br />
| Not required<br />
| standard-A<br />
| USB 2.0<br />
| 250mA<br />
| standard-A port<br />
| Yes<br />
| Yes<br />
| <br />
|-<br />
| Huawei E220<br />
| Not required<br />
| standard-A<br />
| USB 1.1<br />
| 250mA<br />
| standard-A port via High Speed hub<br />
| Yes<br />
| Yes<br />
|<br />
|}<br />
<br />
===USB to Ethernet adapters===<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Device<br />
! Driver<br />
! Connector<br />
! Supported standard<br />
! Current draw<br />
! Suggested connection to Pandora<br />
! Tested in Linux<br />
! Tested on Pandora<br />
! Additional comments<br />
|-<br />
| Apple USB Ethernet Adapter MB442Z/A<br />
| Not required<br />
| standard-A<br />
| USB 2.0<br />
| <br />
| standard-A port<br />
| Yes<br />
| No<br />
| <br />
|}<br />
<br />
==Connectors, adapters, and hubs==<br />
This section is intended as a general guide. Items in this section are standard USB accessories, so drivers are not required. Compatibility with Pandora is assumed. Please note that any external product links are provided for reference only, and are not an endorsement.<br />
===OTG Adapters===<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Device<br />
! Tested<br />
! Additional comments<br />
|-<br />
| Generic adapter<br />
| No<br />
| [[http://shop.ebay.com/?_from=R40&_trksid=p3907.m38.l1313&_nkw=usb+otg+host+cable&_sacat=See-All-Categories Find on eBay]] [[http://www.amazon.co.uk/s/ref=nb_ss_ce?url=search-alias%3Delectronics&field-keywords=OTG+Cable+Adapter&x=3&y=23 Find on Amazon]]<br />
|-<br />
| Nokia USB OTG adapter<br />
| Yes<br />
| Link Required<br />
|}<br />
<br />
===Compact USB Hubs===<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Device<br />
! Tested<br />
! Additional comments<br />
|-<br />
| Griffin SmartShare USB<br />
| No<br />
| [[http://www.griffintechnology.com/products/smartshare-usb Griffin website]]<br />
|}<br />
<br />
==More Information==<br />
For more information on the Pandora's two USB ports and the possible connections that can be made with them, see [[USB_reference|the USB reference page]].<br />
<br />
[[Category:Hardware]]</div>Glennhttps://pandorawiki.org/index.php?title=PXML_specification&diff=2001PXML specification2010-01-10T20:44:01Z<p>Glenn: +cat</p>
<hr />
<div>[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,1,0,0,45,35 Download this page as PDF]<br />
<br />
'''Attention:''' at the present time, the PXML file format isn't set in stone, and is therefore subject to change. There is no guarantee that the format or the schema are bug-free or will be changed at any time. Please wait until this standard is finished before writing a PXML file.<br />
<br />
This is the human-readable specification for the PXML file format. The PXML file format is used in your applications for the OpenPandora® that you package in ".pnd"-files or distribute otherwise, to make it possible for menus and launchers to use your applications and their properties.<br />
<br />
A PXML file should be appended to your ".pnd"-file, using the tools provided for that purpose, or put in a directory that you want to serve as a redistributable package, to make it possible for launchers and menus to find it. It should have the name "PXML.xml" not case sensitive, and there should only be one such file. The contents of the PXML file should also comply to this specification without exception, to guarantee that everyone will be able to read it.<br />
<br />
== XML compatibility ==<br />
The PXML format is XML-based and fully XML-compliant, which means that it can be read and written by any XML reader or writer. Included with this specification should also be a ".xsd"-file, which is used by XML tools to validate PXML files. A ".xsd"-file is also known as a XML schema, and can be called the "computer-readable" version of this document. It is very good practice to validate your PXML-files with that schema before publishing them.<br />
<br />
To write a PXML file, you also need to know the basics of writing a XML file. It boils down to the following:<br />
<br />
# If an element contains text or other elements, it needs a start-tag and an end-tag. This looks like (1)<br />
# If an element does not contain other elements or text, but only attributes, it looks like (2)<br />
<source lang="xml"><br />
<exampleelement someattribute="something">something inside it</exampleelement> <!-- (1) --><br />
<exampleelement2 someattribute="something" /> <!-- (2) --><br />
</source><br />
<br />
== Format ==<br />
<br />
The PXML-file is split up into multiple so-called elements, each of which specify one property of the ".pnd"-package. All of these elements are surrounded with a "<PXML>"-tag, which tells the readers of the file that the data within that tag belongs to a PXML file. The tag and elements should be defined as follows:<br />
=== The PXML-tag ===<br />
==== Description ====<br />
The PXML-tag serves as the container for all PXML elements. It is the first thing that should occur in your PXML file. An example "<PXML>"-tag would look like this:<br />
<br />
<source lang="xml"><br />
<PXML xmlns="http://openpandora.org/namespaces/PXML" id="uniqueID"><br />
<!--All of the PXML elements should be put here--><br />
</PXML><br />
</source><br />
<br />
As you can see, the PXML tag accepts a few attributes, namely the "id" and "xmlns" attributes.<br />
<br />
* The "xmlns" attribute is required by the XML standard, and guarantees that this file will be identified as a PXML file. You must include the xmlns attribute, exactly as shown, in your PXML file, with the URL as specified. Only then can it be guaranteed that the file will be read at all by launchers and menu apps.<br />
* The "id" attribute specifies an identifier for your PND package, and should be something globally unique so that no two PND packages have the same id. This can be achieved by appending some random number to your application name, and to use that as your id; or to simply generate a completely random, very long id. If this id already is used in another PND file, those two PND files will conflict with each other, and unforseeable errors will occur. Please put effort into generating an unique id for your PXML-file.<br />
<br />
=== The title element ===<br />
==== Description ====<br />
<br />
The title element specifies the text that is shown to the users of your PND file as the application title. This element can be specified multiple times in multiple languages the language is indicated by the lang attribute.<br />
<br />
At least one "title"-element is required, in the "en_US" American English language.<br />
<br />
==== Example ====<br />
<source lang="xml"><br />
<title lang="en_US">Your application name</title><br />
<title lang="de_DE">Deinen Programmnamen</title><br />
</source><br />
=== The description element ===<br />
==== Description ====<br />
<br />
The description element specifies the text that is shown to the users of your PND file as the application description. This element can be specified multiple times in multiple languages the language is indicated by the lang attribute.<br />
<br />
At least one "description"-element is required, in the "en_US" American English language.<br />
==== Example ====<br />
<source lang="xml"><br />
<description lang="en_US">Your long description of this application, describing it's purpose and highlighting it's features.</description><br />
<description lang="de_DE">Deine etwas längere Programmbeschreibung, die den Sinn des Programmes und den wichtigsten Features beschreiben sollte.</description><br />
</source><br />
<br />
=== The exec element ===<br />
==== Description ====<br />
<br />
The exec element should specify all the information needed to execute your application.<br />
An exec element must be included in every PXML file. It accepts the following attributes:<br />
<br />
* The command attribute specifies the path to the executable file. This should be a relative path to a file within the PND package.<br />
* The startdir attribute specifies the starting directory (Also known as the working directory) that the application should start in. This should be a relative path to a directory within the PND package, or to a well-known directory in the Pandora file system.<br />
* The standalone attribute specifies whether or not this application can run on its own, or if it needs parameters to run. A value of "true" or "1" means that the application can be run without parameters. A value of "false" or "0" means that the application must be run with parameters (Meaning that no icon will appear for it in a launcher; it will only be run via file associations or via the terminal).<br />
* The background attribute specifies whether or not this application should run in the background, and it should be possible to switch to other apps while it is running, or if it is the only application that should be running. A value of "true" or "1" means that the application can run in the background. A value of "false" or "0" means that the application must be run as the only application.<br />
<br />
==== Example ====<br />
<source lang="xml"><br />
<exec background="true" startdir="/usr/share/icons/" standalone="true" command="myprogram"/><br />
</source><br />
=== The icon element ===<br />
==== Description ====<br />
<br />
The icon element should specify a nice icon for your program.<br />
An icon element is optional. It accepts the following attributes:<br />
<br />
* The src attribute specifies the path to the image file used as the icon.<br />
==== Example ====<br />
<source lang="xml"><br />
<icon src="images/icon.png"/><br />
</source><br />
<br />
=== The previewpics element ===<br />
==== Description ====<br />
<br />
The previewpics element is an element that contains multiple other elements.<br />
A previewpics element is optional.<br />
<br />
It contains multiple pic-elements. Every pic-element represents one preview picture. If the previewpics element is specified, it must contain at least one pic element.<br />
<br />
* The src attribute on a pic element specifies the path to the image file used as the preview picture.<br />
==== Example ====<br />
<source lang="xml"><br />
<previewpics><br />
<pic src="preview/pic1.jpg"/><br />
<pic src="preview/pic2.jpg"/><br />
</previewpics><br />
</source><br />
<br />
=== The author element ===<br />
==== Description ====<br />
<br />
The author element is an element that is used by the author to introduce him/herself.<br />
An author element is optional. It accepts the following attributes:<br />
<br />
* The name attribute specifies the name of the author.<br />
* The website attribute specifies the website of the author.<br />
* The email attribute specifies the e-mail of the author. This attribute is not yet supported by libpnd, but please specify it anyways.<br />
==== Example ====<br />
<source lang="xml"><br />
<author name="Bjornhild Andersson" website="http://some.website.with.author.info"/><br />
</source><br />
=== The version element ===<br />
==== Description ====<br />
<br />
The version element specifies the application version.<br />
A version element is required. It accepts the following attributes:<br />
<br />
* The major attribute specifies the major version number. This number should be 0 or more.<br />
* The minor attribute specifies the minor version number. This number should be 0 or more.<br />
* The release attribute specifies the release number. This number should be 0 or more.<br />
* The build attribute specifies what build the application is at. This number should be 0 or more.<br />
==== Example ====<br />
<source lang="xml"><br />
<version major="1" minor="1" release="1" build="2"/><br />
</source><br />
=== The osversion element ===<br />
==== Description ====<br />
<br />
The osversion element specifies the application version.<br />
An osversion element is optional. It accepts the same attributes as the version element.<br />
==== Example ====<br />
<source lang="xml"><br />
<osversion major="1" minor="1" release="1" build="2"/><br />
</source><br />
=== The categories element ===<br />
==== Description ====<br />
<br />
The categories element is an element that contains multiple other elements.<br />
A categories element is required, and must contain at least one category.<br />
<br />
Menus that use your PXML in any shape or form will use the category information to sort your application entry into the tree or sub menus. Depending on the menu system, this will be done differently every time. It is therefore advisable to specify as many categories and subcategories as possible (and as suitable; don't specify that your application belongs in a category if it doesn't).<br />
<br />
The "categories" element contains multiple category-elements. Every category-element represents one category that this app can be sorted into. Valid top-level categories are (among others):<br />
<br />
# AudioVideo<br />
# Audio<br />
# Video<br />
# Development<br />
# Education<br />
# Game<br />
# Graphics<br />
# Network<br />
# Office<br />
# Settings<br />
# System<br />
# Utility<br />
<br />
Please see [http://standards.freedesktop.org/menu-spec/latest/apa.html the FreeDesktop specification] for more information. In it, you will also find valid subcategories for your top-level categories.<br />
<br />
The category-element takes one attribute: The name-attribute. This attribute represents the category name, which preferrably should be one of the above.<br />
<br />
A category-element can contain further child-elements: subcategory-elements. These represent the subcategories of a category that the app will be sorted into.<br />
<br />
The subcategory-element also takes a name-attribute; this attibute can contain a name for your subcategory.<br />
<br />
==== Example ====<br />
<source lang="xml"><br />
<categories><br />
<!-- This app belongs in the "Game/StrategyGame" category --><br />
<category name="Game"><br />
<subcategory name="StrategyGame"/><br />
</category><br />
<!-- This app also belongs in the "Graphics/ImageProcessing" category --><br />
<category name="Graphics"><br />
<subcategory name="ImageProcessing"/><br />
</category><br />
</categories><br />
</source><br />
=== The associations element ===<br />
==== Description ====<br />
<br />
The associations element is an element that contains multiple other elements.<br />
An associations element is optional, except if exec.standalone is false.<br />
<br />
It contains multiple association-elements. Every association-element represents one file action association.<br />
<br />
* The name attribute on an association element specifies the user-friendly action name for the association.<br />
* The filetype attribute on an association element specifies what file types (in MIME format) that this association should apply to.<br />
* The exec attribute on an association element specifies the command-line arguments that should be given to the program, when this action is performed. The exec can contain a "%s", which indicates where the file name of the file, that the action is performed on, should be inserted. For example, if the exec-line is "--file %s --type lol", and you have a file "lol.bmp" that the action is performed on, the exec-line is transformed into "--file "lol.bmp" --type lol"<br />
==== Example ====<br />
<source lang="xml"><br />
<associations><br />
<association name="Open Bitmap Image" filetype="image/bmp" exec="-f %s --no-deinterlacing"/><br />
<association name="Crash the computer with a stylesheet" filetype="text/css" exec="-f %s --crash-on-success"/><br />
</associations><br />
</source><br />
=== The clockspeed element ===<br />
==== Description ====<br />
<br />
The clockspeed element specifies what clockspeed this app should run at. Please do only specify this element if your application *needs* to run at the specified clock speed.<br />
A clockspeed element is optional. It accepts the following attributes:<br />
<br />
* The frequency attribute specifies the wanted frequency, in megahertz (MHz).<br />
<br />
==== Example ====<br />
<source lang="xml"><br />
<clockspeed frequency="600"/><br />
</source><br />
== Example file ==<br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<PXML id="youruniqueID" xmlns="http://openpandora.org/namespaces/PXML"><br />
<title lang="en_US">Program Title</title><br />
<title lang="de_DE">German Program Title</title><br />
<br />
<exec background="true" startdir="/usr/share/icons/" standalone="true" command="program"/><br />
<br />
<icon src="program.png"/><br />
<br />
<description lang="en_US">This is the English Description of the file.</description><br />
<description lang="de_DE">This would be the German description.</description><br />
<br />
<previewpics><br />
<pic src="preview/pic1.jpg"/><br />
<pic src="preview/pic2.jpg"/><br />
</previewpics><br />
<br />
<author name="Some Dudeson" website="http://a.bc.de"/><br />
<br />
<version major="1" minor="1" release="1" build="2"/><br />
<osversion major="1" minor="0" release="0" build="0"/><br />
<br />
<categories><br />
<category name="Game"><br />
<subcategory name="StrategyGame"/><br />
</category><br />
<category name="Graphics"><br />
<subcategory name="ImageProcessing"/><br />
</category><br />
</categories><br />
<br />
<associations><br />
<association name="View Word File" filetype="application/msword" exec="-f %s -t doc"/><br />
</associations><br />
<br />
<clockspeed frequency="600"/><br />
</PXML><br />
</source><br />
<br />
== Validation ==<br />
<br />
To validate a PXML file, you need a XSD (XML schema) validator, and you have to know how to use it.<br />
<br />
You will also need to put the XML schema for the PXML format in the same folder as your PXML file.<br />
<br />
When you have done that, and know how to use it, you need to change a few things in your PXML file. In your PXML tag, change the contents from this...<br />
<source lang="xml"><br />
<PXML id="..." xmlns="http://openpandora.org/namespaces/PXML"> ...<br />
</source><br />
<br />
...to this:<br />
<source lang="xml"><br />
<PXML id="..." xmlns="http://openpandora.org/namespaces/PXML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PXML_schema.xsd"> ...<br />
</source><br />
<br />
Now the PXML file can be validated.<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Libpnd_hub&diff=2000Libpnd hub2010-01-10T20:43:39Z<p>Glenn: +cat</p>
<hr />
<div>=libpnd - the Pandora Library=<br />
<br />
libpnd is a basic collection of functions and tools to make working Pandora-specific operations easier; to wit, it is hoped multiple applications will make use of this library rather than re-implement similar functionality and lead to problems down the road. (Instead we can run into problems together and thus clobberize them.) <br />
<br />
libpnd thus is a collection of ...<br />
<br />
- handy system code that hopefully is reusable - IO functions, CPU clock setting, etc.<br />
<br />
- applications for supporting the Pandora unique features, such as pndnotifyd for auto-discovery of PXML and .pnd applicatons<br />
<br />
- libraries for support of the .pnd and PXML systems; i.e.: for locating, executable, mounting and unmounting PXML-directory and .pnd applications, loading PXML and handling overrides<br />
<br />
- hopefully reusable code for support of these things; i.e.: a rudimentary but useful config-file parser, rudimentary singly-linked-list container, etc.<br />
<br />
libpnd will/does also include utility functions for setting the CPU clock, reading GPIO inputs without depending on SDL, and other handy bits.<br />
<br />
'''You can, nay, are needed - contribute to libpnd!'''<br />
<br />
==Design considerations and philosophy==<br />
<br />
While much of libpnd is obvious, some decisions had to be made and it may help to know the guiding principle behind it; the Pandora device will be a handheld _computer_, but libpnd is designed to facilitate certain operations with goals towards..<br />
<br />
- simplicity - just work right, configuration not generally needed<br />
<br />
- obviousness - work as one would expect for this sort of device; i.e.: the user assumes something will work a certain way, and it does<br />
<br />
- like other guys - as an extension of the prior point, we have tried to follow UNIX spirit and provide reusable small tools to do the work those bits can be leveraged, but further tried to follow the spirit of other consoles. So while the device is a powerful little computer, it is probably going to be used by gaming and retro enthusiasts and so we color some of our decisions that way. (i.e.: consider that a PS2/xbox/PSP/etc will have save-game or data management as a separate application, for instance. If thats the best multi-million dollar companies can come up with over decades, well, its not so bad for us to fall back on!)<br />
<br />
- not over-defined; libpnd and PXML try to define a bunch of things, but we also do not _over define_; we try to lead by providing examples and styles, and while we have designed ahead for many things, we have also not nailed a lot of that down too early. It is better to be simple and shipped, then complex and a mess.. adaptable rather than scary.<br />
<br />
The library is of course broken into parts:<br />
<br />
<pre><br />
include - include these files to make use of the lib<br />
lib - the code that produces the lib<br />
test - mini tools to test various pieces of the lib in isolation<br />
bin - test tools - tools for testing the lib as it is developed, not anticipated to be used by many<br />
testdata/ - for testing /etc/pandora; will contain 'conf' dir, for example<br />
apps/ - actual applications people may use, such as pndnotifyd<br />
</pre><br />
<br />
For now though, here are a couple notes about the design.<br />
<br />
- it is straight C code, to be maximumly re-usable (perhaps C++ and other language bindings will tie back to it). I have gone out of my way to limit external references so that bindings are easier to make. <br />
<br />
- contrary to the previous comment, we've used a bit of C++ for the tinyxml parser .. hopefully this is not an issue.<br />
<br />
- I have tried to keep the API relatively simple and am faking some OO like data hiding to try to keep dev noses out of structures that are subject to change. i.e.: functions for list management and node access are provided, don't dig into the void* cast structs, or you could get burnt.<br />
<br />
- the API should be pretty stable; so far very few user-code changes have ever been needed.. lib internal changes should be binary compatible.<br />
<br />
- As a result of that decision, 'handles' are used; a handle is a 'black box' type, something you cannot just use 'handle h; h -> foo = 5' type code for. Instead, internally the library will cast the handle to the actual useful type (which may involve pointer arith etc). This way the user can be returned a handle, and pass the handle to various access functions to get useful data/operations.. but the user is not encouraged to look inside the data objects himself<br />
<br />
- As another implication, access functions are available aplenty; it is a little unwieldy perhaps, but its all about keeping the API good without the user peeking inside and risking being broken down the road. (By example, consider.. you use ftell() on a FILE object; you don't go looking in FILE for the 'position' member, since it might be platform specific, etc.)<br />
<br />
- The lib works pretty well, but there is room for improvement internally; it won't hurt my feelings for you to suggest improvements, and I'm sure we would all be grateful for any patches you provide. We've _started_ this library, but by no means wish to carry it alone!<br />
<br />
==Opportunities for improvement==<br />
<br />
Certainly nothing is perfect, especially when chasing moving targets. Some aspects of the library are less efficient, or missing, or buggy, and a few things are noted here should someone have time. The API was designed to be pretty stable so the internal code could be altered without breaking the API interface.<br />
<br />
- better ISO lang handling .. due to shift from original PXML spec to new PXML spec with better lang support I've not updated some of the internal code, API uses etc to handle it. (even .desktop files could include all iso-lang titles, and let the WM pick through as the spec suggests.)<br />
<br />
==License==<br />
<br />
libpnd (including all the apps etc) are released under the LGPL (ie: so there should be no encumbrances that prevent linking to commercial applications.)<br />
<br />
1 GNU LESSER GENERAL PUBLIC LICENSE<br />
<br />
2 Version 2.1, February 1999<br />
<br />
==Obtaining the library==<br />
<br />
libpnd is in the Official Pandora GIT repo: [http://git.openpandora.org/cgi-bin/gitweb.cgi]<br />
<br />
To obtain yourself a copy, use something like:<br />
<br />
<pre><br />
git clone git://git.openpandora.org/pandora-libraries.git<br />
</pre><br />
<br />
Thats all you normally need. For copy-paste from the private Wiki sake, heres what I had before:<br />
<br />
Without going into how to set up a GIT, the summary that I (as a registered dev in the repo) used was:<br />
<br />
<pre><br />
mkdir libpnd<br />
cd libpnd<br />
git init<br />
git remote add libpnd ssh://foo@git.openpandora.org/srv/git/pandora-libraries.git<br />
git pull libpnd master<br />
</pre><br />
<br />
==Building the library==<br />
<br />
Standard 'make' should be sufficient here; pull down the directory from the GIT, cd into it, and run make. Thats it.<br />
<br />
Note that the make default target is 'everything', which will emit:<br />
<pre><br />
libpnd.a - the static linked version of the lib<br />
libpnd.so.1.0.1 - the dynlinked version<br />
libpnd.so.1 - the stub for the shared lib; i.e.: apps should link against libpnd.so.1 and not the 1.0.1 over-specific version<br />
bin/* - the 'test' dir and the 'apps' dir builds will end up in bin<br />
</pre><br />
<br />
There are a few additional make targets, however.<br />
<br />
<pre><br />
make clean - wipes out the object files, the bin files, and *~* (emacs backup files), empties some of the deploy stuff, etc. Do this before committing to GIT or we will beat you with sticks.<br />
make deploy - populates the deploy/ directory, which is what is used inthe shipping images; i.e.: testdata/conf includes test configs, while deploy/etc/pandora/conf includes the configs we ship with. This make will copy over some of the libs and binaries and such.<br />
make pnd - create a few sample pnd files for testing the lib on an x86 machine<br />
</pre><br />
<br />
==Included Applications==<br />
<br />
===pndnotifyd===<br />
<br />
Manages the auto-discovery mechanism and integrating PXML.xml dir-apps and .pnd files into the FreeDesktop standard system (.desktop files). A dedicated libpnd-aware menu could leverage libpnd directly and not need pndnotifyd, though pndnotifyd does offer some handy bits such as HUPping apps to suggest to them that applications may have been added/removed (libpnd includes all the necessary functions for this as well.)<br />
<br />
===pndvalidator===<br />
<br />
Is mostly a skeleton right now; in the future, it is hoped it will inspect a PXML.xml and then check to ensure the referenced assets are present; the goal to validate the PXML.xml is spec compliant, and the resulting application would be useful.<br />
<br />
===discotest===<br />
<br />
One of the test tools; it essentially runs an auto-discovery to list off the found apps (be they PXML.xml dir apps or .pnd files), and can dump various data or invoke one or other little tasks; used to test lots of<br />
bits of libpnd as it was developed.<br />
<br />
===rawpxmltest===<br />
<br />
Reads a given PXML.xml and spits out some of the fields found within.<br />
<br />
===test tools===<br />
<br />
See the test/ dir in the libpnd source for assorted goofy little test apps used for testing bits of libpnd over time. They also may serve as source examples for using some of the APIs. They're old and shoddy probably too.<br />
<br />
==Distributed PXML.xml-directory and pnd applications, how does running them actually work?==<br />
<br />
This is just a quick summary to save you guessing by reading this whole document.<br />
<br />
In essence, libpnd includes lots of real code, but in many places it passes heavy lifting off to shellscripts. This is both handy because the scripts are easily modified without recompilation, and further extends our design goals of making the library bindable to any other language.<br />
<br />
Remember, PXML.xml directories are just as executable/mountable as .pnd apps.<br />
<br />
So while libpnd is mostly straight-C and so easily bound to python or perl or whatever, libpnd itself invokes many scripts. Those scripts can be directly used by other applications, including other shellscripts.. so libnd functionality can even have bindings in other scripts. This is very flexible and powerful, and handy during debugging or SSHing into the Pandora, etc.<br />
<br />
The application lifecycle goes like this:<br />
<br />
- device is turned on<br />
<br />
- during init, pndnotifyd is brought up and inhales the config giles<br />
<br />
- pndnotidyd will attempt to auto-discover what PXML.xml directory apps and .pnd-file apps are in the configured searchpaths<br />
<br />
- pndnotifyd will set up filesystem watches on the directories in the notify searchpath; if any of those directories are touched, pndnotifyd will wake up and re-auto-discover .. possibly removing .desktop entries or creating new ones. (i.e.: you drop a new app into the app searchpath, or remove one, or mount an SD card, etc. This is how appications immediately show up or vanish from the window manager desktops.)<br />
<br />
- a libpnd aware launcher can execute applications direct (using libpnd)<br />
<br />
- a libpnd unaware launcher can execute applications via the .desktop standard system; pndnotidyd will emit .desktop files as needed.<br />
<br />
- when libpnd or a .desktop file need to execute an application, they do it via pnd_run.sh (which may be leveraged by other applications, but they hould use libpnd if they can instead, for utmost compatiblity down the road.) pnd_run.sh does the mount of the ISO, runs the actual execable and so on, as directed by libpnd or the command-line args from the .desktop. pnd_run.sh will clean up after everything as well.<br />
<br />
So it all works like magic, but it is not that complex a system once you've got the hang of what all is going on.<br />
<br />
application -> libpnd -> shellscripts -> system<br />
<br />
==FAQ: IF you want to make files visible to the apps, do you have to modify the pnd?==<br />
<br />
No. When apps write back to themselves, the writes go to their /pandora/appdata on the SD that houses them. The next time the app reads a file in its directory, the OS will ensure they get the newer file, which is the one in the appdata.<br />
<br />
Likewise, you can just drop a file into the appdata and the app will see it.<br />
<br />
The app doesn't know about appdata and its pnd file.. the OS and libpnd take care of all the magic.. the app sees one directory, but the reality is there is magic merging going on behind the scenes.<br />
<br />
==Assumptions about the filesystem and Configuration==<br />
<br />
Note that for libpnd to work, it makes certain assumptions about the filesystem and config files. Since libpnd was developed with the images it should work for the Pandora .. but just dropping libpnd onto another Linux distribution and it won't likely 'work out of the box'. Certain config files will need to be set, and certain conventions followed.<br />
<br />
===Searchpaths===<br />
<br />
libpnd was designed so that most everything is configured in files, and that these files should be easily hackable and easily overriden, without compromising the machine. It should be feasible to add a config file to an SD card, have it take over if available when required, and then 'undo' those configs simply by removal of the SD card and rebooting.<br />
<br />
To facilitate this design goal, all config files are 'sought' using a search-path system.<br />
<br />
Developers should be mindful of using the libpnd APIs so this behaviour is inherited to interested applications; developers could also reuse the logic for searching for files, if they find it useful.<br />
<br />
Searchpaths are colon-delimited list of paths, searched left to right.<br />
<br />
ex: foo:bar:/my/baz means to look for a given file in 'foo', then in 'bar', then in '/my/baz'.<br />
<br />
The standard config files have a default searchpath, and those config files will define further searchpaths for scripts and such the system uses. This makes the system highly flexible -- default scripts are included, but can be overridden by dropping the right named script on an SD card, or by altering a config file.<br />
<br />
See the example config files below for example searchpaths -- i.e.: how pndnotifyd searches for pnd_run, etc.<br />
<br />
===Notification paths===<br />
<br />
The 'apps' config includes a searchpath that specifies the sub-paths to be 'watched'. Various watch mechanisms exist for various filesystem types, but over the course of Pandora development (various kernels, various k-modules, various DM and WM's, I found the included system most stable, though not most current. After a final device image is settled on, it might be time to alter the notification system, but it should not impact the libpnd API.)<br />
<br />
Anyway, watches are placed upon the paths defined, and if anything in those paths changes, the auto-discovery code is kicked off to seek our PXML.xml and .pnd type applications in the search paths.<br />
<br />
Note that searchpath and notifypaths are different (and usually very similar, but have the option to be very different.)<br />
<br />
===Config files===<br />
<br />
libpnd includes a generic simple config file parser and assumes the presence of a few config files. It also includes defaults<br />
so if a config is missing or broken things should work.<br />
<br />
In general, Pandora specific config files should be located in:<br />
<pre><br />
/etc/pandora/conf<br />
</pre><br />
<br />
The config files are:<br />
<pre><br />
conf -- this file is generally _not_ included with the Pandora and left to default; its job is to define the basic default searchpath for config files, so should you wish to override things entirely, you may need to alter this file. i.e.: If you wish to switch to test config files on SD or in /tmp, instead of using any other conf files .. you can create this guy. This provides a mechanism to short circuit the entire conf system.<br />
<br />
apps -- this config file defines auto-discovery and other application bundle parameters<br />
<br />
desktop -- this config defines "dotdesktop" .desktop and FreeDesktop integration paramters -- example is where to spit out icons or .desktop files from discovered PXML.xml or pnd applications<br />
<br />
categories -- this config maps PXML.xml spec based categories to FreeDesktop standard categories; in this way a PXML based applicatoin can show up in the appropriate categories of a WM that does not use libpnd<br />
</pre><br />
<br />
====conf File====<br />
<br />
No default is included with the distribution.<br />
<br />
The default search path is reasonable and assumes we want the official /etc/pandora/conf near the end, with checks to the SD cards for overrides first. (Likely most people will not override, so the canonical location will be used 99.9% of the time.)<br />
<br />
<pre><br />
#define PND_CONF_SEARCHPATH "/media/mmcblk0p1/pandora/conf:/media/mmcblk1p1/pandora/conf:/etc/pandora/conf:./testdata/conf"<br />
</pre><br />
<br />
The key for override is:<br />
<br />
<pre><br />
#define PND_CONF_KEY "conf.searchpath" /* if not found, use PND_CONF_SEARCHPATH */<br />
</pre><br />
<br />
Which suggests using something like this.<br />
<br />
<pre><br />
[conf]<br />
searchpath /foo/bar:/baz/bing<br />
</pre><br />
<br />
====desktop File====<br />
<br />
<pre><br />
# Open Pandora<br />
# Desktop configuration<br />
<br />
[dotfiles]<br />
#(~/Desktop for xfce, /usr/share/applications for WMs that actually follow spec)<br />
dotdesktoppath ~/Desktop/ # path for pndnotifyd to spit .desktop files into (run as root)<br />
iconpath /tmp # path for pndnotifyd to drop icons into (can be same as .desktop if WM permits)<br />
<br />
[launcher]<br />
# if hupscript is commented out entirely, pndnotifyd will not try to find/run the hup<br />
# if it is uncommented, pndnotifyd will attempt to invoke the hupscript after emitting .desktop files<br />
# (the hupscript exists to hup the WMs to redisplay .desktop apps)<br />
#hupscript pnd_hup.sh<br />
</pre><br />
<br />
====apps File====<br />
<br />
<pre><br />
# Open Pandora<br />
# Application configuration<br />
<br />
[autodiscovery]<br />
# searchpath is a list of paths (colon separated) in which to look for PXML.xml or .pnd-file applications<br />
searchpath /media/*/pandora/apps:/usr/pandora/apps<br />
# notifypath is a list of paths to monitor; if anything in those paths changes, the searchpath is rescanned<br />
# note that for each path chunk, all current subdirs of that path are also watched)<br />
notifypath /media:/media/*/pandora/apps:/usr/pandora/apps:./testdata/app?<br />
<br />
# PXMLs may be overridden .. i.e.: overrides are a subset of PXML, where the values are copied over the full PXML<br />
[overrides]<br />
# searchpath to look for PXML overrides (which are named by the unique-id)<br />
searchpath ~/pxml-overrides<br />
<br />
# [pnd] defines where to locate the pnd support scripts, so the user may override pnd_run.sh without clobbering built in<br />
[pnd]<br />
searchpath /media/*/pandora/scripts:/usr/pandora/scripts<br />
runscript pnd_run.sh<br />
</pre><br />
<br />
====categories File====<br />
<br />
<pre><br />
# Open Pandora<br />
# dotdesktop configuration<br />
<br />
# this config file maps 'PXML' categories to free-desktop standard categories<br />
# i.e.: category 'Foo' could map to more standard 'Utility', thus making .desktop file<br />
# emitting a more useful thing<br />
<br />
# the standard listing of categories is:<br />
# http://standards.freedesktop.org/menu-spec/latest/apa.html<br />
<br />
# note that 'map' section in the config is _required_ for a match to be found; this<br />
# is done to separate categories from (future) top-level directives<br />
<br />
default Application;Utility;Network;<br />
<br />
[map]<br />
Development Development<br />
Education Education<br />
Games Game<br />
Graphics Graphics<br />
Internet Network<br />
Multimedia AudioVideo<br />
Office Office<br />
Settings Settings<br />
System System<br />
Utilities Utility<br />
</pre><br />
<br />
===SD card layout===<br />
<br />
libpnd concerns itself with things in the 'pandora' root folder on SD. We agonized over this decision, but settled on this to avoid cases where someone with a 16GB SDHC card puts 50-million files with ".pnd" on them, and expects reasonable performance. Instead, applications for instance would have to be in:<br />
<br />
<pre><br />
/pandora/menu -> apps that will go to /usr/share/applications and should show up in xfce menu by category<br />
/pandora/desktop -> apps that will go to ~/Desktop and show up on user desktop as icons<br />
</pre><br />
<br />
The following location is used by pmenu (and may get deprecated, but I've not discussed it with cpasjuste yet.)<br />
<br />
<pre><br />
/pandora/apps<br />
</pre><br />
<br />
i.e.: the searchpath for autodiscovery includes /media/*/pandora/apps (and desktop and menu now)<br />
<br />
Also in the /pandora/ folder is a magic 'appdata' folder:<br />
<br />
<pre><br />
/pandora/appdata<br />
</pre><br />
<br />
When a .pndfile or PXML.xml dir get mounted, any writes back to the mounted area are put into appdata, with a subdir by the unique-id. i.e.: With the hypothetical MAME.pnd, it might update its config files after a user changes something, or create new files, or store hiscores or whatever. If it doesn't write them to NAND, and doesn't want ot write them to /mame/some/dir, but instead record it to itself for whatever reason, it would go to /pandora/appdata/MAMEs-ID/ instead. The pnd or PXML.xml app area is never modified during a run, only the appdata. (But when an application reads its own path, it will pick up the appdata version of the file instead of the actual file. Then magic of union-type filesystems!)<br />
<br />
Example:<br />
<br />
If Myapp with unique-id foo.123 is mounted, then any write-backs are directed to..<br />
<br />
/pandora/appdata/foo.123/<br />
<br />
On the SD that hosts the application.<br />
<br />
===NAND layout===<br />
<br />
In addition to seeking applications in SD cards, /usr/pandora/apps is included in the default searchpath, so that 'built in' apps can be listed, or users can drop them there.<br />
<br />
It might be a cool addition to put a user homedir into the searchpath as well, so NAND but user-homedir (for on-device browser downloads, say.)<br />
<br />
==Command line tools and testing==<br />
<br />
A number of scripts and tools are included or built with libpnd, to facilitate testing of the lib as its being developed and to assist in making .pnd files and PXML.xml files.<br />
<br />
==PXML.xml and .pnd files==<br />
<br />
On most platforms, applications are distributed as an executable and optional datafiles and likely an installer. The installers job is to integrate the application into the filesystem, as the transport mechanism itself is not executable and is considered temporary. In Windows an application might be installed into Program Files, while in Unix an application might be dropped into /usr/local/bin .. data files in various other places.<br />
<br />
For the Pandora platform we wanted a very easy to use workflow -- download and run -- and also have a very different operating environment. With multiple SD cards available for expansion (and that space being highly desirable due to a smaller internal store) it is desirable to install applications to SD, and yet SD cards are by definition something users will wish to carry multiple of. With two slots, it could be quite a chore to install an application to SD1, its data to SD2, and then say have only one of them plugged in at a time, or switch which slot they're in, or any number of scenarios. i.e.: Installing onto a medium which may be present or not at any time is very different to how most operating systems work. So we made something new and awesome.<br />
<br />
The PXML.xml and .pnd-file approach we came up with attempts to address these issues.<br />
<br />
The goals:<br />
<br />
- for the user, an application can be a single file download<br />
<br />
- furthermore, there is no installation whatsoever, beyond dropping that single file into the right place on the SD card<br />
<br />
- using the application should be easy -- stick in the SD card, and tap/launch on the icon.<br />
<br />
- for uninstallation, delete the single file. Thats it, no fuss.<br />
<br />
- for the developer, creating that single file should be easy to do<br />
<br />
- for the system, performance should be high<br />
<br />
Remember, an application can be a .pnd 'bundle' (single file containing all the sub-files), or a PXML.xml 'dir application' (an unpacked .pnd esentially.) '''BOTH PXML.xml-dirs and .pnd's ARE EXECUTABLE.'''<br />
<br />
pndnotifyd will auto-discover PXML.xml in a directory and consider that an application, emitting a .desktop file, just as well as a .pnd file. i.e.: This can be hand for development or users. Remember that a mounted PXML.xml dir still redirect write-backs to the /pandora/appdata directory, just like a full .pnd application. They are treated the same!<br />
<br />
===What are PXML.xml and .pnd files?===<br />
<br />
PXML.xml is a file describing an application<br />
<br />
A directory containing a PXML.xml _is executable_<br />
<br />
A .pnd file is the packaged up version of the directory that is executable.<br />
<br />
i.e.: a PXML.xml in a directory is just as executable as a .pnd representation of that directory.<br />
<br />
example:<br />
<br />
mkdir OutcaST<br />
cp outcast.bin OutcaST/<br />
cp PXML.xml OutcaST/<br />
# at this point, the OutcaST directory is now discoverable and executable<br />
<br />
pnd_make.sh -this -that OutcaST outcast.pnd<br />
# at this point, outcast.pnd is executable (as is the OutcaST directory), so upload outcast.pnd to the Open Handhelds Archive and let people enjoy!<br />
<br />
===A note on including shared libs===<br />
A philsophy for packaging that I am advocating is to 'just make applications work' -- avoid dependancy trees.<br />
<br />
Some guidelines:<br />
<br />
1) you can depend on shared libs included with the firmware to always be there<br />
<br />
2) you should include any shared libs you need for your app, that are not in the firmware (yes, this increases app size a little bit, and potentially makes for duplication among apps that use the same shared libs)<br />
<br />
3) if a shared lib becomes desirable in the firmware, it can be added there as a firmware patch easily (this has the advantage of gradulaly updating the entire user based, and apps easily saying 'we depend in firmware version X', rather than making for pnd-dependnacies and the equivilent of 'dll hell'<br />
<br />
4) You'll have to be careful in linking your application to ensure that the shared libs you are including in the pnd/PXML-dir are to be locatable by your binaries. ie: stick them in a 'lib/' dir in your bundle, and stamp your binary with a library-path './dir/' so they can be found, say. More later.<br />
<br />
===Future idea: pnd's for containing system-wide shared libs===<br />
<br />
This is something we've bounced around for quite awhile, but not committed to. As it keeps coming up I thought I'd put some notes here in public.<br />
<br />
It is possibly desirable to make a special searchpath that is discovered during machine boot, and any pnd's found there are automatically mounted (and left mounted) into a special path (say /usr/local/pandora/lib or somesuch.) This way, collections of handy utilities or shared libraries could be distributed as a pnd, and become available in consistent locations. If 10 applications need a shared lib, and don't want to duplciate it in each of their pnd files, this could be an approach.<br />
<br />
I tend to think it is best avoided, however, since it complicates the user experience -- we end up with pnd depandancies, and apps nolonger about to 'just work', and apps that did work and 'suddenly break' when other files are altered. The philosphy we're going for with pnd files is 'drag and drop' -- user downloads a pnd file, and it works.. a self contained application, nice and easy. We start complicating the dependancies, and it turns into 'dll hell' as seen on other platforms.<br />
<br />
That said, it is _not_ difficult to add into the existing system and design; we've been mulling it over, but it is best avoided for now. rather than complicate the system up front, let us try to get a functional and as lightweight-as-possible system on the uptake, gather some usage data points and then worry about upgrades :)<br />
<br />
===File format - PXML.xml===<br />
See the [[PXML_specification|PXML specification]]<br />
<br />
Alternatively the spec is included in the docs/ directory of the libpnd distribution, though the wiki version linked above should be considered cannon.<br />
<br />
A note on history; the PXML spec was originally created by EvilDragon, and went through a number of revisions as suggestions came in; as these things are wont to do, the target was ever moving and the scope and meaning of PXML changed so at some point a more strategic approach was needed. dflemstr took it upon himself to help recode some of the parse and re-evaluate many of the PXML decisions and hence was born the PXML-version-2 spec.<br />
<br />
===File format - .pnd files===<br />
The pnd file format is pretty straight forward, though most will interact with it through the included (or community supplied) tools.<br />
<br />
Basically its just an ISO file (or other filesystem type) with a PXML.xml and an optional PNG icon appended. (example: cat appfolder.iso app.pxml icon.png > app.pnd) For ease of discussion, I refer to ISO but in fact you coudl be using squashfs or other types.<br />
<br />
The ISO filesystem portion of the file can include anything the developer wishes, as long as it includes a PXML.xml in its root file and an executable somewhere in there. It can also include images, audio files, data files of any kind. It can be small or large.<br />
<br />
Yes, the PXML.xml is included in the ISO portion (in the root directory), and also appended to the end of the .pnd file (for _convenience_ .. it is very easy and fast to locate in this position; we can backseek into the ISO to find the PXML, but if its a 500MB ISO it could take awhile. Hence, we append it and can find it in one seek.)<br />
<br />
This simple format makes it possible to easily create .pnd files with the default utility's of most operating systems. Further, it is a fairly fail-safe system -- the PXML is appended, but is also included within the ISO image part of the file so if the appended-PXML is ever lost (unpack and repack poorly, say) the system will still work (the PXML inside the ISO can be found easily, even without mounting the ISO _as_ an ISO, since it is a plaintext uncompressed image format.) <br />
<br />
Manually creating a .pnd (or even a PXML) is a pain so there will be a few helper scripts or maybe even a gui app out when we launch.<br />
<br />
Included with libpnd are some scripts to create PXML and pndfiles, though it is expected people will create handier utilities. See the tool section of this wiki for some details.<br />
<br />
Question from the gp32x forum regarding confusion of PXML location -- remember that in general mot developers will keep a directory that represents the .pnd or PXML-dir application. Their makefile/build-process will drop the executable(s) into that directory, which inludes a PXML.xml description of the application, and possibly an icon (and whatever all else they wish.) To build the .pnd file, a script (say) is used which compresses all this into the pnd format (including appending the PXML.) So yes, the PXML is in two places in the .pnd file and one place in the source directory. You'll get used to it ;)<br />
<br />
Rationale --<br />
<br />
Several iterations of pnd files have been considered, from zipfiles to cramfs to other formats, to putting in a key/value set of information tags in the file, to table-of-contents indexes, to any number of options to help performance, and so on. In the end we went for a good overall and simple solution and dropped getting fancy -- PXML.xml can be extended to define the type of the file if it cannot be magic'd, so we could using other filesystem types in the future (and this is why people should use libpnd rather than rolling their own solution.) For now however, pnd files are ISO files with the PXML.xml appended and an optional icon. This keeps the PXML and icon easy to locate, and yet a easy file format.<br />
<br />
====What filesystem types can be contained within a pnd-file?====<br />
<br />
The pnd container can really contain a large variety of filesystem types; day-zero we're aiming for ISO since it is simple, easy build across every major OS, and fast to use. But it is not the only supported filesystem type, and more should be added all the time. (Possibly '-auto' can be added to pnd-run and it'll "just work" for dozens of types!)<br />
<br />
A compressed filesystem type has always been desirable for file sizing reasons, though it potentially impacts performance (depending on the application operation really.)<br />
<br />
Supported types (not an exhaustive list!):<br />
<br />
o ISO<br />
<br />
o squashfs<br />
<br />
====PND generation workflow====<br />
<br />
- create a directory to represent the application on SD card; i.e.: ./mame-app<br />
<br />
- create a PXML.xml fil and drop it into the dir (./mame-app/PXML.xml); genpxml script can be used, or do it by hand<br />
<br />
- drop the executable and data files into this dir (say, ./mame-app/mame.bin, and ./mame-app/artwork/foo, etc.)''' <- note, with a PXML.xml and executabe, it can now be discovered and run without even bundling into .pnd!'''<br />
<br />
- invoke pnd-make.sh to produce mame4all-pandora-1.0-arm.pnd or whatever you want to call it (foobearspanky.pnd, we don't care.)<br />
<br />
- you're done, distribute it as you see fit<br />
<br />
====Making PND files - Windows / DOS commandline====<br />
<br />
There should be a basic GUI along very soon, and more advanced friendlier GUIs in due time. But for now, we thought it prudent to include some basic instructions on the command line for day-zero.<br />
<br />
For this command-line tutorial, I will assume you have already created a PXML.xml file; copy one of the templates and then edit it, using notepad or whatever _TEXT_ editor you see fit.<br />
<br />
Prepare in advance:<br />
<br />
1) Make a PXML.xml file (through whatever means; copy a template, or get a PXML.xml tool when they come available.) Ensure that you've got a reasonably unique-id in that field (ie: say, app-name, your name, and date/time all catenated together.) <br />
<br />
2) Get yourself mkisofs tools; for example, grab from here: http://www.student.tugraz.at/thomas.plank/ -- get cdrtools-2.01-win32-bin.zip and DLL version 1.5.25, and extract to somewhere. That lets you run 'mkisofs' to spit out .iso files<br />
<br />
2b) If you want to make a compressed image, use squashfs tools here: ftp://ftp.slax.org/useful-binaries/win32/squashfs-tools/<br />
<br />
3) Put your application and all needed files into a single directory .. say "myapp"; it doesn't matter what you call it. Might be cool as a Makefile step<br />
<br />
4) In your app-dir, put the PXML.xml file in the root<br />
<br />
5) Put the icon in the root of that dir as well (make it a .png file)<br />
<br />
6) Make sure the PXML.xml names the icon (just its filename.png), and specifies the executable (foo.bin or whatever.)<br />
<br />
Generate the actual PND-file, fully manual method:<br />
<br />
1) Make yourself the iso; this step produces the iso, but to turn the iso into a pnd you need a couple last steps. You could also use some fancy iso-building tool.<br />
'''mkisofs -o foo.iso -R /path/to/folder/myapp'''<br />
<br />
2) Append PXML.xml to the .iso (yes, the PXML.xml is included in the iso, but we also want to append it for performance reasons.) <br />
'''copy foo.iso+PXML.xml foo.step2'''<br />
<br />
3) Append the icon PNG file to the .iso (if you have an icon; if not, you can leave this step out.)<br />
'''copy foo.step2+myicon.png foo.pnd'''<br />
<br />
4) Clean up: del''' foo.step2 foo.iso'''<br />
<br />
5) Profit!<br />
<br />
====Making PND files - Linux/BSD/Unix (including on Pandora)====<br />
<br />
=====Command-line=====<br />
<br />
Tools are included in the libpnd distribution; see below for discussion, but suffice to say they are included int he GIT. Look in testdata/scripts for:<br />
<br />
o genpxml - spits out a template PXML.xml for you, and even includes a reasonably unique-id<br />
o pnd-make.sh - given a directory and some arguments, will spit out a .pnd file; great for use in Makefiles<br />
<br />
We're working on others as well, so piece of cake under Unix and Unix-like OSes.<br />
<br />
=====GUI=====<br />
<br />
TBD<br />
<br />
====Making PND files - Windows GUI====<br />
<br />
====Making PND files - Mac OSX====<br />
<br />
===PXML overrides===<br />
<br />
PXML.xml files can have any number of their elements over-ridden by user preferences. <br />
<br />
The design goal here was to make it so user-preferences could alter the impact of the PXML.xml in any way, but without requiring the actual PXML.xml in the .pnd (and within the ISO therein) to be altered (could be a 500MB ISO after all!), and further, for these changes to persist. Consider than an SD card could be removed and inserted into the other slot, or the app could be removed entirely and come back another day, or other scenarios.<br />
<br />
As such, the PXML-overrides are kept in NAND in the user homedirectory (See the config files to find out where.)<br />
<br />
libpnd includes functions to pull in PXML, and also functions to then look for and merge in overrides. It is not always done since you may wish to inspect the PXML or the overrides, so the developers job is to do as they see fit -- pull the XML, and likely also pull in the overrides.<br />
<br />
At this time I'm not sure if people will ever use overrides, but the system has been built in should it be needed.<br />
<br />
===Included shellscripts to generate files and other sundry duties===<br />
<br />
====genpxml====<br />
<br />
This tool can spit out a basic but correct PXML.xml, faking up a halfway-useful unique-id in the process. It might be handy in saving you writing up a PXML.xml from scratch.<br />
<br />
====pnd_hup.sh====<br />
<br />
pndnotifyd will attempt to locate this script and invoke it after an auto-discovery run, if the pnd_hup entry is present (and uncommented) in the config files. It is expected to be commented out in release images, as xfce watches directories for .desktop files and does not need a HUP; some desktop managers need to be HUPped to rescan for .desktop files in a timely fashion, so the pnd_hup config entry can be uncommented and this script will attempt to figure out who to HUP.<br />
<br />
====pnd_make.sh====<br />
<br />
This is one of the great ones :)<br />
<br />
Given a directory with a PXML.xml (see genpxml above) and an executable and any other goo you want in there, this script will spit out a .pnd file you can execute or distribute as an application.<br />
<br />
====pnd_run.sh====<br />
<br />
This job does a lot of the heavy lifting for libpnd, including setting up the 'union filesystems', doing .pnd and PXML.xml-app-dir execution and mounting, and so on. Generally you will talk to it via libpnd or .desktop files, but you can invoke it dorectly from your apps if you wish to circumvent libpnd or mount .pnd files within a shellscript/perlscript/etc.<br />
<br />
==Auto-discovery of applications==<br />
<br />
TBD.<br />
<br />
==Integration with FreeDesktop .desktop systems==<br />
<br />
===dotdesktop (.desktop) files===<br />
<br />
===Icons===<br />
<br />
There are some rules for Icons in PXML.xml and pnd/directory bundles<br />
<br />
- An Icon should be in the root of the directory or .pnd bundle<br />
<br />
- An Icon must be specified in the PXML.xml if you expect it to work<br />
<br />
- As the PXML.xml is parsed, the icon is sought; if the icon is specified, but not found, it is assumed to be a system default icon and the filename will be placed into the .desktop Icon= line verbatim (ex: Icon=foo.png), and the window manager presumably will know how to locate it. If the icon is specified, and is found, then it will be copied into the configured IconPath, and the full path to it will be used for the Icon= line in the .desktop file ex: Icon=/tmp/myicon.png). If no icon is specified in the PXML file, then no Icon= line will be entered into the .desktop and the WM will presumably apply a default icon based on category or whatever.<br />
<br />
<br />
==APIs==<br />
<br />
Feel free to just go read the .h files; I have tried to comment liberally :)<br />
<br />
===Setting and Getting the CPU clock speed===<br />
<br />
===Device paramaters - brightness, etc===<br />
<br />
===PND files, exec and mount===<br />
<br />
===Application discovery===<br />
<br />
===Config file parsing===<br />
<br />
===Boxing, the singly-linked list container===<br />
<br />
===Directory watching===<br />
<br />
===Logging api===<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Floating_Point_Optimization&diff=1998Floating Point Optimization2010-01-10T20:42:13Z<p>Glenn: +cat</p>
<hr />
<div>== Introduction ==<br />
In the past it was rare for an embedded processor to have dedicated floating point hardware, this usually limited you to either using fixed point math (which can be very tricky to write) or very slow software floating point emulation. Fortunately the ARM Cortex A8 found in the OMAP3 has 2 Floating Point Units, a non-pipelined VFP-lite conforming to the IEEE754 standard for floating point arithmetic and a pipelined SIMD NEON coprocessor. The VFP-lite can handle both single and double precision arithmetic, as well as properly handling exceptions and subnormal numbers. However, Due to the full spec compliance and presence of the NEON, it is a relatively slow implementation in the A8, usually taking between 18 - 21 cycles to perform a single precision multiply accumulate. The NEON unit on the other hand is designed for very fast single precision vector math, it can sustain multiply accumulates at a rate of two per cycle. Efficiently utilizing these coprocessors in GCC will be the focus of this article.<br />
<br />
'''Note:''' In this article I refer to the A8's integer pipeline as the "ARM" , the VFP-lite as simply the "VFP" and the NEON unit as the "NFP".<br />
<br />
== Compiler Support ==<br />
The NEON + VFP-lite is a new design from ARM and hence does not yet have very mature compiler support. At present the Code Sourcery toolchain has the best support since the mainline GCCs do not support NEON yet. Code Sourcery Compiler versions:<br />
* CSL 2007q3: Working NEON, Softfp Support<br />
* CSL 2008q3: Broken NEON!<br />
* CSL 2009q1: Working NEON, Hardfp + Softfp Support<br />
<br />
Generally the CS2007q3 release is recommended, the CSL 2009q1 release is promising but it has not been thoroughly tested yet. One big problem with the current compilers is the heavy dependence on VFP code, currently they only output NEON code when an obvious chance of vectorization is encountered (rarely). Apart from the esoteric rounding, vector, etc modes of the VFP (most of which compilers don't use) and predication (used occasionally), most VFP floating point instructions can be exactly replicated using an order of magnitude faster NEON instructions.... Infact it has been reported to me that the GCC packaged with the iPhone 3GS SDK does exactly this. Hopefully future compilers will support this feature. <br />
<br />
Inorder to instruct the compiler to produce NEON or VFP code you should use the following compile flags: -mfpu=neon or -mfpu=vfp. Unfortunately the CSL 2007 / 2008 toolchains do not support the passing of values in floating point registers (i talk about this some more in the Transfers section), so you must specify a software ABI via -mfloat-abi=softfp. The CSL 2009q1 release is the first release to support the passing of values in FP registers (AKA hardfp) via the -mfloat-abi=hard compile flag. Note that hardfp compiled binaries are not compatible with softfp ones and vice versa, so make sure your libraries have the correct ABI. Additionally, If you want the compiler to attempt to vectorize your integer / floating point code for the NEON you should add: -ftree-vectorize to your flags. <br />
<br />
Therefore i recommend the following flags: '''-O3 -mcpu=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=(softfp|hard) -ffast-math -fsingle-precision-constant''' where -mfloat-abi=hard for the CSL 2009q1 release and softfp for all the others.<br />
<br />
== VFP-Lite RunFast ==<br />
Under the correct circumstances some of The VFPs instructions will be executed in the NEON coprocessor. Unfortunately this does not gain the full benefit of the NEON, it still takes 7 cycles for an FMAC / FMUL / FADD. Due to this quirk you will likely get better scalar performance by accessing the NEON directly via Intrinsics or ASM.<br />
<br />
Inorder for VFP instructions to execute in the NFP the following constraints must be met:<br />
* RunFast mode must be enabled<br />
* Must be single precision floating point operands<br />
* Must not be a vector instruction (GCC doesn't appear to use this feature, so don't worry about it)<br />
<br />
Runfast mode is enabled when the following conditions are present:<br />
* Subnormal numbers are being flushed to zero <br />
* Default NaN mode is active<br />
* No floating point exceptions are enabled<br />
<br />
I'm not sure if Runfast mode will be enabled by default in the Angstrom distribution packaged with the Pandora. If it isn't you can use the following C code to enforce it:<br />
<br />
<source lang="c"><br />
void enable_runfast()<br />
{<br />
static const unsigned int x = 0x04086060;<br />
static const unsigned int y = 0x03000000;<br />
int r;<br />
asm volatile (<br />
"fmrx %0, fpscr \n\t" //r0 = FPSCR<br />
"and %0, %0, %1 \n\t" //r0 = r0 & 0x04086060<br />
"orr %0, %0, %2 \n\t" //r0 = r0 | 0x03000000<br />
"fmxr fpscr, %0 \n\t" //FPSCR = r0<br />
: "=r"(r)<br />
: "r"(x), "r"(y)<br />
);<br />
}</source><br />
<br />
The instructions that are executed on the NFP are: FADDS, FSUBS, FABSS, FNEGS, FMULS, FNMULS, FMACS, FNMACS, FMSCS, FNMSCS, FCMPS, FCMPES, FCMPZS, FCMPEZS, FUITOS, FSITOS, FTOUIS, FTOSIS, FTOUIZS, FTOSIZS, FSHTOS, FSLTOS, FUHTOS, FULTOS, FTOSHS, FTOSLS, FTOUHS, FTOULS.<br />
<br />
== Single Precision Floating Point ==<br />
One important and easy optimization is to make sure that single precision constants are being used. By default this is not the case, instead a double precision constant is being used, so all related operations involving that constant require slower double precision instructions and cannot be executed on the NEON. eg<br />
<br />
<source lang="c"><br />
float foo(float x)<br />
{ <br />
return (2.123 * x); <br />
}</source><br />
<br />
might end up the same as:<br />
<br />
<source lang="c"><br />
float foo(float x)<br />
{<br />
double dx = (double) x;<br />
double dy = (double) 2.123; <br />
double dr = dx * dy;<br />
float r = (float) dr;<br />
return r;<br />
}</source><br />
<br />
You can enforce single precision constants by including the compiler flag: '''-fsingle-precision-constant''', alternatively you can append an 'f' to the end of each constant. ie 2.123f<br />
<br />
Another thing to watch out for is the double versions of the functions in libm (sin, exp, sqrt, etc). By default these functions operate on double precision floating point values and suffer the same problems as the constants. Luckily libm supplies floating point versions aswell, they can be accessed by appending an 'f' to the end of the function. ie sinf(), expf(), sqrtf().<br />
<br />
== NFP / VFP to ARM Transfers ==<br />
Probably the biggest bottleneck in the architecture is that inorder to transfer a number from the VFP / NFP registers onto the ARM you must stall both the ARM and NFP / VFP for >20 cycles. This is particularly troublesome because this is how GCC (except the CSL 2009q1 release) supplies arguments and recieves returns from functions. Possibly The best way to minimize operand passing stalls is to make the floating point functions inline.<br />
<br />
Another source of NFP / VFP to ARM transfers are conditional branches that depend on floating point numbers. You can do the condition on the VFP but inorder to branch the flags must be sent from the VFP to the ARM. For very simple branches your best bet is to not branch at all and instead use arithmetic. ie<br />
<source lang="c">if (x < 0) {x += 1.1244;}</source><br />
Is the same as:<br />
<source lang="c">x = x + (x < 0) * 1.1244</source><br />
However you might want to keep a close eye on what the compiler actually produces with the above code. <br />
<br />
One interesting fact is that using stores and loads do not cause a stall. So aslong as you don't need the result straight away you can hide the 20 cycle latency. Instead of doing a transfer you; store your NFP / VFP result to memory, do some work on the ARM, then load the result back onto the ARM without penalty. ie<br />
<source lang="c">void foo(float *x, float *r)<br />
{<br />
*r = 123 + *x;<br />
}<br />
<br />
void bar(float *x, float *r)<br />
{<br />
*r = 546 + *x;<br />
}<br />
<br />
void main()<br />
{<br />
float x = 10;<br />
float y, z;<br />
foo(&x, &y)<br />
<br />
//do ~20 cycles of ARM work<br />
<br />
bar(&y, &z);<br />
<br />
}</source><br />
<br />
The last common source of transfers is when you cast a floating point value as an integer, by default all integer work will be done in the ARM pipeline and hence a transfer operation occurs. This is particularly problematic for complex algorithms that rely on bitwise or rounding operations on floating point numbers, ie almost all the functions in cmath depend on range reduction (rounding). A smart compiler would recognize that they can almost always be done in the NEON's integer pipeline.<br />
<br />
== NEON SIMD ==<br />
The NEON unit is similar to the MMX and SSE extensions found on X86 processors, it is optimized for Single Instruction Multiple Data (SIMD) operations.<br />
The NEON unit has 2 floating point pipelines, an integer pipeline and a 128bit load/store/permute pipeline. When properly utilized it is a very powerful coprocessor. Unfortunately GCC does a rather poor job of vectorizing code for the NEON unit. To get the best performance you should use either the intrinsics provided in the "arm_neon.h" header or hand written assembly. <br />
<br />
== Summary ==<br />
It's often said amongst software developers that you 'may aswell not bother trying to out perform a compiler', whilst there is a grain of truth in this where X86 is concerned, this is definitely not the case with Floating point on the ARM Cortex A8. Infact it is almost the opposite, you can almost always make significant gains via targeting the NEON. Therefore, Inorder to achieve the best floating point performance on the Pandora (or ARM Cortex A8 device):<br />
* Use the CodeSourcery 2007q3 or 2009q1 releases and these flags: -O3 -mcpu=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=(softfp|hard) -ffast-math -fsingle-precision-constant<br />
* Only use single precision floating point<br />
* Use NEON intrinsics / ASM when ever you find a bottlenecking FP function. You can do better than the compiler.<br />
* Minimize Conditional Branches<br />
* Enable RunFast mode<br />
<br />
For softfp:<br />
* Inline floating point code (unless its very large)<br />
* Pass FP arguments via pointers instead of by value and do integer work in between function calls.<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Combining_OpenGL_ES_1.1_and_SDL_to_create_a_window_on_the_Pandora&diff=1997Combining OpenGL ES 1.1 and SDL to create a window on the Pandora2010-01-10T20:41:44Z<p>Glenn: + Category:Software</p>
<hr />
<div>There is a special SDL source code for pandora with OpenGL ES capability <br />
available here : http://github.com/Cpasjuste<br />
<br />
The screen initialisation is now easy as this : SDL_SetVideoMode(800, 480, 16, SDL_OPENGLES)<br />
<br />
An SDL/GLES exemple is also available on the git repository.<br />
<br />
[[Category:Software]]</div>Glennhttps://pandorawiki.org/index.php?title=Games&diff=1988Games2010-01-10T20:36:21Z<p>Glenn: + Category:Software</p>
<hr />
<div>Completed games go here.<br />
<br />
For unreleased games under development, see the [[Projects_Under_Development#Games|Projects Under Development page]].<br />
<br />
The games listed below are listed as completed build on the Under Development page.<br />
<br />
BattleJewels by Skeezix<br />
<br />
uHexen2: Hammer of Thyrion by Adventus<br />
<br />
Zdoom by Adventus<br />
<br />
Please note that production of these games will go much faster once the actual product is released, as right now only minimal testing is available for those that do not have dev boards. Also, many listed on the Under Development page list working builds, but are not listed here as they are not yet listed as complete.<br />
<br />
[[Category:Software]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Software&diff=1987Category:Software2010-01-10T20:35:58Z<p>Glenn: new</p>
<hr />
<div>[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Emulator_Compatibility&diff=1986Category:Emulator Compatibility2010-01-10T20:32:12Z<p>Glenn: catspec</p>
<hr />
<div>A category for all the emulator compatibility pages.<br />
<br />
[[Category:Emulators]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Emulators&diff=1985Category:Emulators2010-01-10T20:31:22Z<p>Glenn: + Category:Developer</p>
<hr />
<div>Pages about emulators.<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Software_projects&diff=1982Software projects2010-01-10T20:28:04Z<p>Glenn: + Category:Development</p>
<hr />
<div>See the [[Port Requests]] article for open-source projects which ''could'' be ported but have not been taken on by anyone yet.<br />
<br />
== Operating Systems ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Android Omap<br />
|[http://elinux.org/Android_on_OMAP Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|Angstrom Linux<br />
|[http://www.angstrom-distribution.org/ Link]<br />
|Working build, not completed<br />
|<br />
|<br />
|-<br />
|AROS Arm<br />
|[http://projects.powerdeveloper.org/project/imx515/735 Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|FreeBSD<br />
|[http://wiki.freebsd.org/FreeBSD/arm/OMAP Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|Fedora ARM<br />
|[http://fedoraproject.org/wiki/Architectures/ARM Link]<br />
|wip<br />
|<br />
|<br />
|<br />
|-<br />
|Gentoo Linux<br />
|[http://gentoo.openpandora.org Link]<br />
|Working build, not completed<br />
|javaJake, Viridior<br />
|IRC: (FreeNode) #gentoo-pandora<br />
|-<br />
|HaikuOS<br />
|[http://www.haiku-os.org Link]<br />
|wip<br />
|<br />
|<br />
|-<br />
|RISC OS<br />
|[http://www.riscosopen.org Link]<br />
|wip<br />
|Uwe Kall, Jeffrey Lee<br />
|BeagleBoard port available for download and testing<br />
|-<br />
|Ubuntu ARM<br />
|[http://www.ubuntu.com/products/whatisubuntu/arm Link]<br />
|wip<br />
|<br />
|}<br />
<br />
== Games ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Abuse<br />
|[http://abuse.zoy.org/ Link]<br />
|working build<br />
|Cpasjuste<br />
|2D Platform<br />
|-<br />
|Aleph One<br />
|[http://www.youtube.com/watch?v=1zQ7Fbwhb5I/ Link]<br />
|WIP<br />
|Pickle<br />
|FPS<br />
|-<br />
|Battle for Wesnoth v1.6.2<br />
|[http://www.gp32x.com/board/index.php?showtopic=47936 Link]<br />
|working build<br />
|Cpasjuste<br />
|Strategy<br />
|-<br />
|BattleJewels<br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Skeezix<br />
|Logical<br />
|-<br />
|BlobWars<br />
|[http://www.parallelrealities.co.uk/projects/blobWars.php Link]<br />
|working build<br />
|Cpasjuste<br />
|2D Platform<br />
|-<br />
|Caster<br />
|[http://www.gp32x.com/board/index.php?showtopic=46813 Link]<br />
|Working build (tested on PC)<br />
|Svartalf<br />
|RPG<br />
|- <br />
|CDogs<br />
|<br />
|WIP<br />
|Pickle<br />
|Top down Shooter<br />
|-<br />
|Chaotic Vortex<br />
|[http://www.gp32x.com/board/index.php?/topic/49754-chaotic-vortex-dual-stick-arena-shooter Link]<br />
|WIP<br />
|Ruben<br />
|Dual stick 2D shooter<br />
|-<br />
|Descent 1 (d1x-rebirth engine)<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1032 Link]<br />
|Working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Descent 2 (d2x-rebirth engine)<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1032 Link]<br />
|Working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Eternity 6: The Waterphoenix<br />
|[http://www.gp32x.com/board/index.php?/topic/50772-eternity-6-the-waterphoenix/ Link]<br />
|WIP<br />
|Darien<br />
|Side Scroller / Beat 'Em Up<br />
|-<br />
|FHeroes Port (Heroes Of Might And Magic 2)<br />
|[http://www.gp32x.com/board/index.php?showtopic=47553 Link]<br />
|Working build<br />
|Pickle<br />
|Strategy<br />
|-<br />
|FreeCiv 2.1.9<br />
|[http://freeciv.wikia.com/wiki/Main_Page Link]<br />
|Working build<br />
|Cpasjuste<br />
|Strategy<br />
|-<br />
|Galactic Artifact<br />
|[http://www.gp32x.com/board/index.php?showtopic=46836 Link]<br />
|Working build<br />
|Trevor Bradley<br />
|Strategy<br />
|-<br />
|GemRB (Infinity Engine)<br />
|<br />
|wip<br />
|Adventus<br />
|open-source implementation of Bioware's Infinity Engine, supports games including Baldurs Gate 2 and Planescape Torment.<br />
|-<br />
|Giannas Return<br />
|[http://www.gianas-return.de/ Link]<br />
|Working<br />
|Giannas Team<br />
|Arcade<br />
|-<br />
|Gravity Blocks<br />
|[http://www.gp32x.com/board/index.php?showtopic=47662 Link]<br />
|wip (early in developement)<br />
|Awekening<br />
|Arcade<br />
|-<br />
|Homeworld Port<br />
|[http://www.gp32x.com/board/index.php?showtopic=47565 Link]<br />
|wip<br />
|LinuxHacker<br />
|Simulation<br />
|-<br />
|Human Condition (was TINCS)<br />
|[http://www.gp32x.com/board/index.php?showtopic=46487 Link1][http://www.youtube.com/user/ButtermanHimself Link2]<br />
|wip<br />
|Butterman<br />
|FPP<br />
|-<br />
|Lerp<br />
|[http://grapefruitopia.com/lerp/ Link]<br />
|working build<br />
|benjymous<br />
|2D physics puzzle platformer<br />
|-<br />
|Lord of the Rings Port<br />
|[http://www.gp32x.com/board/index.php?showtopic=46792&hl= Link]<br />
|Unknown<br />
|Daeglin<br />
|RPG<br />
|-<br />
|Mental<br />
|<br />
|Working build, tested on PC<br />
|Colin Jones (xentalion)<br />
|2D Horror Survival Adventure<br />
|-<br />
|Monster!<br />
|[http://christophsdevblog.blogspot.com/ Link]<br />
|wip<br />
|Chris R<br />
|Arcade<br />
|- <br />
|Ms Driller<br />
|<br />
|WIP<br />
|Wally<br />
|Arcade<br />
|-<br />
|NAEV<br />
|[http://code.google.com/p/naev/ Link]<br />
|wip (waiting for pandora to finish and test)<br />
|bobbens<br />
|Action/RPG/Sim<br />
|-<br />
|Nails Adventure<br />
|[http://www.gp32x.com/board/index.php?showtopic=46961 Link]<br />
|wip<br />
|jsmtux/Mr. Gonzo<br />
|<br />
|-<br />
|OpenLiero (Liero)<br />
|<br />
|working build, need to be polished<br />
|Pickle<br />
|Shoot'Em Up<br />
|-<br />
|OpenTyrian<br />
|[http://code.google.com/p/opentyrian/ Link]<br />
|working build<br />
|Cpasjuste<br />
|Shoot'Em Up<br />
|-<br />
|Pandora Panic!<br />
|[http://www.youtube.com/watch?v=y9d6UXhQP6o Link]<br />
|Working build<br />
|PokeParadox / GP32X Community<br />
|Arcade<br />
|-<br />
|Pandora Pool Panic<br />
|[http://www.gp32x.com/board/index.php?showtopic=46996 Link]<br />
|Almost Finished<br />
|Unfathomable Depths<br />
|Arcade<br />
|-<br />
|PanMMO - Pandora MMO Game via Internet<br />
|[http://www.youtube.com/user/enirya Link]<br />
|wip<br />
|Enirya<br />
|RPG<br />
|-<br />
|PanDjoust<br />
|[http://www.gp32x.com/board/index.php?/topic/51192-pandjoust-a-new-simple-platformer/ Link]<br />
|Early Stages<br />
|MarkoeZ<br />
|Platformer<br />
|-<br />
|Powermanga<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|Quake 1<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Quake 2<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Quake 3<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|FPP<br />
|-<br />
|Quake 3<br />
|<br />
|working build<br />
|Pickle<br />
|FPP<br />
|-<br />
|Reminiscence (flashback)<br />
|[http://cyxdown.free.fr/reminiscence/ Link]<br />
|working build<br />
|Cpasjuste<br />
|Action/Adventure<br />
|-<br />
|Rise of The Triad<br />
|[http://www.gp32x.com/board/index.php?showtopic=47931 Link]<br />
|wip<br />
|arrrgh<br />
|FPS<br />
|-<br />
|Slitherlink<br />
|[http://www.gp32x.com/board/index.php?/topic/50756-slitherlink/ Link]<br />
|WIP<br />
|Mia<br />
|Puzzle<br />
|-<br />
|Super Lumenal<br />
|[http://www.youtube.com/watch?v=sZHi3YT3xuE&feature=channel_page Link]<br />
|wip<br />
|Adventus<br />
|Arcade<br />
|-<br />
|SuperTux 1<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1040 Link]<br />
|working build<br />
|Pickle<br />
|Platform<br />
|-<br />
|SuperTux 2<br />
|[http://forum.openhandhelds.org/viewtopic.php?f=6&t=1040 Link]<br />
|working build<br />
|Pickle<br />
|Platform<br />
|-<br />
|Tecnoballz<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|Working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|Teeworlds<br />
|[http://www.teeworlds.com/ Link]<br />
|wip<br />
|<br />
|Arcade<br />
|-<br />
|The Mana World<br />
|[http://www.themanaworld.org/ Link]<br />
|Working build<br />
|Cpasjuste<br />
|MMORPG<br />
|-<br />
|uHexen2: Hammer of Thyrion <br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Adventus<br />
|FPP<br />
|-<br />
|Ur-Quan Masters<br />
|[http://www.gp32x.com/board/index.php?showtopic=43625&st=165&p=673047&#entry673047 Link]<br />
|Working build<br />
|<br />
|Space Exploration<br />
|-<br />
|Warioland-inspired game<br />
|[http://www.gp32x.com/board/index.php?/topic/48680-warioland-inspired-game/ Link]<br />
|wip<br />
|foxblock<br />
|Platformer<br />
|-<br />
|We Come In Peace<br />
|[http://www.gp32x.com/board/index.php?showtopic=43655 Link]<br />
|working build<br />
|Otaco<br />
|Strategy<br />
|-<br />
|Where in world is...<br />
|[http://www.openpandora.pl Link]<br />
|Wip<br />
|StreaK<br />
|Casual<br />
|-<br />
|Wizzley Presto and the Mysterious Time Machine<br />
|[http://www.30daygame.com/ Link]<br />
|wip<br />
|Craigix, Zodttd, Ruckage<br />
|Arcade, 30 Day Game Competition<br />
|-<br />
|Wolf4SDL (Wolfenstein 3D)<br />
|<br />
|working build<br />
|Pickle<br />
|FPS<br />
|-<br />
|Wandor<br />
|[http://www.gp32x.com/board/index.php?/topic/48680-wandor-working-title/ Link]<br />
|WIP<br />
|foxblock<br />
|Side Scroller<br />
|-<br />
|XSwing Plus<br />
|[http://www.gp32x.com/board/index.php?s=&showtopic=43655&view=findpost&p=733021 Link]<br />
|wip<br />
|Tobse<br />
|Arcade<br />
|-<br />
|ZEQ2Lite<br />
|[http://www.gp32x.com/board/index.php?showtopic=47623&hl= Link]<br />
|Work in progress<br />
|MDave<br />
|Dragonball Z Third Person Fighter/Shooter<br />
|-<br />
|Zdoom <br />
|<br />
|Completed build for GP2X, WIP for Pandora<br />
|Adventus<br />
|FPP<br />
|-<br />
|Zombd<br />
|[http://www.gp32x.com/board/index.php?showtopic=46933 Link]<br />
|Wip<br />
|iprice/Mr Gonzo<br />
|Shoot'Em Up<br />
|}<br />
<br />
== Emulators ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Emulated System<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|Caprice32<br />
|Amstrad CPC<br />
|[http://www.gp32x.com/board/index.php?showtopic=48140 Link1] [http://www.caprice32.cybercube.com/ Link2]<br />
|wip<br />
|hdonk<br />
|<br />
|-<br />
|DosBox<br />
|x86 DOS<br />
|<br />
|working build<br />
|Pickle<br />
|<br />
|-<br />
|FinalBurnAdvance<br />
|CPS1/2/3/taito...<br />
|[http://www.youtube.com/watch?v=06hjDLMBaf8 Link]<br />
|<br />
|Squidge<br />
|<br />
|-<br />
|Frotz<br />
|Z-Machine interpreter<br />
|[http://www.cosam.org/computers/pandora/frotz-2.43.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|Fuse<br />
|ZX Spectrum<br />
|[http://www.cosam.org/computers/pandora/fuse-0.9.0.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|GnGeo<br />
|SNK NeoGeo<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|gpSP<br />
|Nintendo GBA<br />
|<br />
|wip<br />
|ZodTTD<br />
|<br />
|-<br />
|Hatari<br />
|Atari ST<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|Jzintv<br />
|Mattel Intellivision<br />
|[http://www.gp32x.com/board/index.php?showtopic=48035 Link]<br />
|<br />
|WizardStan<br />
|<br />
|-<br />
|[[MAME4ALL]]<br />
|Arcade<br />
|[http://www.youtube.com/user/franxism Link]<br />
|<br />
|Franxis<br />
|<br />
|-<br />
|Mupen64plus<br />
|Nintendo 64<br />
|[http://www.gp32x.com/board/index.php?/topic/49358-mupen64plus/ Link]<br />
|working build<br />
|Ari64<br />
|Adventus ported graphics plugin<br />
|-<br />
|NeoPop<br />
|SNK NeoGeo Pocket<br />
|[http://mydedibox.fr/_stuff/pandora/ Link1] [http://www.youtube.com/user/cpasjuste Link2]<br />
|<br />
|Cpasjuste<br />
|<br />
|-<br />
|NullDC<br />
|Sega Dreamcast<br />
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910 Link]<br />
|Wip<br />
|Zezu / drkIIraziel<br />
|<br />
|-<br />
|PandaSNES<br />
|Nintendo SNES<br />
|[http://www.gp32x.com/board/index.php?showtopic=43213 Link]<br />
|wip<br />
|Squidge<br />
|<br />
|-<br />
|Pandora-PSP<br />
|Sony Playstation Portable<br />
|[http://jayfoxrox.bplaced.net/pandora-psp/ Link]<br />
|wip<br />
|[[User:JayFoxRox|JayFoxRox]]<br />
|<br />
|-<br />
|PAtari<br />
|Atari 800<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|PicoDrive<br />
|Sega Genesis/CD/32x<br />
|[http://www.youtube.com/watch?v=QDbLQI91510 Link]<br />
|working build<br />
|Notaz<br />
|Fullspeed emulator<br />
|-<br />
|PSMS<br />
|Sega Master System<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|PSnes<br />
|Nintendo SNES<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|working build<br />
|Cpasjuste<br />
|<br />
|-<br />
|[[PSX4Pandora]]<br />
|Sony PlayStation<br />
|[http://www.zodttd.com Link]<br />
|Not Status, working build<br />
|ZodTTD<br />
|<br />
|-<br />
|ScummVM<br />
|x86 Scumm engine games<br />
|<br />
|Working build<br />
|DJ Willis<br />
|Fullspeed emulator<br />
|-<br />
|SIMH<br />
|old hardware<br />
|[http://www.cosam.org/computers/pandora/simh-3.8.zip Link]<br />
|working build<br />
|SteveM<br />
|<br />
|-<br />
|Temper<br />
|NEC PC Engine<br />
|[http://exophase.devzero.co.uk/ Link]<br />
|wip<br />
|Exophase<br />
|Fullspeed emulator<br />
|-<br />
|Tempest<br />
|Atari Jaguar<br />
|[http://www.gp32x.com/board/index.php?showtopic=43119 Link]<br />
|<br />
|Firefox<br />
|<br />
|-<br />
|[[UAE4ALL]]<br />
|Amiga<br />
|[http://www.gp32x.com/board/index.php?showtopic=44100 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|XMAME<br />
|Arcade<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|<br />
|Cpasjuste<br />
|<br />
|}<br />
<br />
== Graphic Engines ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|GLES2D<br />
|<br />
|Wip<br />
|Cpasjuste<br />
|OpenGL ES 2D library<br />
|-<br />
|GL-WES-v2.0<br />
|[http://code.google.com/p/gl-wes-v2/ link] <br />
|Working Build<br />
|Adventus<br />
|Opensource OpenGL 2.0 driver built on OpenGL ES 2.0.<br />
|-<br />
|Irrlicht<br />
|[http://irrlicht.sourceforge.net/] [http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=32538&start=45]<br />
|working build<br />
|Hybrid<br />
|3D game engine<br />
|-<br />
|NSS Engine<br />
|[http://www.nosiestastudios.com/wiki/ Link1] [http://www.youtube.com/user/Prompt84 Link2]<br />
|<br />
|No Siesta Studios<br />
|<br />
|-<br />
|OGRE Engine<br />
|[http://www.gp32x.com/board/index.php?showtopic=46706 Link1] [http://www.youtube.com/watch?v=LDtUE5PIhV0 Link2]<br />
|<br />
|<br />
|3D real-time renderer<br />
|-<br />
|Otaco Glost Engine<br />
|[http://www.youtube.com/user/otacogloost Link1], [http://www.gp32x.com/board/index.php?/topic/48393-i-did-stuff/page__p__736650&#entry736650 Link2]<br />
|working<br />
|Otaco<br />
|<br />
|-<br />
|Quad-Ren 2D<br />
|[http://quad-ren.sourceforge.net/index.php Link]<br />
|Working<br />
|Hessiess<br />
|Version 0.5 <br />
|-<br />
|SDL GLES<br />
|[http://github.com/Cpasjuste/sdl-1.2.13_gles/tree Link]<br />
|working<br />
|Cpasjuste<br />
|<br />
|-<br />
|XreaL<br />
|[http://xreal.sourceforge.net/xrealwiki/ Link]<br />
|<br />
|Pickle [?]<br />
|<br />
|-<br />
|Stratagus<br />
|[http://stratagus.sourceforge.net/ Link]<br />
|working build<br />
|Cpasjuste<br />
|RTS Engine<br />
|}<br />
<br />
== Other programs ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|AbiWord - Word Processor<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|Claws Mail<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|Epiphany Web Bowser<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|FireFox - Internet Browser<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GIMP - Image Editor<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GMenu<br />
|[http://www.youtube.com/watch?v=VYzi8gziC7E Link]<br />
|Working build<br />
|Pandora Team<br />
|<br />
|-<br />
|Gnumeric Spreadsheet - Spreadsheet<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|for Angstrom OpenPandora<br />
|-<br />
|GoView<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Image Gallery<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Inside The Box<br />
|[http://www.openpandora.pl Link1] [http://www.youtube.com/watch?v=uLMmJBDEs2E Link2]<br />
|wip<br />
|StreaK<br />
|Pandora e-zine<br />
|-<br />
|IRC Client<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|LeafPad<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|Matchbox Shell / GUI<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|MPlayer<br />
|[http://www.gp32x.com/board/index.php?showtopic=41420 Link1] [http://www.youtube.com/watch?v=v9RAPNa-55k Link2]<br />
|Working build<br />
|Squidge<br />
|<br />
|-<br />
|Math-NEON<br />
|[http://code.google.com/p/math-neon/ Link1]<br />
|Wip<br />
|Adventus<br />
|cmath like library optimised for ARM NEON coprocessor.<br />
|-<br />
|Pandaphone<br />
|[http://www.gp32x.com/board/index.php?/topic/48327-pandaphone/ Link]<br />
|<br />
|jb0yx<br />
|A project to incorporate the Open Pandora handheld device with cell phone technology<br />
|-<br />
|Pandora Sync Suite<br />
|[http://www.openpandora.pl Link]<br />
|Working build<br />
|StreaK<br />
|for Windows 9x/NT<br />
|-<br />
|Pangea GUI<br />
|[http://www.gp32x.com/board/index.php?showtopic=45631&hl=pangea Link]<br />
|WIP<br />
|efegea<br />
|Gmenu alternative<br />
|-<br />
|Panorama<br />
|[http://www.gp32x.com/board/index.php?/topic/51076-panorama/ Link]<br />
|WIP<br />
|dflemstr<br />
|Gmenu alternative<br />
|-<br />
|PDM<br />
|[http://github.com/Cpasjuste/pdm/tree Link]<br />
|<br />
|Cpasjuste<br />
|Light desktop manager for Pandora<br />
|-<br />
|PGui<br />
|[http://github.com/Cpasjuste/pgui/tree Link]<br />
|<br />
|Cpasjuste<br />
|Standard emulator fronted for Pandora<br />
|-<br />
|Pidgin - IM (for Angstrom OpenPandora)<br />
|[http://www.youtube.com/watch?v=oYf-I1UuWhk Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|PMenu<br />
|[http://mydedibox.fr/_stuff/pandora/ Link]<br />
|<br />
|Cpasjuste<br />
|Minimal Menu for Pandora<br />
|-<br />
|PND Maker (for Windows 9x/NT)<br />
|[http://www.openpandora.pl Link]<br />
|Working build<br />
|StreaK<br />
|<br />
|-<br />
|Qemu<br />
|[http://www.nongnu.org/qemu/status.html Link]<br />
|testing build<br />
|Fabrice Bellard<br />
|open source machine emulator and virtualizer<br />
|-<br />
|Scale<br />
|[http://www.youtube.com/user/Zoxc64 Link]<br />
|wip<br />
|Zoxc64<br />
|Minimal Menu for Pandora<br />
|-<br />
|Simple Dev Studio for Pandora<br />
|[http://www.openpandora.pl Link]<br />
|Wip<br />
|StreaK<br />
|for Windows 9x/NT<br />
|-<br />
|[[TINXL]]<br />
|[[TINXL]]<br />
|<br />
|<br />
|Application stack for multiplayer internet games<br />
|-<br />
|[[TS2A]]<br />
|[[TS2A]]<br />
|Documentation only<br />
||[[User:JayFoxRox|JayFoxRox]]<br />
|Teamspeak 2 Alternative Client / Server, Needs developer<br />
|-<br />
|XMMS<br />
|[http://www.youtube.com/watch?v=sKKMj37Psd8 Link]<br />
|Working build<br />
|<br />
|<br />
|-<br />
|ZiB Emulator Frontend<br />
|[http://www.gp32x.com/board/index.php?showtopic=47203 Link1] [http://www.youtube.com/watch?v=UJvON8lCM3M Link2]<br />
|<br />
|Aimless_E<br />
|<br />
|}<br />
<br />
== Demos / Technical Demos for OpenPandora ==<br />
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec"<br />
! Project Name<br />
! Link<br />
! Status<br />
! Author/Port Author<br />
! Notes<br />
|-<br />
|OpenGL Cell Shading<br />
|[http://www.youtube.com/watch?v=cpAj0jHglGw Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|OpenGL Demo with MP3 Playback<br />
|[http://www.youtube.com/watch?v=hkx18kruRJs Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|OpenGL Skull Demo<br />
|[http://www.youtube.com/watch?v=qG7EDaZpyOo Link]<br />
|working build<br />
|<br />
|<br />
|-<br />
|WaveDemo<br />
|[http://www.youtube.com/watch?v=4wgEHFCq9Lo Link]<br />
|Working<br />
|Otaco<br />
|<br />
|}<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Cross-compiler&diff=1981Cross-compiler2010-01-10T20:27:36Z<p>Glenn: + Category:Development</p>
<hr />
<div>''I'm still sorting this out myself, I'm going to give a short tutorial about compiling something from the Windows command line, the rest will be explained when the Pandora is released''<br />
<br />
What you need: <br />
<br />
- Patience<br />
<br />
<br />
To compile your applications to the ARM architecture you're going to need a cross-compiler. Luckily, Code-Sourcery hosts a bunch of cross-compiling suites for various platforms on their site, some editions have to be paid for, but they do have "lite" editions without support that are completely free.<br />
<br />
Head up onto here, http://www.codesourcery.com/sgpp/lite/arm/releases/2007q3<br />
<br />
You want the "ARM GNU/Linux" option, then choose whichever operating system you're running bellow.<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=Template:Pandora_Hardware&diff=1978Template:Pandora Hardware2010-01-10T20:25:34Z<p>Glenn: catspec Category:Hardware</p>
<hr />
<div>=== 3rd Party Hardware ===<br />
This is a list of hardware that can be used with the Pandora UMPC.<br />
<br />
This page lists the name of a product, the link to the product, miscellaneous notes on it, and then the status.<br />
<br />
The status has a possible 3 colors. (Editors, please copy and paste the styling when creating a new row.)<br />
<br />
{|<br />
|-<br />
| style="background:green;color:white;text-align:center" | Works! with Pandora<br />
| style="background:orange;text-align:center" | Unknown to work<br />
| style="background:red;color:white;text-align:center" | Not compatible with Pandora<br />
|}<br />
<br />
<br />
{|<br />
|- style="background:#000000; color:white"<br />
! Name<br />
! Link<br />
! Notes<br />
! Status<br />
! Source<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Keyboards<br />
|-<br />
| Apple Wireless Bluetooth Keyboard<br />
| http://www.bestbuy.com/site/olspage.jsp?skuId=8509759&st=keyboard&lp=12&type=product&cp=1&id=1186005932539<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|- style="background:#CCCCCC;"<br />
| Adesso Foldable Keyboard<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166038<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| Adesso Mouse/Keyboard Combination<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166052<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| Darfon Foldable Keyboard<br />
| http://www.darfon.com.tw/English/HID_Portable.asp<br />
| Possibly relisted under other manufacturers names<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| DealExtreme Compact 88 key keyboard<br />
| http://www.dealextreme.com/details.dx/sku.11933<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| iGo Stowaway Ultra-Slim Bluetooth Keyboard<br />
| http://www.amazon.com/Stowaway-Ultra-Slim-Bluetooth-Blackberry-Handhelds/dp/B0002OKCXE<br />
| iGo no longer makes them, however many Nokia Internet tablet owners have them.<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Mice<br />
|-<br />
| Adesso Mouse w/ numpad<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166082<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Cases<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Accessories/Misc<br />
|-<br />
| Archos screen protectors<br />
| http://www.zagg.com/invisibleshield/media-player/archos<br />
| Assumed to work due to screen dimensions<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| Mini-Box PicoLCD 4x20 External LCD display<br />
| http://www.mini-box.com/PicoLCD-4X20-Sideshow<br />
| Also works in Windows Vista<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| DealExtreme 58-n-1 card reader<br />
| http://www.dealextreme.com/details.dx/sku.7523<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| DealExtreme clip-on 1.3 MP Webcap<br />
| http://www.dealextreme.com/details.dx/sku.3569<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Game Controllers<br />
|-<br />
| Genius Portable USB Pandora Gamepad<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16826179016<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| NES/SNES to USB Converters and controllers<br />
| http://www.retrousb.com/index.php?categoryID=79<br />
| May be better off buying the controllers (retro) from eBay<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| USB Adapter for all kinds of retro joysticks<br />
| http://www.raphnetshop.com/products/atari2usb/index.php?category=Gaming<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-style="background:#CCCCCC;"<br />
| Logitech Precision<br />
| http://www.logitech.com/index.cfm/gaming/pc_gaming/gamepads/devices/301<br />
|<br />
* Not all the buttons have been tested, but I think we can safely assume they'll work. (When confirmed all work, remove this note)<br />
* Requires USB adapter<br />
| style="background:green;color:white;text-align:center" | Works<br />
| [http://www.youtube.com/watch?v=njgAQhwqJZg Source]<br />
|}<br />
<br />
[[Category:Hardware]]</div>Glennhttps://pandorawiki.org/index.php?title=Hardware_documentation&diff=1977Hardware documentation2010-01-10T20:25:13Z<p>Glenn: catspec Category:Hardware</p>
<hr />
<div>==OMAP3530==<br />
*OMAP35x: Main page on TI site[http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915]<br />
*OMAP3530 specific page[http://focus.ti.com/docs/prod/folders/print/omap3530.html] ''This lists the features of the chip and has all the applicable Technical Documents''<br />
*OMAP35XX technical manual: [http://www.ti.com/litv/pdf/spruf98b] (38MB PDF)<br />
<br />
==C64x+==<br />
*CPU and Instruction Set Reference Guide[http://focus.ti.com/lit/ug/spru732h/spru732h.pdf]<br />
*TMS320C6000 Assembly Language Tools v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru186p]<br />
*TMS320C6000 Optimizing Compiler v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&familyId=44&abstractName=spru187n]<br />
*TMS320C6000 Programmer's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru198i]<br />
<br />
==Cortex-A8==<br />
*r1p1[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344b/DDI0344.pdf] ''Note: OMAP3530 uses r1p2''<br />
*NEON instructions[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204h/Bcfjicfj.html]<br />
*'''UPDATE''': r2p2 Documentation [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344e/index.html] ''Note: OMAP3530 uses r1p2''<br />
*NEON memory hazards[http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/]<br />
<br />
==Screen==<br />
*Screen datasheet (TD043MTEA2)[http://beyondinfinite.com/lcd/Library/Toppoly/TD043MTEA2.pdf]<br />
<br />
==OpenGL ES 2.0==<br />
*Official site[http://khronos.org/opengles/2_X/]<br />
<br />
==Other OMAP3530 Projects==<br />
*Beagle Board Resources[http://beagleboard.org/resources] As it uses the same SoC, many BB resources are also relevant for the Pandora.<br />
*Beagle Board Google Group[http://groups.google.com/group/beagleboard]<br />
<br />
[[Category:Hardware]]</div>Glennhttps://pandorawiki.org/index.php?title=Hardware_hacking&diff=1976Hardware hacking2010-01-10T20:24:30Z<p>Glenn: +cat</p>
<hr />
<div>=Making an RS232 level converter for the Pandora=<br />
How is this done?<br />
<br />
=Pinouts=<br />
==Ext Connector==<br />
''Please add any information you have here''<br />
<br />
''What is the pinout?''<br />
<br />
''Where can we get the connectors from?''<br />
<br />
==Battery==<br />
3.7V <br />
Lithium polymer single cell battery<br />
4000 mAH<br />
4 AH<br />
battery cover here:<br />
[http://www.openpandora.org/images/Battery2.jpg]<br />
<br />
==Internal connections==<br />
''Please add any information you have here''<br />
===LCD===<br />
===UART===<br />
''Does this exist???''<br />
===GPIO===<br />
===Battery===<br />
===JTAG===<br />
<br />
===Keypad backlight===<br />
Maximum current draw?<br />
<br />
==Breakout Board==<br />
[[Image:Breakoutboard.jpg|thumb|alt=Developer's breakout board|Developer's breakout board]]<br />
This is the breakout board used by Pandora team members during development. Only a small number were made, and they are not available to the public. However a similar product (or gerber files) may be released in the future. A schematic for this board is available here: http://openpandora.ca/schematic/AV_Board_schematic.pdf<br />
<br />
[[Category:Hardware]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Hardware&diff=1975Category:Hardware2010-01-10T20:24:12Z<p>Glenn: new</p>
<hr />
<div>[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Special:Badtitle/NS104:FAQ&diff=775Special:Badtitle/NS104:FAQ2008-10-04T11:54:45Z<p>Glenn: +cat</p>
<hr />
<div>==Preguntas==<br />
===¿Qué es Pandora?===<br />
<br />
Es una videoconsola portátil Open-Source con Wifi y Bluetooth.<br />
Características y especificaciones<br />
<br />
===¿Cómo se ha concebido?===<br />
<br />
Pandora es una máquina única. Ha sido diseñada basado en las sugerencias de cientos de usuarios de foros con un único objetivo: crear el dispositivo portátil de código abierto definitivo.<br />
<br />
===¿Cómo es de potente?===<br />
<br />
Es con mucho la consola portátil más potente hasta el momento en términos de proceso de CPU y capacidades gráficas 3D. Sus prestaciones técnicas harán que sea capaz de soportar aplicaciones como Firefox3 o Quake3 con facilidad.<br />
<br />
===¿Dónde y cuándo podré comprarla?===<br />
<br />
Actualmente ya está disponible para desarrolladores seleccionados. Los demás usuarios podrán reservarla desde el 30 de Septiembre. Los envíos empezarán a finales de Noviembre. Se distribuirá desde Inglaterra, USA, Canada, Alemania y Turquía.<br />
<br />
===¿Cuánto costará?===<br />
<br />
Precio final: €250 (impuestos incluidos)<br />
<br />
¿Para qué ha sido diseñado este dispositivo?<br />
<br />
Ha sido diseñado como un ordenador ultra portable de código abierto basado en GNU/Linux con controles de juego. Es muy pequeño, con el tamaño aproximado de una Nintendo DS. Cabe facilmente en tu bolsillo.<br />
<br />
===¿Por qué ese diseño tan radical?===<br />
<br />
El diseño es de tipo concha ya que da una máxima proteccion, comodidad y por supuesto el máximo tamaño de la batería para una mayor autonomía.<br />
<br />
Puedes ver una foto comparativa aquí.<br />
<br />
===Tengo una idea… / ¿Podríais cambiar… ?===<br />
<br />
Entra en los foros oficiales de Pandora (en inglés) y cuenta tu idea.<br />
<br />
Tambien puedes entrar en Pandora Wiki (en inglés) para tener más información. Dicha web no es oficial y por lo tanto los creadores no son responsables de su contenido.<br />
<br />
La página de Pandora Wiki dispone también de un FAQ mucho más completo (en inglés).<br />
<br />
[[Category:FAQ]]</div>Glennhttps://pandorawiki.org/index.php?title=Special:Badtitle/NS104:Acerca_de_Pandora&diff=774Special:Badtitle/NS104:Acerca de Pandora2008-10-04T11:54:13Z<p>Glenn: +Category:Categories</p>
<hr />
<div>[[Image:Pandora-newrender.jpg|Right|thumb|360px|La Pandora]]<br />
<br />
==¿Qué es Pandora?==<br />
<br />
Pandora es una videoconsola portátil “abierta”. Al estar basada en Linux permite a cualquier desarrollador programar sus aplicaciones y juegos para esta plataforma. Su apariencia y tamaño son similares al de una Nintendo DS.<br />
<br />
Características destacadas:<br />
<br />
* Pantalla táctil panorámica de 4,3 pulgadas<br />
* Dos slots para tarjetas de memoria de hasta 64 Gb<br />
* Controles de juego completos,<br /> incluyendo dos controladores analógicos<br />
* Teclado QWERTY integrado con teclas de función<br />
* Conectividad: Wifi, Bluetooth, USB 2.0<br />
* Aceleración 3D<br />
* Duración de la batería en torno a 10 horas<br />
<br />
Especificaciones:<br />
<br />
* Procesador Texas Instruments OMAP3530 a 625MHz, con núcleo ARM® Cortex™-A8<br />
* 128 Mb de memoria SDRAM DDR-333<br />
* 256 Mb de memoria FLASH NAND para almacenamiento interno.<br />
* Procesador de audio y video IVA2+ con tecnología DaVinci™ de Texas Instruments<br />
* Aceleración 3D por hardware PowerVR SGX compatible con OpenGL ES 2.0<br />
* Conexión inalámbrica Wifi 802.11b/g integrada<br />
* Bluetooth 2.0 + ERD integrado (3Mbps)<br />
* Pantalla táctil LCD 800×480, panorámica 4.3″, 16.7 millones de colores, brillo 300 cd/m2, contraste 450:1<br />
* Controles de juego: cruceta, 2 analógicos, 4 botones y 2 botones “gatillo”<br />
* Dos slots para tarjetas de memoria SDHC, hasta 64 Gb de capacidad<br />
* Salida de audio para auriculares hasta 150 mW por canal, 16 ohms, 99dB SNR<br />
* Salida de TV independiente (S-Video y video compuesto)<br />
* Micrófono incorporado. Posibilidad de conectar micrófono externo desde auriculares<br />
* Teclado de 43 teclas QWERTY y teclas numéricas<br />
* Puerto USB 2.0 OTG (480 Mb/s) con capacidad para cargar la batería.<br />
* Puerto USB Host 2.0 (480 Mb/s) capaz de proporcionar los 500 mA a los dispositivos conectados.<br />
* UART accesible externamente para depuración y hacking.<br />
* Diseño interno a prueba de fallos con autoarranque integrado para experimentación segura.<br />
* Sistema operativo Linux (2.6.x)<br />
* Dimensiones: 140 x 83 x 27 mm<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Development_tutorials&diff=773Development tutorials2008-10-04T11:53:23Z<p>Glenn: Redirecting to Development Tools</p>
<hr />
<div>#REDIRECT [[Development Tools]]</div>Glennhttps://pandorawiki.org/index.php?title=Development_Tools&diff=772Development Tools2008-10-04T11:52:39Z<p>Glenn: +Category:Development</p>
<hr />
<div>==Tools for Pandora Software Development==<br />
<br />
* CodeSourcery gcc[http://www.codesourcery.com/gnu_toolchains/arm]<br />
* TI CodeComposer Studio: Free Evaluation Tools[http://focus.ti.com/dsp/docs/dspsupportaut.tsp?sectionId=3&tabId=416&familyId=44&toolTypeId=30]<br />
* TI c6x Codegen tools for Linux[https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html]; License [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/doc/c6x/TILAW-%23180394-v1-Compiler_Clickwrap_For_OS_Community-2.html]; TI account required; this is *only* for Open Source development<br />
* OpenGL ES 2.0 emulator for PC[http://www.imgtec.com/powervr/insider/sdkdownloads/index.asp#GLES2] ''This works both on Linux and Windows. One needs to register with imgtec before downloading.''<br />
* Das U-boot: The Universal Bootloader[http://www.denx.de/wiki/DULG/WebHome]<br />
<br />
<br />
[[Category:Development]]</div>Glennhttps://pandorawiki.org/index.php?title=User:Glenn&diff=771User:Glenn2008-10-04T11:34:46Z<p>Glenn: +link</p>
<hr />
<div>*http://da.wikipedia.org/wiki/Bruger:Glenn</div>Glennhttps://pandorawiki.org/index.php?title=Category:Wiki&diff=770Category:Wiki2008-10-04T11:31:00Z<p>Glenn: +cat</p>
<hr />
<div>Pages to do with the running of the wiki.<br />
<br />
[[Category:Community]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Templates&diff=769Category:Templates2008-10-04T11:30:18Z<p>Glenn: +cat</p>
<hr />
<div>Templates used by this wiki.<br />
<br />
[[Category:Community]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Newsletters&diff=767Category:Newsletters2008-10-04T11:29:25Z<p>Glenn: +cat</p>
<hr />
<div>This page serves as an archive for the official OpenPandora newsletters<br />
<br />
[[Category:Community]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:FAQ&diff=766Category:FAQ2008-10-04T11:28:53Z<p>Glenn: +Category:Categories</p>
<hr />
<div>Articles giving general information about the Pandora.<br />
<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Emulators&diff=765Category:Emulators2008-10-04T11:28:30Z<p>Glenn: +Category:Categories</p>
<hr />
<div>Pages about emulators.<br />
<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Emulator_Compatibility&diff=764Category:Emulator Compatibility2008-10-04T11:28:13Z<p>Glenn: +Category:Categories</p>
<hr />
<div>A category for all the emulator compatibility pages.<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Development&diff=763Category:Development2008-10-04T11:27:39Z<p>Glenn: +Category:Categories</p>
<hr />
<div>Articles relating to development.<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Template:Pandora_Hardware&diff=754Template:Pandora Hardware2008-10-04T10:57:25Z<p>Glenn: +Category:Categories</p>
<hr />
<div>=== 3rd Party Hardware ===<br />
This is a list of hardware that can be used with the Pandora UMPC.<br />
<br />
This page lists the name of a product, the link to the product, miscellaneous notes on it, and then the status.<br />
<br />
The status has a possible 3 colors. (Editors, please copy and paste the styling when creating a new row.)<br />
<br />
{|<br />
|-<br />
| style="background:green;color:white;text-align:center" | Works! with Pandora<br />
| style="background:orange;text-align:center" | Unknown to work<br />
| style="background:red;color:white;text-align:center" | Not compatible with Pandora<br />
|}<br />
<br />
<br />
{|<br />
|- style="background:#000000; color:white"<br />
! Name<br />
! Link<br />
! Notes<br />
! Status<br />
! Source<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Keyboards<br />
|-<br />
| Apple Wireless Bluetooth Keyboard<br />
| http://www.bestbuy.com/site/olspage.jsp?skuId=8509759&st=keyboard&lp=12&type=product&cp=1&id=1186005932539<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|- style="background:#CCCCCC;"<br />
| Adesso Foldable Keyboard<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166038<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| Adesso Mouse/Keyboard Combination<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166052<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| Darfon Foldable Keyboard<br />
| http://www.darfon.com.tw/English/HID_Portable.asp<br />
| Possibly relisted under other manufacturers names<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| DealExtreme Compact 88 key keyboard<br />
| http://www.dealextreme.com/details.dx/sku.11933<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| iGo Stowaway Ultra-Slim Bluetooth Keyboard<br />
| http://www.amazon.com/Stowaway-Ultra-Slim-Bluetooth-Blackberry-Handhelds/dp/B0002OKCXE<br />
| iGo no longer makes them, however many Nokia Internet tablet owners have them.<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Mice<br />
|-<br />
| Adesso Mouse w/ numpad<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16823166082<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Cases<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Accessories/Misc<br />
|-<br />
| Archos screen protectors<br />
| http://www.zagg.com/invisibleshield/media-player/archos<br />
| Assumed to work due to screen dimensions<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| Mini-Box PicoLCD 4x20 External LCD display<br />
| http://www.mini-box.com/PicoLCD-4X20-Sideshow<br />
| Also works in Windows Vista<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| DealExtreme 58-n-1 card reader<br />
| http://www.dealextreme.com/details.dx/sku.7523<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| DealExtreme clip-on 1.3 MP Webcap<br />
| http://www.dealextreme.com/details.dx/sku.3569<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
! style="background:#555555; color:white" width="100%" colspan=5 | Game Controllers<br />
|-<br />
| Genius Portable USB Pandora Gamepad<br />
| http://www.newegg.com/Product/Product.aspx?Item=N82E16826179016<br />
| <br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|- style="background:#CCCCCC;"<br />
| NES/SNES to USB Converters and controllers<br />
| http://www.retrousb.com/index.php?categoryID=79<br />
| May be better off buying the controllers (retro) from eBay<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-<br />
| USB Adapter for all kinds of retro joysticks<br />
| http://www.raphnetshop.com/products/atari2usb/index.php?category=Gaming<br />
|<br />
| style="background:orange;text-align:center" | Unknown<br />
|<br />
|-style="background:#CCCCCC;"<br />
| Logitech Precision<br />
| http://www.logitech.com/index.cfm/gaming/pc_gaming/gamepads/devices/301<br />
|<br />
* Not all the buttons have been tested, but I think we can safely assume they'll work. (When confirmed all work, remove this note)<br />
* Requires USB adapter<br />
| style="background:green;color:white;text-align:center" | Works<br />
| [http://www.youtube.com/watch?v=njgAQhwqJZg Source]<br />
|}<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Logo&diff=753Logo2008-10-04T10:57:06Z<p>Glenn: +Category:Categories</p>
<hr />
<div>== High Resolution Logo ==<br />
People keep asking for the logo, so in the interest of helping out, I re-drew the drawing. Here's the logo in PDF (using RGB colors as people are making things for screen use). I didn't have a high resolution copy to work from, so I did my best in the time I had. I do not know what the font is, and craigix has stated he believes it to be drawn.<br />
<br />
* [[Image:Pandora_logo-unofficial.pdf]]<br />
<br />
== Logo Colors ==<br />
<br />
For those doing print or reproducing the logo, the CMYK colors are:<br />
* box logo: 100% cyan, 75% black<br />
* word logo: 100% cyan, 20% black<br />
<br />
== Logo Use ==<br />
<br />
I suspect there are no logo use rules at present, and so I'll just make some general design suggestions. Don't change the spacing between the letters. When presented side-by-side, try not to change the spacing between the box and the word logo. In general, don't overlay the word logo over the box (unless perhaps the box logo is enormous) as the legibility of both would suffer. The logo is best presented in solid colors, and the letters in the word logo should be of the same color. When scaling the logo, preserve the aspect ratio of height to width. (These are merely suggestions of best use, but design is about pushing boundaries, and so some rules can be a bit flexible.)<br />
<br />
I do not know the designer of the logo, and I imagine the logo copyright is owned by OpenPandora. Ask them, or check their web page for rights reserved.<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Hardware_documentation&diff=751Hardware documentation2008-10-04T10:56:22Z<p>Glenn: +Category:Categories</p>
<hr />
<div>===OMAP3530===<br />
*OMAP35x: Main page on TI site[http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915]<br />
*OMAP3530 specific page[http://focus.ti.com/docs/prod/folders/print/omap3530.html] ''This lists the features of the chip and has all the applicable Technical Documents''<br />
*OMAP35XX technical manual: [http://www.ti.com/litv/pdf/spruf98a] (38MB PDF)<br />
<br />
<br />
===C64x+===<br />
*CPU and Instruction Set Reference Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru732g]<br />
*TMS320C6000 Assembly Language Tools v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru186p]<br />
*TMS320C6000 Optimizing Compiler v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&familyId=44&abstractName=spru187n]<br />
*TMS320C6000 Programmer's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru198i]<br />
<br />
<br />
===Cortex-A8===<br />
*r1p1[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344b/DDI0344.pdf] ''Note: OMAP3530 uses r1p2''<br />
*NEON instructions[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204h/Bcfjicfj.html]<br />
<br />
===OpenGL ES 2.0===<br />
*Official site[http://khronos.org/opengles/2_X/]<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Games&diff=750Games2008-10-04T10:56:02Z<p>Glenn: +Category:Categories</p>
<hr />
<div>There are no games yet.<br />
<br />
[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Community&diff=747Category:Community2008-10-04T10:54:40Z<p>Glenn: new</p>
<hr />
<div>[[Category:Categories]]</div>Glennhttps://pandorawiki.org/index.php?title=Category:Categories&diff=745Category:Categories2008-10-04T10:53:20Z<p>Glenn: new</p>
<hr />
<div>.</div>Glennhttps://pandorawiki.org/index.php?title=Category:Wiki&diff=744Category:Wiki2008-10-04T10:53:06Z<p>Glenn: +Category:Categories</p>
<hr />
<div>Pages to do with the running of the wiki.<br />
<br />
[[Category:Categories]]</div>Glenn