Suggestion: Windows CE BSP...

[Antineutrino]

Hi...
I just found this site...

It seems a community where you can share many interesting sources...

http://www.pudn.com/downloads76/sour...ail288001.html

And I downloaded this...
http://rapidshare.com/files/19434687..._V010103_G.rar


If is there any willing and skilled coder to try to rebuild new drivers for our Axims...

[Antineutrino]

These packages contain sources of many drivers for common PPC hardware...
I suppose that in the first one I linked (but don't downloaded yet) we'll find also source code for a 2700G driver...

[MrMage]

43680550XSBase2700G_V010103_G.rar indeed contains such drivers in the Marathon directory, as far as I can consider. But I did not find any Visual C++ project files yet.

Aren't the two links you provided about the same archive?

[Antineutrino]

I think that the first one I linked is XSBase2700G_V010101 and the second is
XSBase2700G_V010103 G

So the one I downloaded is newer I suppose...

[Antineutrino]

These are registry keys added by the driver with a nice explanation...

They are inside 'marathon.reg'
Maybe tweaking those keys we could solve the compatibility problems with the new GWES.exe...

;
; Copyright (c) Microsoft Corporation. All rights reserved.
;
;
; Use of this source code is subject to the terms of the Microsoft end-user
; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.
; If you did not accept the terms of the EULA, you are not authorized to use
; this source code. For a copy of the EULA, please see the LICENSE.RTF on your
; install media.
;

;--------------------------- Power Management ----------------------
;
; Power state definitions extracted from common.reg
;
; ----- D0 state -----
; In this system power state, the user is interacting actively with
; the system.
;
; ----- D1 state -----
; In this system power state, the user may be interacting with the
; system, but not actively. For instance, they might be looking at
; the screen or they might not. In this power state the system is
; "idle" but still in use by the user, so all devices still be
; operational (but possibly with some latency).
;
; ----- D2 state -----
; In this system power state, the user is not considered to be using
; the system, even passively. However, the system is not suspended
; and system programs may be doing work on the user's behalf. In this
; power state the system is "idle" but might still be used by system
; programs. Devices that aren't actively doing work might be powered
; down.
;
; ----- D3 state -----
; In this system power state, the system is suspended. Devices are turned
; off, interrupts are not being serviced, and the CPU is stopped.
;
; ----- D4 state (reset) -----
; Entering this system power state reboots the system. If an OEM includes this state in
; their platform, they must support KernelIoControl() with IOCTL_HAL_REBOOT.
;
; ----- D4 state (shutdown) -----
; Entering this system power state shuts down the system. All devices are powered off,
; resuming may require user intervention. The system will cold boot on resume.
; Supporting this power state requires that the OEM customize the Power Manager
; to recognize POWER_STATE_OFF and take platform-specific action to remove
; power.


;[HKEY_CURRENT_USER\ControlPanel\Backlight]
; "BatteryTimeOut"=dword:3C
; "ACTimeout"=dword:3C

; Amend Power Management registry settings -----------------------------

IF POWER_STATE_ZERO_TIMEOUTS
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Power\Timeouts]
"ACUserIdle"=dword:00000000
"ACSystemIdle"=dword:00000000
"ACSuspend"=dword:00000000
"BattUserIdle"=dword:00000000
"BattSystemIdle"=dword:00000000
"BattSuspend"=dword:00000000
ENDIF

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\State\ShutDown]
"Default"=dword:4 ; D4
"Flags"=dword:20000 ; POWER_STATE_OFF

; This key stops the PM from treating 'systemidle' as a D4 state.(see common.reg)
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\State\SystemIdle\{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}]

IF OSV_PPC

; This key stops the PM from treating 'ScreenOff' as a D4 state. (default is D0)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\State\ScreenOff\{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}]
"Default"=dword:2 ; D2

; This key stops the PM from treating 'Unattended' as a D4 state. (default is D0)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\State\Unattended\{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}]
"Default"=dword:2 ; D2

; This key stops the PM from treating 'Resuming' as a D4 state. (default is D2)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\State\Resuming\{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}]
"Default"=dword:0 ; D0

ENDIF ; OSV_PPC

; PowerVR entries begin --------------------------------

;;;***** bug fix - GWES!Contrast_ReadRegistry() returns success even if the field is
;;; not there. This means that the Restore value is undefined
;;;*****

[HKEY_CURRENT_USER\ControlPanel\Keybd]
"Contrast"=dword:80

[HKEY_LOCAL_MACHINE\SYSTEM\GWE]
; "PORepaint"=dword:0 - the display driver handles everything
; "PORepaint"=dword:1 - gwe should save and restore the bits
; "PORepaint"=dword:2 - gwe should invalidate and repaint
; "PORepaint"=dword:3 - gwe and driver need to save video memory
;
"PORepaint"=dword:3


#if ! defined PVR_CETESTKIT
[HKEY_LOCAL_MACHINE\System\GDI\Drivers]
"Display"="ddi_powervr.dll"
#endif

[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR]

