All Projects

Found I'd kept some notes about making the Pandora's wake on alarm function work...

drivers/rtc/rtc-twl4030.c

twl4030_rtc_remove (for when the driver is removed) and twl4030_rtc_
shutdown (for when the system is shutdown) functions need to change. Or at least the shut down does.

oh YUK who's been using goto....

changes in drivers/rtc/rtc-twl4030.c

twl4030_rtc_remove
commented out //mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);

twl4030_rtc_shutdown
replaced
// mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M |
// BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);
with
mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M);

twl4030_rtc_suspend
replaced
// mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M |
// BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);
with
mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M);

twl4030_rtc_init
added (before return!)
twl4030_rtc_alarm_irq_set_state(true);

Should probably check reg 0x2B with mask 0x08 to see if alarm should be left enabled or not ?
but only in twl4030_rtc_shutdown and ?remove? NOT in twl4030_rtc_init
should remove ever happen ???

I'm guessing it's best to not enable the alarm irq's all the time???

opengles and op_power.sh don't like each other very much.
whenever returning from low power to full power mode again, opengles rendering is just dead.

the reason for this issue are following 2 lines within op_power.sh

18 echo 0 > /sys/devices/platform/omapfb/graphics/fb0/blank
...
66 echo 1 > /sys/devices/platform/omapfb/graphics/fb0/blank

if these lines are removed/commented, the gles rendering just resumes fine.

Built-in keyboard input is a central thing on the Pandora, as it concerns almost all user interfaced apps!
I realized that I myself and also others submitted quite many reports concerning this issue.
Hence this meta issue is intended as an overview/accumulation/aid for those devs who are willing to overwork the whole issue.
If you realize new related issues, feel free to add them here.
If this my effort is contradicting the OpenPandora workflow, then pardon me, and instruct me, how else to handle issues of that kind. Thanks!

Keyboard low level: Driver, keyboard layout, post processing (hotkeys, input support, etc)
FS#138 FS#227 FS#242  FS#259 

Keyboard mid level: Application interfacing
 FS#102  FS#123 FS#238

Keyboard application internal level
 FS#157  (dupe:  FS#249 ) FS#243 FS#256

using evdev xorg drivers and not the tslib drivers you can receive pressure axis data however there is
a problem with the values reported by the ads7846 module and the evdev driver has no calibration property for pressure

using
xinput test touchscreen
you can see the pressure axis ranging from 120-ish for hard press to about 150-170 for light press (low pressure values can
be quite erratic)

I could possibly hack the evdev module to possibly do something with this odd and narrow range of values, but I rather think looking
at the source that the ads7846 module needs some work.

is there a git tag that has a known working configuration? as I've had problems getting the kernel to compile the last few times I attempted...

When thee Pandora is shutting down because its almost out of power, it should check to make sure that the nub inputs are set to the default mode (which is mouse movement for the left nub and mouse buttons for the right nub). If not, it should change them to be like that.

FLAWED BEHAVIOUR:

Copy and paste only works between 2 active applications. This is very limiting!
If you are in the single task oriented MiniMenu you have no chance at all to share the clipboard between apps!
If you are in the multi tasking oriented XFCE desktop environment you can only share between apps running in parallel! Not with apps which started after the source app has been terminated.

DESIRED BEHAVIOUR:

The clipboard content (within reasonable limits of course) should remain, regardless of the source application, so that you can paste at any later moment into any application.

When the lid is closed the only remaining buttons on the Pandora are the L + R shoulder buttons and the power slider.
Applications operating in this mode should utilize that few available buttons!

Example for button utilization in a audio playback software:
L + R at once: Toggle Play/Pause
L hold: fast backward
R hold: fast forward
L click: jump to previous song
R click: jump to next song
L double click: jump to previous album/artist
R double click: jump to next album/artist

