From: "Carlo E. Prelz" <fluido@fluido.as>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Re: FBDEV 2.6.0-test7 updates.
Date: Thu, 16 Oct 2003 11:19:18 +0200 [thread overview]
Message-ID: <20031016091918.GA1002@casa.fluido.as> (raw)
In-Reply-To: <Pine.LNX.4.44.0310160022210.13660-100000@phoenix.infradead.org>
Subject: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
Date: gio, ott 16, 2003 at 12:27:44 +0100
Quoting James Simmons (jsimmons@infradead.org):
> I applied it. I also have Ben's new driver avaiable for testing.
> The diff I released uses Ben's new driver but in BK I'm stilling using teh
> old driver.
I am the happy owner of a "Club"-branded Radeon9200 video card. Here
are my experiences using your diff.
My card has a PCI id of 5964. Here you can read the output of 'lspci
-vvv' for it:
--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--
01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5964 (rev 01) (prog-if 00 [VGA])
Subsystem: C.P. Technology Co. Ltd: Unknown device 2073
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: 96 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 16
Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]
Region 1: I/O ports at b800 [size=256]
Region 2: Memory at dfef0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [58] AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--
The only 9200 listed in pci_ids.h had an
id of 5960. I added a new line, as follows:
--- pci_ids.h~ 2003-10-16 08:26:14.000000000 +0200
+++ pci_ids.h 2003-10-16 09:12:22.000000000 +0200
@@ -307,6 +307,7 @@
#define PCI_DEVICE_ID_ATI_RADEON_In 0x496e
/* Radeon RV280 (9200) */
#define PCI_DEVICE_ID_ATI_RADEON_Y_ 0x5960
+#define PCI_DEVICE_ID_ATI_RADEON_Yz 0x5964
/* Radeon R300 (9500) */
#define PCI_DEVICE_ID_ATI_RADEON_AD 0x4144
/* Radeon R300 (9700) */
(I did not know how to call it. _Yz did not exist, so I grabbed it. Is
there any logic in these codes?)
Then I added the new ID to aty/radeon_base.c:
--- radeon_base.c~ 2003-10-16 08:26:13.000000000 +0200
+++ radeon_base.c 2003-10-16 09:13:18.000000000 +0200
@@ -153,6 +153,7 @@
{ PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RADEON_X6, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RADEON_RS300},
{ PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RADEON_X7, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RADEON_RS300},
{ PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RADEON_Y_, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RADEON_RV280},
+ { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RADEON_Yz, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RADEON_RV280},
{ 0, }
};
MODULE_DEVICE_TABLE(pci, radeonfb_pci_table);
Again, I just blindly duplicated the entry for the other 9200. Now the
stuff compiled, but if I chose to make a radeonfb module, I got a
message stating that
WARNING: /lib/modules/2.6.0-test7/kernel/drivers/video/aty/radeonfb.ko needs unknown symbol release_console_sem
Well, I compiled the fb stuff in kernel. The card was eventually
recognized:
radeonfb_pci_register BEGIN
radeonfb: probed DDR SGRAM 131072k videoram
radeonfb: ref_clk=2700, ref_div=12, xclk=16600 from BIOS
Starting monitor auto detection...
radeonfb: Monitor 1 type CRT found
radeonfb: Monitor 2 type no found
radeonfb: ATI Radeon Yd 9200 RV280 DDR SGRAM 128 MB
radeonfb_pci_register END
(BTW what does "type no" mean? I have a monitor connected to the DVD
plug, as well as my normal LCD monitor on the VGA plug - both monitors
show the framebuffer image)
But, always at 640x480. My adding
video=radeonfb:1280x1024-32@60
to the append line in Lilo did not cause any visible effect. Running
'fbset 1280x1024-60' did indeed change the resolution on my two
monitors (although with wrong number of lines and columns - unpleasant
but I know how to fix that). But if I then changed to another virtual
console, both my monitors went black. The LCD one complained that it
was fed invalid frequencies (103.1 kHz horizontal, 197.8 Hz
vertical). At this point, changing virtual consoles had no effect
anymore, and if I typed Ctrl-Alt-Del, the machine would beep (meaning
it caught the reboot request) but nothing would happen
thereafter. Only a hard reboot would give me back the machine.
(There is also this fancy special effect: the cursor is not
full-white, but with cute fractal-like black pixels inside.)
What can I do to help debugging this code? (I am not bk-enabled!)
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)
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-16 9:20 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 [this message]
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 ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-17 10:49 ` 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=20031016091918.GA1002@casa.fluido.as \
--to=fluido@fluido.as \
--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).