s3c2410fb 8bit mode corrupt

[laforge@…]

The 8bit mode of s3c2410fb seems to be broken, at least in 2.6.20 there seems to
be a NUXI problem (byte swapping), since the fonts get rendered with the wrong
byte order. The palette / LUT is also broken, giving funny color effects

removing HWSWAP from the LCDCON registers did not solve the problem.

[stefan@…]

Small update:

16bit: Working fine
8bit: Broken
4bit: Broken, but different from 8bit
2bit: Different broken again. Not able to launch matchbox.
1bit: Bluescreen only. Not even kernel messages.

Most important one is 8bit, perhaps 4bit. I think we can ignore 2bit and 1bit.

I'll continue with further debugging.

[laforge@…]

8bit is important, we can forget about 2 and 4 bit (IIRC the 2410 can't do this
anyway), but 1bit would be nice if it is fixed, too.

[stefan@…]

Switching from half word swap to byte swap

• S3C2410_LCDCON5_HWSWP,

+ S3C2410_LCDCON5_BSWP,

gives me a working text output on 16bit and 8bit. Colors in X are broken in both
deoths now.

With HWSWP text and colors works.

[stefan@…]

With HWSWP text and colors works.

... with 16bit.

[stefan@…]

I enabled the bootup logo to test the colors on the textconsole.

Using BSWP on 16BPP has a tint. HWSWP is the right choice for 16BPP. It gives
perfect textconsole and X.

For 8BPP BSWP is the right choice for the textconsole. The Tux has the right
color s. The problem with 8BPP start with the Xserver. When starting the xserver
the following appears:

can't get colormap: Invalid argument
alloc color failed
alloc color failed
...

[stefan@…]

Funny observation: rxvt has the right colors, but only grey, white and black.
Same for other apps with disabled openmoko theme.

Icons are still broken

[stefan@…]

To fix the BSWP vs. HWSWP setting problem I'm in contact with Ben Dooks. He's
thinking about the best integration of it.

I will open a new bug about the 8bit kdrive problem.

[stefan@…]

Seems to be a better idea let the info in this bug.

Starting kdrive with 8bit gives the following error:

can't get colormap: Invalid argument

The errors occurs due to an failed ioctl: (hw/kdrive/fbdev/fbdev.c:770)

k = ioctl (priv->fd, FBIOGETCMAP, &cmap);

if (k < 0)
{
perror ("can't get colormap");
return;

FBIOGETCMAP is the ioctl to get the color map from the framebuffer driver.

[stefan@…]

It seems I got to the root of all the problems. :)

During our meeting with mickey he talked about our theme and the 24bit artwork...

After disabling the theme and ignoring more hardcoded theme and artwork stuff it
looks like the 8bit mode worked fine all the time.

I tested this in the beginning but was confused from some hardcoded settings and
icons. At least I learned much abut the fb driver which I can use for the QVGA
support.

That means for 8bit we just need to change the swaping but have not useable UI
as we can not realize our theme in 8bit.

Harald, what was the reason for 8bit support? Just verify that the kernel driver
works fine, power saving or something else?

Dynamically switching between 8bit and 16bit with fbset should be possible but
is still has some problems and is under reseach for QVGA anyway.

[alphaone@…]

So s3c2410fb 8bit mode is working.
Any progress on 1bit mode?

[willie_chen@…]

No more problem here.