When a X window which is displaying GLES2 render output is:
- Either dragged out of the visibile screen region (?)
- Is made larger than it was at the creation time of the GLES2 context
then:
- The performance will drop significantly as the EGL buffer swaps won't occur as fast as before,
- The render output will be corrupted and flicker
- In rare occasions crashes the application or locks up the entire system (which forces you to remove the battery)

The problem can not be solved without restarting the application (Possibly forcing players to complete the same goals again as they were unable to reach a savepoint or similar things).

This was confirmed in Mupen64Plus and the PowerVR GLES Samples and some of my own projects (which are, however, based on the PowerVR samples).
As I didn't see any other reports about this problems (but had it confirmed by other Pandora users too) I would expect that it can be fixed by using a newer X, kernel or combination of them as other OMAP users would be effected too.

Trashing a file/folder seems to MOVE it to a certain trash directory on the MAIN VOLUME, rather then the ORIGINATING VOLUME, hence this can result in a COPY RATHER THAN A MOVE operation, if the trashed file originates from a filesystem other than the main filesystem!

This is very inefficient and faulty as it is:
a) Very time consuming
b) And in case of large files this operation can even fail due to not enough free space on the main volume.

Ok, I just want to say that there is something missing about the font on the base image. I cant get what (at least for now)

Here is an issue : http://www.gp32x.com/board/index.php?/topic/54282-getting-vnc-viewer-to-work/

With my current Ogre build I get :
Warning: Unable to load any usable ISO8859 font
Error: Aborting: no font found

I've googled but so far no solution :(

In GTK applications, such as Truecrypt, NoteCase Pro or Mousepad, the file open / file save dialogs have shortcuts to mounted file systems on the left side.
If clicking such a shortcut entry, the corresponding file system's contents are shown in the right dialog pane.
This works for file systems, which were available at boot time.
For file systems mounted after booting, e.g. by inserting an SD card or connecting a USB drive, when clicking such an entry, an error message appears saying
"Could not mount [volumen name]
Failed to execute child process 'gnome-mount' (No such file or directory)"

This is healed by
sudo opkg install gnome-mount
(which instals gnome-mount, nautilus, gvfsd-ftp, gvfs (upgrade), and a lot of libs (upgrades)..

This has been seen in SuperZaxxon release 1.5, not in Beta3 (but Beta3 is the only choice in Flyspray's dropdown currently).

I reported that error for HF6 I think, and it seemed to be fixed in SuperZaxxon Beta5. A regression?

When put into Hold mode, X11 handles the power switch as if it's being pressed, and it generates lots of keypress events, passing them to the foreground application. Since /dev/input/eventX does not seem to continuously trigger, I'm guessing it's due to key repeat.

To reproduce:

• Install xev and open it in the terminal


• Put the power key in HOLD mode


• Notice the "time" value changing rapidly

In addition to causing more work to X, it also floods the active application with key presses, resulting in increased CPU usage. In my test, switching to HOLD while Firefox is in the foreground causes it to use 6% CPU and X an additional 2.5%.

In addition, the key-press events continue even after the switch is taken off HOLD until another key is pressed.

A possible solution to this is to blacklist the power-button event device, to prevent evdev from listening to it (the key is handled by pndevmapperd).

The update mode functions have moved from the DSS layer to omapfb implementaion.
This patch exports the new function symbols for use by the TI drivers.

--- a/drivers/video/omap2/omapfb/omapfb-ioctl.c
+++ b/drivers/video/omap2/omapfb/omapfb-ioctl.c
@@ -22,6 +22,7 @@

#include <linux/fb.h>
#include <linux/device.h>
+#include <linux/module.h>
#include <linux/uaccess.h>
#include <linux/platform_device.h>
#include <linux/mm.h>
@@ -359,6 +360,7 @@ int omapfb_set_update_mode(struct fb_info *fbi,

return r;
}
+EXPORT_SYMBOL(omapfb_set_update_mode);

int omapfb_get_update_mode(struct fb_info *fbi,
enum omapfb_update_mode *mode)
@@ -381,6 +383,7 @@ int omapfb_get_update_mode(struct fb_info *fbi,

return 0;
}
+EXPORT_SYMBOL(omapfb_get_update_mode);

/* XXX this color key handling is a hack... */
static struct omapfb_color_key omapfb_color_keys[2];

This is the related documentation:
http://pandorawiki.org/Power_modes#Low_Power
(Please update accordingly as part of the issue resolution)

FROM MY USER EXPERIENCE:

If you put the Pandora into Low Power Mode, then press some keys, and then wake the Pandora back into Normal Mode, your input (both keys and nubs, haven't tried with USB input yet) seem to have triggered something while the device was in Low Power Mode!

What does really happen in Low Power Mode concerning execution and input?

a) Input is received AND triggers as application execution continues
or
b) Kernel/driver queues the input signals into a buffer, and executes them on wake?

If supposition a) or b) is true, then this would be one more reason to properly implement:  FS#259 

