Re: APUS Debian Boot-Floppies Images and bugs

[Ken T. <ke...@we...>]

On Wed, 16 May 2001, Alan Buxey wrote:

Hello,

> is there a source for all thes e- or is it a case of reading through all
> the driver .c files for their flags? 

> from this, i guess such things as virge:1024x768-8, virge:640x480-24
> will work? what controls the refresh for this card?

I think all the relevant drivers in 2.2 and those in 2.4 which don't use
modedb.c support, take modes like video=name:XRESxYRES-depth apart from
amifb which takes options like ntsc, dblpal, vga and more.  Some drivers
also accept otions like video=cyberfb:cyber16 to give a 16 bit default
mode.

Yes, each driver needs its own collection of supported modes gathered by
searching through the .c files, or a subset of common modes - if you are
lucky.

The refresh rate is determined by the constants in the mode data base
built into each driver (apart from those using modedb). For instance
800x600-16 in (my) virgefb gives 50Hz refresh but 1024x768-8 gives 75Hz
refresh, you get the refresh rate you're given!.

Mode can be changed later by fbset, either to a mode in /etc/fb.modes, or
by giving specific values for some or all of the parmeters.

Only way to know the true refresh rate is to calculate it from pixelclock
and the horizontal and vertical resolution, sync and margin values.

> okay, so I'll base it on the bpp mode for now.

With virge driver as it is in kernels (both 2.2 and 2.4) now, bootstrap
needs the -v option, keep amiga video and be booted from a WB screen of
the same xres, yres and depth.

I should commit the virge changes.

Ken.