; Single mode stuff
; mode list is trunkated to just one entry with the following settings
"Width"=dword:280
"Height"=dword:1E0
"BitsPerPixel"=dword:10
"OutputMask"=dword:00070707

; Display refresh
; Default wait time (in millisecs) after access before local memory goes into self-refresh
; 0x2710 == 10000 ms == 10 secs
; "LocalMemoryTimeout"=dword:2710
"LocalMemoryTimeout"=dword:A
; Only enable this if the on-die frame buffer is being used to display
"UseSelfRefresh"=dword:1

; Special sleep mode support - to support Marathon and LM off upon sleep
; 1 to enable it; 0 to disable it.
"SpecialSleep"=dword:1

; Marathon system configuration overrides
"VLIOChipSelect"=dword:5
"SRAMChipSelect"=dword:1
"SDRAMMemType"=dword:9

; Marathon Revision ID will be read from the SOC_ID register to determine
; the approprate setting for ODFB Active Power Mode. Active Low Power Mode
; will only be enabled in this way, for revisions A3 and later. This can be
; overrided as required (revisions A0 and A1 do not support ODFB
; Active Low Power Mode). Note: the revision ID for A2 cannot be distinguished
; from the revision ID for A1.
; "ODFBPowerModeActiveLow"=dword:1

; "Prefetch"=dword:0
; "Timeout"=dword:ffffff00
; "BondConfig"=dword:0
; "SPAccessViaVLIO"=dword:ffffffff

; "CoreClock"=dword:C65D40 ;13MHz (ie REFCLK)
; "CoreClock"=dword:17D7840 ;25MHz
; "CoreClock"=dword:2FaF080 ;50MHz
; "CoreClock"=dword:47868C0 ;75MHz
; "CoreClock"=dword:4C4B400 ;80MHz (MBX=/2)
; "CoreClock"=dword:5F5E100 ;100MHz (MBX=/2)
; "CoreClock"=dword:7ED6B40 ;133MHz (MBX=/2)
"Panel"=dword:00000005
"PanelExt"=dword:C0000002

; Screen rotation control
"DisableDynamicScreenRotation"=dword:0

IF OSV_PPC
"RotationRemap"=dword:10E
ENDIF

; Framebuffer allocation stratagy based on the allocation flags
; GPE_REQUIRE_VIDEO_MEMORY and GPE_PREFER_VIDEO_MEMORY
;
; default = 0 All FB memory,internal and external, available
; control is via a bit mask
; bit 0 Req Int FB, always assumed set
; bit 1 Req Ext FB
; bits 2 & 3 ignored
; bit 4 Pref Int FB
; bit 5 Pref Ext FB
; bits 6 - 31 ignored

; "FBAllocStrategy"=dword:21


[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Gl obal\D3DM]
[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Ga me Settings\D3DM]
[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Ga me Settings\D3DM\Common]
[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Ga me Settings\DDraw]
[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Ga me Settings\OpenGLES]
[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\Ga me Settings\OpenGLES\Common]

[HKEY_LOCAL_MACHINE\Drivers\Display\PowerVR\MBX1\La stApp]

[HKEY_LOCAL_MACHINE\system\gdi\rotation]
IF OSV_PPC
;angle from portrait origin for PocketPC
"Angle"=dword:0
"LandscapeMode"=dword:5A
ELSE
;angle from landscape origin for WinCE
IF WCE_LANDSCAPE
"Angle"=dword:0
ELSE
"Angle"=dword:10E
ENDIF
ENDIF

[HKEY_LOCAL_MACHINE\SYSTEM\GDI]
"ClearType"=dword:1

[HKEY_LOCAL_MACHINE\System\GDI\ClearTypeSettings]
;"NativeOrientation"=dword:0 ; 0 is the default. This is the angle that supports cleartype.
IF OSV_PPC
"OffOnRotation"=dword:1 ; 1 means "turn off Cleartype when rotated"
ENDIF

IF OSV_PPC
; Welcome.exe: Disable tutorial and calibration pages
; Touch calibration (0x02), Stylus (0x04), Popup menu (0x08), Timezone (0x10), Complete (0x20)
[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
; Touch calibration must be enabled for high res metrics.
"Disable"=dword:FFFFFFFD

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Player\Video]
; sets WMP default to use full screen if video is large
"Full Screen"=dword:00000001

; -- Specify high res metrics (192 DPI) for PocketPC with VGA panel
; -- For low res (320x240) panel use 96 DPI metrics.
[HKEY_LOCAL_MACHINE\Drivers\Display\GPE]
; 0xC0 = 192 This is DPI info
"LogicalPixelsX"=dword:C0
"LogicalPixelsY"=dword:C0
ENDIF

[HKEY_LOCAL_MACHINE\System\D3DM\Drivers]
"LocalHook"="pvr_d3dm.dll"

; PowerVR entries end ----------------------------------

[Antineutrino]

I think that to rebuild the drivers we need the Microsoft Platform Builder...

http://msdn.microsoft.com/en-us/library/aa448756.aspx

[Antineutrino]