OBSERVANCE EXAMPLE 1:

1) Start MiniMenu. Mentally note down your active tab.
2) Put Pandora to Low Power Mode.
3) Press shoulder button R once.
4) Wake Pandora to Normal Mode. You are now one tab to the right of where you left. Input must have been caught in Low Power Mode, but wether execution of it happened while Low Power Mode or later after wake in Normal power Mode is unclear.

OBSERVANCE EXAMPLE 2:

1) Start gedit (a text editor). Insert the digit "1".
2) Put Pandora to Low Power Mode.
3) Press: CTRL-N 2 CTRL-N 3 CTRL-N 4. (Without the spaces)
4) Wake Pandora to Normal Mode.
5) For a fraction of a second you see the tabs building up. Either the input was really received AND executed while Low Power Mode and what you see is just a delayed window manager refreshment, or the input was queued in Low Power Mode, and only executed on wake.

populating volatile requires execution of initialization script, which I had to minimally modify for it to start working. I am placing that file to /usr/pandora/init/ folder.

Any suggestions for better place for custom init scripts? :)

This script fixes utmp (and pndnotifyd) problem for systemd image

Noticed problems (TODO):
boot sequence recreates cache, run and tmp dirs before populate-volatile inits them. One of the solutions would be to deploy system with symlinks already in place (pointing to /var/volatile subdirs)

-------------
Deployment:

delete:
/etc/init.d/populate-volatile.sh
/etc/rcS.d/S37populate-volatile.sh
/var/{cache,lock,log,run,tmp}

add:
/etc/systemd/system/populate-volatile.service
/usr/pandora/init/populate-volatile.sh

symlink:
/etc/systemd/system/basic.target.wants/populate-volatile.service to /etc/systemd/system/populate-volatile.service

URLs for files:
http://dl.dropbox.com/u/18781412/next/populate-volatile.service
http://dl.dropbox.com/u/18781412/next/populate-volatile.sh

Steps to reproduce the bug(s):

1) In MiniMenu select an arbitrary app.
2) Press SPACE to bring up the contextual menu.
3) Select "Edit notes line 1".
4) Insert your string and confirm.
5) Now at a later time you may decide to remove your note line again. Therefore you select the same app again in MiniMenu, then repeat steps 2-3, but this time:

a) Erase all characters so that you get an empty string and then confirm. RESULT: Your change is simply ignored! There should be a possibility within MiniMenu to remove/reset note lines, the simplest being to simply accept an empty string as an input, that's what an average user will try if s/he does not find a dedicated "Delete note line" command.

b) As a workaround I tried something and detected yet another bug! As I could not create an empty string, I simply created a note line only containing 1 SPACE character (=the string " ") and confirmed. This got accepted.

If MiniMenu is in detailed view mode (press the A-button or TAB in order to bring it up, if it is not already there) and you slide over an app whose note line is " ", MiniMenu crashes!

