Guide to Get the Best Performace from the GMA 500

[mikewhatever]

3535.126] (II) PSB(0): Debug: xxi830_psbCrtcGammaSet
[  3535.126] (II) PSB(0): Debug: xxi830_psbCrtcLoadLut 0x8386c00

Does anyone know what the above means. The Xorg logs are full of it here, 600 lines after about 3 hours of uptime, and they keep appearing at the end of the log.

[lucazade]

3535.126] (II) PSB(0): Debug: xxi830_psbCrtcGammaSet
[  3535.126] (II) PSB(0): Debug: xxi830_psbCrtcLoadLut 0x8386c00

Does anyone know what the above means. The Xorg logs are full of it here, 600 lines after about 3 hours of uptime, and they keep appearing at the end of the log.

Don't know what those lines means, my log is full of
(II) PSB(0): SDVO: R: 12 00 (Pending)

these debug messages were enabled/added when the psb driver
was created inside the moblin project and nobody removed or fixed them.

psb driver is full of patches and debug messages.. A clean implementation or
a good clean would be nice.

[lucazade]

I am going to move new xserver-xorg-video-psb with Xv video patch from
fix ppa to main one.
Let me know if ok or if there is any issue.

[yvesdm3000]

Well I have mostly messages regarding the fade-down of the backlight and sometimes some other messages and I generally clean-up my debug junk before I post a patch. Maybe we should add a 'debug'-option and only display the messages when the option is enabled?

-Yves

[lucazade]

Well I have mostly messages regarding the fade-down of the backlight and sometimes some other messages and I generally clean-up my debug junk before I post a patch. Maybe we should add a 'debug'-option and only display the messages when the option is enabled?

-Yves

I agree.. a debug option could be a solution.
I believe that reading and writing xorg.log eat also battery because it always access hd.
Let me know how I could help you.

[yvesdm3000]

patch that kills debug now on launchpad

[argonius]

Back to psb on my Nokia Booklet with Xv and Brightness working. Cool, thanks guys!

Christian

[legoman666]

check in "gstreamer-properties" in 2nd tab "Video"
if Automatic detection is selected as standard plugin
for video out.

It is now. I tried all three options, all crash the plugin.

[tista]

Hi, all EMGDers.

The situation in previous post of mine would change now: #3234

The newer upstream kernel 2.6.38-4-generic for Natty has something happens. the emgdbl would be loaded successfully but ACPI video driver might override it (activated as "/sys/class/backlight/acpi_video0/"...). now I'm trying to fix this bug. it would cause to i915 or intel opregion codes updates. so I might have to rebuild video.ko with dispatch for newest updates...

so if you run EMGD on Natty with emgdbl successfully, you'd better to lock your kernel version less than 2.6.38-3-generic. I'm so sorry. (but don't worry about system crash by upgrading kernel to 2.6.38-4-generic. only emgdbl problems.)

I must fix this bug A.S.A.P. and so sorry for disturbing discussions in PSB.

[P.S:]
I've attached alpha2 source.
This alpha2 would be released as "workaround for acpi video issues in Natty".
so it would be run with newest 2.6.38-4-generic kernel.

[chagelog from alpha1]
* purge ACPI video register function.
* some property codes ware updated.

[notes]
* the kernel option "acpi_backlight=video" was still recommended in order to disable platform specified backlight controls.
* emgdbl now run as standalone module (independent from video.ko module).
* all bugs in alpha1 would be still remained.

If you already tried alpha1 release, you should update to alpha2 soon !!

Regards.

[yvesdm3000]

It is now. I tried all three options, all crash the plugin.

Make sure all of your gsrteamer packages are current, they are not that well packaged and if one is older, gstreamer isn't that reliable...

-Yves