|
From: Santiago G. M. <ma...@ay...> - 2002-11-28 17:50:59
|
I have just had lunch, yes, at 17:30 :-(
I have been till late at work trying to get java to work on mozilla on the
NC, but I could not do it (Igalia guys reading this, you could have a look
at this) the Blackdown-1.3.1-02b-FCS machine didn't seem to run ok on powerpc
:-( I have not been able to find IBM's JVM for powerpc (that sounds weird to
me) and blackdown 1.1 machine doesn't seem to have a plugin for Mozilla.
Anyway, I was testing this because I had patched the kernel to get the
64Megs used and so I had memory for a jvm.
> I uploaded a newer patch that fixes the memory size problem and the slow
> timer. This version also knows how to output the kernel command line
Heh heh, rules, I left the ppc compiling it and has finished by now, I'll
test tomorrow.
> prompt to the vga. The boot graphics driver uses whatever is configured
> in the firmware for the x-server. You need to disable CONFIG_VGA_CONSOLE
> for the built-in fb driver to work.
Umm, is that because of the command line output to the vga? Because I was
having 1024x768 with CONFIG_VGA_CONSOLE enabled and having a 128x48 console
without any problem. I'll try to have a look at the code tomorrow, I didn't
have time today.
> As you said, this driver does not init
> the VGA registers, so it will only run at the resolution set by the
> firmware.
Umm, when are we gonna have mode switching on the FB? I mean, like being
able to use 16bpp or something like that :-) Did you have any luck with your
info for setting the modes?
> Can you also post what you added to the fb driver? Is that the init code
> from cyberfb.c?
Nope, I don't have any init code, I just played with the mode settings, I
calculated the values from the XFree settings for 1024x768x85 ISO stuff.
Here is my patch:
diff -r -u linux-2.4.19.orig/drivers/video/s3trio.c linux-2.4.19/drivers/video/s3trio.c
--- linux-2.4.19.orig/drivers/video/s3trio.c Thu Nov 28 18:34:19 2002
+++ linux-2.4.19/drivers/video/s3trio.c Wed Nov 27 10:32:51 2002
@@ -72,12 +72,23 @@
static struct fb_fix_screeninfo fb_fix;
static struct fb_var_screeninfo fb_var = {
+ 1024, 768, 1024, 768, 0, 0, 8, 0,
+ {0, 8, 0}, {0, 8, 0}, {0, 8, 0}, {0, 0, 0},
+ /* 1024x768, 85 Hz, pixclock (ns) lm rm um lm hs vs */
+ 0, 0, -1, -1, FB_ACCELF_TEXT, 10580, 208, 48, 36, 1, 96, 3,
+ FB_SYNC_COMP_HIGH_ACT|FB_SYNC_VERT_HIGH_ACT,
+ FB_VMODE_NONINTERLACED
+};
+
+/*
+static struct fb_var_screeninfo fb_var = {
640, 480, 640, 480, 0, 0, 8, 0,
{0, 8, 0}, {0, 8, 0}, {0, 8, 0}, {0, 0, 0},
0, 0, -1, -1, FB_ACCELF_TEXT, 39722, 40, 24, 32, 11, 96, 2,
FB_SYNC_COMP_HIGH_ACT|FB_SYNC_VERT_HIGH_ACT,
FB_VMODE_NONINTERLACED
};
+*/
static struct fb_var_screeninfo default_var_640x480 = {
640, 480, 640, 480, 0, 0, 8, 0,
@@ -331,8 +342,8 @@
outw(SRC_BACKGROUND | MIX_SRC, 0xb6e8);/* direct color*/
outw(MF_T_CLIP | 0, 0xbee8 ); /* clip virtual area */
outw(MF_L_CLIP | 0, 0xbee8 );
- outw(MF_R_CLIP | (640 - 1), 0xbee8);
- outw(MF_B_CLIP | (480 - 1), 0xbee8);
+ outw(MF_R_CLIP | (1024 - 1), 0xbee8);
+ outw(MF_B_CLIP | (768 - 1), 0xbee8);
Trio_WaitQueue(0x0400);
outw(0xffff, 0xaae8); /* Enable all planes */
outw(0xffff, 0xaae8); /* Enable all planes */
@@ -570,7 +581,7 @@
s3trio_setcolreg(255, 56, 100, 160, 0, NULL /* not used */);
s3trio_setcolreg(254, 0, 0, 0, 0, NULL /* not used */);
- memset((char *)s3trio_base, 0, 640*480);
+ memset((char *)s3trio_base, 0, 1024*768);
#if 0
Trio_RectFill(0, 0, 90, 90, 7, 1);
@@ -804,7 +815,7 @@
s3trio_setcolreg(255, 56, 100, 160, 0, NULL /* not used */);
s3trio_setcolreg(254, 0, 0, 0, 0, NULL /* not used */);
- memset((char *)s3trio_base, 0, 640*480);
+ memset((char *)s3trio_base, 0, 1024*768);
#if 0
Trio_RectFill(0, 0, 90, 90, 7, 1);
> Don't know about alsa. The kernel contains an OSS driver for the Chrystal
> Semi CS4232, but the PReP code in arch/ppc/prep_setup.c is broken. The
> broken code does nothing more than load the driver with the proper settings
> for the machine, i.e. io, interrupt, dma - I think. You should be able to
> enable modules for the kernel, compile cs4232 as module, and insmod with
> proper command line options.
I think I tried this but it didn't compile, I'll try again.
> One weird thing with the nfs root fs -- the mount command does not show any
> of the mounts, i.e. rootfs, /proc, /dev, etc. ???? The nfs root fs works
> very nicely otherwise.
Yes, this is because the root fs is read only (at least I have it like that)
and /etc/mtab doesn't show a thing about actual mounts, I'll try to get this
a little bit better, and also to fix the lot of noisy errors coming on the
screen, but after we get all hard working, I prefer to try to get hard
working first. ;-)
Well, let's see if we can get the FB to work on 16 bits and that sound and
we are almost done ;-)
Regards!
|