Maybe the bug is connected with the writing to / the parsing from the .OVR (override) files which MiniMenu creates for the affected files, as the separating value in OVR files seems to be TAB, and SPACE is also WHITESPACE, therefore some parsers probably skip/misinterpret this, and MiniMenu then catches an unexpected situation!

WORKAROUND: If you ran into the problem, that you cannot get rid of the note lines anymore, simply start a file browser of your choice, navigate to the location of the affected .PND file and find its sister .OVR (override) file and delete it or edit it accordingly!

I assigned personal subcategories to some of my games.
Some of those subcategories share the same beginning string, i.e: Shooter, ShooterBallistic ShooterScoller.
MiniMenu displays those subcategories with flaws! See the ASCII screenshots below.
Note: The star symbols indicate the currently active selection.

The main category tab "Game" being active:

----------------------------------------------------------
| All | Audio | AudioVideo | Education |*Game*| Graphics |
----------------------------------------------------------
ActionGame AdventureGame ArcadeGame BlocksGame ...
Shooter ShooterBallistic ShooterScroller ...
GameA GameB GameC ...
----------------------------------------------------------

Now if I navigate into the sub-category "Shooter", everything normal:

----------------------------------------------------------
|*Shooter*|
----------------------------------------------------------
.. ShooterA ShooterB ShooterC ...
----------------------------------------------------------

But if I navigate to the sub-category "ShooterBallistic", strangely MiniMenu shows 2 tabs, "Shooter" and "ShooterBallistic", and jumps right into "Shooter".

----------------------------------------------------------
|*Shooter*| ShooterBallistic |
----------------------------------------------------------
.. ShooterA ShooterB ShooterC ...
----------------------------------------------------------

In order to reach my intended tab "ShooterBallistic" I need to navigate to it again. Annoying. There the contents are as expected:

----------------------------------------------------------
| Shooter |*ShooterBallistic*|
----------------------------------------------------------
.. ShooterBallisticA ShooterBallisticB ShooterBallisticC
----------------------------------------------------------

The flaw is the same for all other sub-categories beginning with "Shooter...". All have the flaw as shown in the example "ShooterBallistic", only that it is themselves instead of "ShooterBallistic". One more example to be perfectly clear:

----------------------------------------------------------
| Shooter |*ShooterScroller*|
----------------------------------------------------------
.. ShooterScrollerA ShooterScrollerB ShooterScrollerC
----------------------------------------------------------

Imagine this tab content:
Nubs, Pandora Input, PNDstore.

CURRENT BEHAVIOR:

Pressing "P" and "N" is succession jumps to "Nubs" eventually, as it first jumps to the first "P" item ("Pandora Input"), then to the first "N" item, "Nubs".

DESIRED BEHAVIOR:

That it acts like in most Linux file browsers or the Mac OS X Finder.

In detail: Pressing "P" and "N" within a certain time limit should combine them to the string "PN" and jump to the first item which starts with that string, i.e. "PNDStore". If no item matches, reduce the combination string by one character, try to match again, if that doesn't match, try matching again with one character less, ... , until only one character is left, and if that one doesn't match jump to the nearest previous lexicographical character, which matches.

As verified with xev, an attached bluetooth keyboard can not generate colon (shift semicolon). xmodmap shows that (unlike a standard Linux system) shift-semicolon is mapped to NoSymbol. While it's find that there's a special symbol to get semicolon on the built-in keyboard, the other binding really should be there in support of attached keyboards.

Hi, sadly the XFCE bluetooth manager seems to have problems with pairing simple SPP devices (an BT GPS mouse here).

1. Enable BT
2. BT Manager -> Add new device
3. Confirm Dialog and wait for scanning
4. Pick device
5. Select PIN options -> "0000" (here for me)
In next step the dialog still asks you to enter a random PIN at your BT device (which is impossible here).