These keys are interesting....
...
..
..
; "CoreClock"=dword:C65D40 ;13MHz (ie REFCLK)
; "CoreClock"=dword:17D7840 ;25MHz
; "CoreClock"=dword:2FaF080 ;50MHz
; "CoreClock"=dword:47868C0 ;75MHz
; "CoreClock"=dword:4C4B400 ;80MHz (MBX=/2)
; "CoreClock"=dword:5F5E100 ;100MHz (MBX=/2)
; "CoreClock"=dword:7ED6B40 ;133MHz (MBX=/2)
...
...

Perhaps we can overclock the 2700G?

[Antineutrino]

Ok...
So I played a bit with CoreClock keys...
Setting it to 133 MHZ...
Benchmark with SKTools Draw Bitmap test...No change
Test it with BenchGLES 0.2... No change

So I think that I have to reboot the device to actually force the video driver read the new frequncy values.
Reboot the device
Check the registry keys if they were changed... No change. Good. It keep settings.
Benchmark again with SKTools Draw Bitmap test...A bit faster but could be a only a random score variation.
Test it with BenchGLES 0.2... AND WHOAAA! It's actually faster! Normally I end with a score of 1216.. Now I reached 1358...
The last test gains about 10-12 FPS... (From 36 to 46-48 FPS).

After that I tried to test with GLBenchmark 1.0.2.
Strange score here.
It's way faster in tests that depend on 2700G Fill Rate but speed in triangle output test seems to be halfed.

So I suppose that the (MBX=/2) means that the triangle engine speed should be 1/2 of the reference speed... This sounds strange because I thought that was the PXA270 CPU to setup the triangle primitives...




Be careful if you dare to test over 133 Mhz. I manage to reach 150Mhz but the screen started to double all the lines and lost the refresh sync.

[Antineutrino]

Ok guys...
I developed a simple application to overclock the 2700G
If you want to try it....

[KimChee]

Ill give it a shot and report back..

[Drakey83]

Originally Posted by Antineutrino

Ok guys...
I developed a simple application to overclock the 2700G
If you want to try it....

Antineutrino I just wanted to thank you for researching these drivers and making this program. I dont know anyhting about the technical side of this kind of stuff so I couldnt really help with this thread because I really wouldnt know what I would be talking about and I would just look stupid. so with that being said I understand it enough to know how much this could potentially help us ax heads and I wanted to thank you for your work on checking this out, also I wanted to tell you thanks for making this program, and to let you know that i am testing it out now. THANKS AGAIN!
Drakey83

Keep up the great work!

[MrMage]

Nice. Cold you tell me which clocks are the default ones?

[Antineutrino]

AFAIK the default setting should be 75 Mhz with no registry key.
When you start the application for the first time it will create the default key.

[Antineutrino]

Originally Posted by Drakey83

Antineutrino I just wanted to thank you for researching these drivers and making this program. I dont know anyhting about the technical side of this kind of stuff so I couldnt really help with this thread because I really wouldnt know what I would be talking about and I would just look stupid. so with that being said I understand it enough to know how much this could potentially help us ax heads and I wanted to thank you for your work on checking this out, also I wanted to tell you thanks for making this program, and to let you know that i am testing it out now. THANKS AGAIN!
Drakey83

Keep up the great work!

I also wish to thank you Drakey83 for the great work you are doing for the great Axim community!

[Antineutrino]

Originally Posted by Antineutrino

...
...
Benchmark again with SKTools Draw Bitmap test...A bit faster but could be a only a random score variation.
...
...

I made a mistake when I stated that SKTools Draw Bitmap benchmark was not faster...
Actually it's 1790 vs 1654, a nice improvement.

Overclocking the x51v CPU to 715 Mhz and 2700G Core I managed to reach 2084 points in that test.

[PhAyzoN]

715? XCPUScalar can take it to 724 (although I dont like 9MHz would help much), unless thats a typo.

EDIT: Actually maybe its 748MHz, I forget I'd have to check.

[KimChee]

What version of xcpuscalar are you using 3.01 or 3.03?

[Antineutrino]

Originally Posted by PhAyzoN

715? XCPUScalar can take it to 724 (although I dont like 9MHz would help much), unless thats a typo.

EDIT: Actually maybe its 748MHz, I forget I'd have to check.

728 Mhz (Maximum reachable by XCPUSCALAR) is not the faster setting for the x51v... 715 is (maximum stable on my x51v) due to faster BUS and RAM.
As desktop PC you can overclock your PPC device not only by increasing cpu multiplier but also by tweaking RAM Speed and BUS Speed...
'Pocket Hack Master' can do this and is way better than XCPUSCALAR...

To reach core speed of 715, BUS 286 and RAM 143 Mhz the settings are
L =22 N=5 A=1 LCD_26 =1 Turbo = On FastBus = On
You can also test other nice settings
as
CPU BUS RAM
683 273 137
702 234 117
663 221 111

Default speed is
624 104 104

[MrMage]

Did you experience less garbled screens with any of those settings?

[Antineutrino]

Originally Posted by MrMage

Did you experience less garbled screens with any of those settings?

All those settings are stable on my x51v and my screen is perfect.
Are you having problems?