linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlo E. Prelz" <fluido@fluido.as>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
Date: Fri, 17 Oct 2003 12:04:12 +0200	[thread overview]
Message-ID: <20031017100412.GA1639@casa.fluido.as> (raw)
In-Reply-To: <1066300935.646.136.camel@gaston>

	Subject: Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
	Date: gio, ott 16, 2003 at 12:42:15 +0200

Quoting Benjamin Herrenschmidt (benh@kernel.crashing.org):

> You also have an rsync mirror of that tree at
> source.mivsta.com::linuxppc-2.5-benh

Ok. I got the code (it is mvista, not mivsta...). My card is
recognized without modifications:

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

bus pci: add driver radeonfb
radeonfb_pci_register BEGIN
radeonfb: probed DDR SGRAM 131072k videoram
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=200.00 Mhz, System=166.00 MHz
Starting monitor auto detection...
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: I2C (port 3) ... found CRT display
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
========================================
Display Information (EDID)
========================================
   EDID Version 1.3
   Manufacturer: MED Model: 4720 Serial#: 0
   Year: 2001 Week 44
   Display Characteristics:
      Analog Display Input: Input Voltage - 0.700V/0.300V
      Sync: Serration on 
      Max H-size in cm: 34
      Max V-size in cm: 27
      Gamma: 2.20
      DPMS: Active yes, Suspend yes, Standby yes
      RGB Color Display
      Chromaticity: RedX:   0.625 RedY:   0.340
                    GreenX: 0.280 GreenY: 0.595
                    BlueX:  0.155 BlueY:  0.070
                    WhiteX: 0.281 WhiteY: 0.311
      Default color format is primary
      First DETAILED Timing is preferred
      Display is GTF capable
   Standard Timings
      1280x1024@60Hz
   Supported VESA Modes
      720x400@70Hz
      640x480@60Hz
      640x480@67Hz
      640x480@72Hz
      640x480@75Hz
      800x600@56Hz
      800x600@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      1152x870@75Hz
      Manufacturer's mask: 0
   Detailed Monitor Information
      135 MHz 1280 1296 1440 1688 1024 1025 1028 1066 +HSync +VSync

      Serial No     : 0
      Monitor Name  : MD 9463 AE
      HorizSync     : 24-80 KHz
      VertRefresh   : 56-75 Hz
      Max Pixelclock: 130 MHz
========================================
radeonfb: Monitor 2 type no found
radeonfb: ATI Radeon Yd  DDR SGRAM 128 MB
radeonfb_pci_register END
bound device '0000:01:00.0' to driver 'radeonfb'

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

and then

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

hStart = 664, hEnd = 760, hTotal = 800
vStart = 491, vEnd = 493, vTotal = 525
h_total_disp = 0x4f0063	   hsync_strt_wid = 0x8c02a2
v_total_disp = 0x1df020c	   vsync_strt_wid = 0x8201ea
pixclock = 39721
freq = 2517
post div = 0x8
fb_div = 0x59
ppll_div_3 = 0x30059
lvds_gen_cntl: 08000008
Console: switching to colour frame buffer device 80x30

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

Then, when changing to 1280x1024, with command

/usr/sbin/fbset  -depth 32 1280x1024-60

the actual console changes correctly, but when switching to other VCs,
the monitor again complains saying it gets bad frequencies: 103.1 kHz
horizontal and 197.8 Hz vertical.

If I blindly login, and run the appropriate fbset command, the
terminal works OK. I made this small script:

#!/bin/sh
stty cols 160 rows 64
/usr/sbin/fbset  -depth 32 1280x1024-60
consolechars -m iso15 -f iso15graf-16

and gave it a very short name. This way, once the terminal is set, I
can see what I type. I still have to logout and login again because
bash does not change its idea of the number of columns with
stty... So, quite uncomfortable but working ok. 

Obviously, if I were able to set the default mode to 1280x1024, things
would be sunny.
video=radeonfb:1280x1024-32@60 
and
video=radeonfb:mode:1280x1024-32@60 
seems not to produce any visible effect. What is the current proper
way to initialize radeonfb from LILO? 

And on a similar topic, could you write a couple of examples about how
to use the parameters included in radeon_base.c? I am thinking
especially of the "mirror" and "monitor_layout" parameters, that I
believe would allow me to use the two or three video outputs of the
card independently. I currently read

0 ATI Radeon Yd 

in /proc/fb. I should read two or three lines there, I believe...

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)

  reply	other threads:[~2003-10-17 10:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 22:59 FBDEV 2.6.0-test7 updates James Simmons
2003-10-15 23:17 ` Andrew Morton
2003-10-15 23:22   ` James Simmons
2003-10-15 23:20 ` Andrew Morton
2003-10-15 23:27   ` James Simmons
2003-10-16  9:19     ` Carlo E. Prelz
2003-10-16  9:29       ` Sven Luther
2003-10-17 16:48         ` James Simmons
2003-10-16 10:00       ` Benjamin Herrenschmidt
2003-10-16 10:19         ` Carlo E. Prelz
2003-10-16 10:41           ` Benjamin Herrenschmidt
2003-10-16 10:48             ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-16 10:42           ` Benjamin Herrenschmidt
2003-10-17 10:04             ` Carlo E. Prelz [this message]
2003-10-17 10:49               ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 11:10                 ` Carlo E. Prelz
2003-10-17 11:16                   ` Benjamin Herrenschmidt
2003-10-17 14:44                     ` [Linux-fbdev-devel] " Kronos
2003-10-17 17:29                       ` James Simmons
2003-10-18 21:28                   ` [Linux-fbdev-devel] " Pavel Machek
2003-10-17 17:40                 ` James Simmons
2003-10-17 14:26               ` [Linux-fbdev-devel] " Kronos
2003-10-16 21:06         ` Otto Solares
2003-10-17 10:30           ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 16:52           ` James Simmons
2003-10-17 19:34             ` [Linux-fbdev-devel] " Jon Smirl
2003-10-17 19:50               ` Dave Jones
2003-10-17 22:42       ` Jon Smirl
2003-10-16  0:24   ` Michel Dänzer
2003-10-16  8:19   ` Benjamin Herrenschmidt
2003-10-17 16:45     ` [Linux-fbdev-devel] " James Simmons
2003-10-16  5:08 ` Jan De Luyck
2003-10-17 16:44   ` James Simmons
2003-10-16  5:17 ` Jan De Luyck
2003-10-16 10:44 ` Adrian Bunk
2003-10-16 17:48   ` James Simmons
2003-10-16 19:58 ` Geert Uytterhoeven
2003-10-16 20:40   ` [Linux-fbdev-devel] " Sam Ravnborg
2003-10-17 11:18   ` Benjamin Herrenschmidt
2003-10-17 17:25     ` [Linux-fbdev-devel] " James Simmons
2003-10-17 17:45       ` Torrey Hoffman
2003-10-17 17:23   ` [Linux-fbdev-devel] " James Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031017100412.GA1639@casa.fluido.as \
    --to=fluido@fluido.as \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).