Thus it seems, that the XFCE dialog makes troubles, I tried it with 2 different GPS. Pairing the GPS manually works fine:
sudo rfcomm connect rfcomm0 00:18:E4:26:5F:14

This patch when applied aginst TI 4.04.00.03 SGX drivers will allow building the pvr kernel modules.
This relies on task 272 (kernel patch) and should be used inconjuction with task 273

diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_displayclass.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_displayclass.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_displayclass.c 2011-06-20 21:03:33.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_displayclass.c 2012-02-09 08:37:21.000000000 +1100
@@ -830,7 +830,11 @@
unsigned long ulLCM;
unsigned uiFBDevID = psDevInfo->uiFBDevID;

+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif

psLINFBInfo = registered_fb[uiFBDevID];
if (psLINFBInfo == NULL)
@@ -972,7 +976,11 @@
ErrorModPut:
module_put(psLINFBOwner);
ErrorRelSem:
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif

return eError;
}
@@ -982,7 +990,11 @@
struct fb_info *psLINFBInfo = psDevInfo->psLINFBInfo;
struct module *psLINFBOwner;

+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif

psLINFBOwner = psLINFBInfo->fbops->owner;

@@ -993,7 +1005,11 @@

module_put(psLINFBOwner);

+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif
}

static OMAPLFB_DEVINFO *OMAPLFBInitDev(unsigned uiFBDevID)
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c 2011-06-20 21:03:33.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c 2012-02-09 13:14:28.000000000 +1100
@@ -24,11 +24,14 @@
*
******************************************************************************/

+
+#include <linux/version.h>
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>

#include <asm/atomic.h>

@@ -236,8 +239,11 @@
struct fb_var_screeninfo sFBVar;
int res;
unsigned long ulYResVirtual;
-
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif

sFBVar = psDevInfo->psLINFBInfo->var;

@@ -268,31 +274,37 @@
printk(KERN_INFO DRIVER_PREFIX ": %s: Device %u: fb_pan_display failed (Y Offset: %lu, Error: %d)\n", __FUNCTION__, psDevInfo->uiFBDevID, psBuffer->ulYOffset, res);
}
}
-
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif
}

OMAPLFB_UPDATE_MODE OMAPLFBGetUpdateMode(OMAPLFB_DEVINFO *psDevInfo)
{
struct omap_dss_device *psDSSDev = fb2display(psDevInfo->psLINFBInfo);
OMAP_DSS_DRIVER(psDSSDrv, psDSSDev);
-
- enum omap_dss_update_mode eMode;
-
- if (psDSSDrv == NULL || psDSSDrv->get_update_mode == NULL)
- {
- DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: Can't get update mode\n", __FUNCTION__, psDevInfo->uiFBDevID));
- return OMAPLFB_UPDATE_MODE_UNDEFINED;
+ if (psDSSDrv == NULL || psDSSDev == NULL)
+ {
+ DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: No DSS device\n", __FUNCTION__, psDevInfo->uiFBDevID));
+ }
+ enum omapfb_update_mode eMode;
+
+ if (!omapfb_get_update_mode(psDevInfo->psLINFBInfo, &eMode))
+ {
+// DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: Can't get update mode\n", __FUNCTION__, psDevInfo->uiFBDevID));
+ return OMAPLFB_UPDATE_MODE_AUTO;
+// return OMAPLFB_UPDATE_MODE_UNDEFINED;
}

- eMode = psDSSDrv->get_update_mode(psDSSDev);
switch(eMode)
{
- case OMAP_DSS_UPDATE_AUTO:
+ case OMAPFB_AUTO_UPDATE:
return OMAPLFB_UPDATE_MODE_AUTO;
- case OMAP_DSS_UPDATE_MANUAL:
+ case OMAPFB_MANUAL_UPDATE:
return OMAPLFB_UPDATE_MODE_MANUAL;
- case OMAP_DSS_UPDATE_DISABLED:
+ case OMAPFB_UPDATE_DISABLED:
return OMAPLFB_UPDATE_MODE_DISABLED;
default:
DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: Unknown update mode (%d)\n", __FUNCTION__, psDevInfo->uiFBDevID, eMode));
@@ -307,10 +319,10 @@
{
struct omap_dss_device *psDSSDev = fb2display(psDevInfo->psLINFBInfo);
OMAP_DSS_DRIVER(psDSSDrv, psDSSDev);
- enum omap_dss_update_mode eDSSMode;
+ enum omapfb_update_mode eDSSMode;
int res;

- if (psDSSDrv == NULL || psDSSDrv->set_update_mode == NULL)
+ if (psDSSDrv == NULL)
{
DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: Can't set update mode\n", __FUNCTION__, psDevInfo->uiFBDevID));
return OMAPLFB_FALSE;
@@ -319,20 +331,20 @@
switch(eMode)
{
case OMAPLFB_UPDATE_MODE_AUTO:
- eDSSMode = OMAP_DSS_UPDATE_AUTO;
+ eDSSMode = OMAPFB_AUTO_UPDATE;
break;
case OMAPLFB_UPDATE_MODE_MANUAL:
- eDSSMode = OMAP_DSS_UPDATE_MANUAL;
+ eDSSMode = OMAPFB_MANUAL_UPDATE;
break;
case OMAPLFB_UPDATE_MODE_DISABLED:
- eDSSMode = OMAP_DSS_UPDATE_DISABLED;
+ eDSSMode = OMAPFB_UPDATE_DISABLED;
break;
default:
DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: Unknown update mode (%d)\n", __FUNCTION__, psDevInfo->uiFBDevID, eMode));
return OMAPLFB_FALSE;
}

- res = psDSSDrv->set_update_mode(psDSSDev, eDSSMode);
+ res = omapfb_set_update_mode(psDevInfo->psLINFBInfo, eDSSMode);
if (res != 0)
{
DEBUG_PRINTK((KERN_INFO DRIVER_PREFIX ": %s: Device %u: set_update_mode failed (%d)\n", __FUNCTION__, psDevInfo->uiFBDevID, res));
@@ -441,10 +453,17 @@
OMAPLFB_ERROR OMAPLFBUnblankDisplay(OMAPLFB_DEVINFO *psDevInfo)
{
int res;
-
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif
res = fb_blank(psDevInfo->psLINFBInfo, 0);
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif
if (res != 0 && res != -EINVAL)
{
printk(KERN_WARNING DRIVER_PREFIX
@@ -459,9 +478,17 @@

static void OMAPLFBBlankDisplay(OMAPLFB_DEVINFO *psDevInfo)
{
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif
fb_blank(psDevInfo->psLINFBInfo, 1);
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif
}

static void OMAPLFBEarlySuspendHandler(struct early_suspend *h)
@@ -692,9 +719,17 @@
flush_workqueue(psDevInfo->psSwapChain->psWorkQueue);
}

+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_lock();
+#else
acquire_console_sem();
+#endif
ret = fb_blank(psDevInfo->psLINFBInfo, iFBMode);
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+ console_unlock();
+#else
release_console_sem();
+#endif

OMAPLFBCreateSwapChainUnLock(psDevInfo);

@@ -717,7 +752,6 @@
static int __init OMAPLFB_Init(void)
#endif
{
-
if(OMAPLFBInit() != OMAPLFB_OK)
{
printk(KERN_WARNING DRIVER_PREFIX ": %s: OMAPLFBInit failed\n", __FUNCTION__);
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/common/resman.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/common/resman.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/common/resman.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/common/resman.c 2012-02-09 23:33:43.000000000 +1100
@@ -24,15 +24,17 @@
*
******************************************************************************/

+#include <linux/version.h>
#include "services_headers.h"
#include "resman.h"

#ifdef __linux__
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <linux/sched.h>
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,9)
#include <linux/hardirq.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/event.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/event.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/event.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/event.c 2012-02-09 09:00:12.000000000 +1100
@@ -24,11 +24,14 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <asm/io.h>
#include <asm/page.h>
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,22))
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mmap.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mmap.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mmap.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mmap.c 2012-02-09 08:56:41.000000000 +1100
@@ -24,11 +24,14 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <linux/mm.h>
#include <linux/module.h>
#include <linux/vmalloc.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.c 2012-02-09 08:52:48.000000000 +1100
@@ -24,11 +24,14 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <linux/mm.h>
#include <linux/vmalloc.h>
#include <asm/io.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.h b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.h
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.h 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mm.h 2012-02-09 08:55:49.000000000 +1100
@@ -27,11 +27,14 @@
#ifndef __IMG_LINUX_MM_H__
#define __IMG_LINUX_MM_H__

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <linux/slab.h>
#include <linux/mm.h>
#include <linux/list.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/module.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/module.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/module.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/module.c 2012-02-09 08:59:05.000000000 +1100
@@ -24,9 +24,13 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

#if !defined(SUPPORT_DRI_DRM)

@@ -44,7 +48,6 @@
#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/module.h>
-#include <linux/version.h>
#include <linux/fs.h>
#include <linux/proc_fs.h>

diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.c 2012-02-10 00:24:09.000000000 +1100
@@ -24,10 +24,13 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
-#include <linux/version.h>
+#endif

#include <linux/spinlock.h>
#include <linux/mm.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.h b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.h
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.h 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/mutils.h 2012-02-09 08:54:31.000000000 +1100
@@ -27,11 +27,13 @@
#ifndef __IMG_LINUX_MUTILS_H__
#define __IMG_LINUX_MUTILS_H__

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
-
-#include <linux/version.h>
+#endif

#if !(defined(__i386__) && (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,26)))
#if defined(SUPPORT_LINUX_X86_PAT)
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/osfunc.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/osfunc.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/osfunc.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/osfunc.c 2012-02-09 09:01:16.000000000 +1100
@@ -24,11 +24,14 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <asm/io.h>
#include <asm/page.h>
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,22))
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/proc.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/proc.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/proc.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/proc.c 2012-02-09 08:57:49.000000000 +1100
@@ -24,13 +24,16 @@
*
******************************************************************************/

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

#include <linux/init.h>
#include <linux/module.h>
-#include <linux/version.h>
#include <linux/fs.h>
#include <linux/proc_fs.h>
#include <linux/seq_file.h>
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_debug.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_debug.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_debug.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_debug.c 2012-02-09 23:54:38.000000000 +1100
@@ -24,9 +24,12 @@
*
******************************************************************************/

+#include <linux/version.h>
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

#include <asm/io.h>
#include <asm/uaccess.h>
@@ -72,7 +75,7 @@
static PVRSRV_LINUX_MUTEX gsDebugMutexNonIRQ;

-static spinlock_t gsDebugLockIRQ = SPIN_LOCK_UNLOCKED;
+static DEFINE_SPINLOCK(gsDebugLockIRQ);

#if !defined (USE_SPIN_LOCK)
#define USE_SPIN_LOCK (in_interrupt() || !preemptible())
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_drm.c b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_drm.c
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_drm.c 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_drm.c 2012-02-16 01:58:14.000000000 +1100
@@ -26,14 +26,16 @@

#if defined(SUPPORT_DRI_DRM)

+#include <linux/version.h>
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/module.h>
-#include <linux/version.h>
#include <linux/fs.h>
#include <linux/proc_fs.h>
#include <linux/sched.h>
@@ -371,11 +373,23 @@
.poll = drm_poll,
.fasync = drm_fasync,
},
+#if (LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,38))
.pci_driver =
{
.name = PVR_DRM_NAME,
.id_table = asPciIdList,
},
+#else
+ .kdriver =
+ {
+ PVR_DRM_NAME,
+ asPciIdList,
+ },
+// {
+// .pci->name = PVR_DRM_NAME,
+// .pci->id_table = asPciIdList,
+// },
+#endif

.name = PVR_DRM_NAME,
.desc = PVR_DRM_DESC,
@@ -385,6 +399,13 @@
.patchlevel = PVRVERSION_BUILD,
};

+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,39))
+static struct pci_driver pci_pvr_driver = {
+ .name = PVR_DRM_NAME,
+ .id_table = asPciIdList,
+};
+#endif
+
static int __init PVRSRVDrmInit(void)
{
int iRes;
@@ -401,7 +422,11 @@
}
#endif

+#if (LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,38))
iRes = drm_init(&sPVRDrmDriver);
+#else
+ iRes = drm_pci_init(&sPVRDrmDriver,&pci_pvr_driver);
+#endif
#if defined(PVR_DRI_DRM_NOT_PCI)
if (iRes != 0)
{
@@ -413,7 +438,11 @@

static void __exit PVRSRVDrmExit(void)
{
+#if (LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,38))
drm_exit(&sPVRDrmDriver);
+#else
+ drm_pci_exit(&sPVRDrmDriver,&pci_pvr_driver);
+#endif

#if defined(PVR_DRI_DRM_NOT_PCI)
drm_pvr_dev_remove();
diff -ru a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_uaccess.h b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_uaccess.h
--- a/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_uaccess.h 2011-06-20 21:03:34.000000000 +1000
+++ b/Graphics_SDK_4_04_00_03/GFX_Linux_KM/services4/srvkm/env/linux/pvr_uaccess.h 2012-02-09 08:51:21.000000000 +1100
@@ -27,11 +27,14 @@
#ifndef __PVR_UACCESS_H__
#define __PVR_UACCESS_H__

+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,38)
#ifndef AUTOCONF_INCLUDED
#include <linux/config.h>
#endif
+#endif

-#include <linux/version.h>
#include <asm/uaccess.h>

static inline unsigned long pvr_copy_to_user(void __user *pvTo, const void *pvFrom, unsigned long ulBytes)

Please add support for xz compression in the kernel so squashfs tools can compress better the png images.

ISSUE ENVIRONMENT:

If you hold your Pandora in your hands, you only have your thumbs for typing, hence your typing abilities are quite limited.

It is hard to press more than 2 keys, and hard to press 2 keys on the same side, as your second thumb does not reach the opposite side all too easy (except you have a basketball player's hands).

The modifier keys Start/ALT Select/CTRL Pandora/(META, I guess?) are in the middle of the keyboard, hence the can easily pressed together with another key. But SHIFT lies at an ergonomically problematic side (left boundary). Hence hard to press with other left side keys.

SUGGESTED SOLUTION:

I suggest that Pandora OS offers an optional and configurable input help.

[1|2|3 presses | hold for duration x] SHIFT [timeout y] [modifier key 2] [timeout z] key

Produces the same result like SHIFT + modkey2 + key

Very likely modifier key 2 and timeout z are not necessary, as you can trigger the SHIFT hold (by your defined action), and then press the modifier key 2 and the other key at once, as the other modifier keys are laid at a central (ergonomically better) position.

PyGame is damn slow (games with scrolling are not at all playable).
Would be nice if Hardware surface could be used :)

On OS Zaxon (hotfix 3).

With "xfconf-query", the resolution is 800x480@60 Hz.
But with the tool in the menu "Settings" -> "Display", the resolution is 800x480@0 Hz.

With Java (opensdk-6-jre 6b18-1.8),

GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getDisplayModes()

return 1 display mode that is 800x480@0 Hz with a BPP of -1.

It seems to be the reason that GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getDisplayMode() return null
and when closing a java application that goes in fullscreen mode to throw an exception (invalid display mode).