[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: can I use video=imsttfb? [was: what is the video=ofonly kernel argument]



On Wed, Oct 02, 2002 at 07:37:08AM -0700, Chris Tillman wrote:
> On Wed, Oct 02, 2002 at 11:47:18AM +0200, Vinai Kopp wrote:
> > 
> > Now, would it be possible to specify this:
> > 
> >    video=imsttfb:vmode:?,cmode:24
> > 
> > And what vmode would/could I specify?
> > I am guessing this on what I read in the bootpromt howto and in
> > imsttfb.c, but I could likely be dreadfully wrong. Any pointers in the
> > right directions are very appreciated!
> 
> This is the 9600, right? According to macframebuffer.html which I
> downloaded from somewhere, that should be and ATI Mach64 (you could
> verify with cat /proc/pci). So then you should be using atyfb, not 
> imsttfb:

Yes, this is the 9600/300 - great you remembered it :)

# cat /proc/pci
[snip hostbridge and stuff]
  Bus  1, device  15, function  0:
    Display controller: Integrated Micro Solutions Inc. IMS9129 [Twin
  turbo 128] (rev 1).
      IRQ 29.
      Master Capable.  Latency=32.  Min Gnt=8.Max Lat=8.
      Prefetchable 32 bit memory at 0x90000000 [0x90ffffff]

# lspci -vv  01:0f.0
01:0f.0 Display controller: Integrated Micro Solutions Inc. IMS9129 
[Twin turbo 128] (rev 01)
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
	ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
	>TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 2000ns max)
        Interrupt: pin A routed to IRQ 29
        Region 0: Memory at 90000000 (32-bit, prefetchable) [size=16M]
        Expansion ROM at 92000000 [disabled] [size=64K]

So I guess it is a imstty, isn't it?

> SYNTAX
> 
>         video=xxxxx:vmode:vv,cmode:cc r
> 
> where xxxxx should be replaced with something appropriate for the frame buffer
> of your video card or built-in video chipset, vv and cc should be replaced with
> a vmode and cmode, respectively, that are supported by your monitor.  r is
> optional, and can be replaced with an appropriate run-level.  See below for
> examples of these values.

This list is wonderfull. Thanks!

> VMODE
> 
> vmode refers to both the screen size in pixels (horizontal x vertical) and the
> refresh rate (in Hz).
> 
> vmode   size(pixels)    refresh         notes
> -----   ------------    -------         -----
> 1       512 x 384       60 Hz           Interlaced NTSC
> 2       512 x 384       60 Hz
> 3       640 x 480       50 Hz           Interlaced PAL
> 4       640 x 480       60 Hz           Interlaced NTSC
> 5       640 x 480       60 Hz
> 6       640 x 480       67 Hz
> 7       640 x 870       75 Hz           Portrait
> 8       768 x 576       50 Hz           Interlaced PAL
> 9       800 x 600       56 Hz
> 10      800 x 600       60 Hz
> 11      800 x 600       72 Hz
> 12      800 x 600       75 Hz
> 13      832 x 624       75 Hz
> 14      1024 x 768      60 Hz
> 15      1024 x 768      72 Hz
> 16      1024 x 768      75 Hz
> 17      1024 x 768      75 Hz
> 18      1152 x 870      75 Hz
> 19      1280 x 960      75 Hz
> 20      1280 x 1024     75 Hz
> 
> 
> CMODE
> 
> cmode refers to the bit depth and will be either 8, 16, 24, or 32 (though 24
> and 32 might actually produce the same result).  To convert bit depth into
> number of colors simply find 2^(bit depth).  So an 8-bit display will have 2^8
> or 256 colors, while a 24-bit display will have 2^24 or 16,777,216 colors
> (millions of colors).  
> 
> This document is: <a href="http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043";>http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043</a>

I'll try out the parameters tonight!

Thanks,
-- 
Vinai
Registered Linux User #280755, Debian GNU/Linux  http://counter.li.org/
Secure eMail with gnupg                          http://www.gnupg.org/

Attachment: pgpHAA0XRTjMv.pgp
Description: PGP signature


Reply to: