From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?
Date: Fri, 30 Dec 2005 18:37:43 +0100 [thread overview]
Message-ID: <43B57067.1010807@vc.cvut.cz> (raw)
In-Reply-To: <20051223031333.GA14399@shaftnet.org>
Stuffed Crust wrote:
> I have an AMD64 laptop with a Radeon Mobility X700, and a 1680x1050
> screen. I'm trying to get it to work with the "new" radeonfb driver in
> Linux 2.6.15-rc6. I have not tested the "old" driver. As best as I can
> tell, I'm the second person to ask about this particular bit of
> hardware.
>
> The Radeon M26, aka Mobility X700, is supposedly a derivative of the
> desktop X700, aka RV410, which in turn is supposedly derived from the
> R423. (They certainly make this rather confusing..) As configured, mine
> has 128 megs of RAM and a PCI ID of 1002:5653.
>
> This deviceid is not present in the device table, but to get it detected
> to begin with, I added this to the device table in radeon_base.c:
>
> CHIP_DEF(PCI_CHIP_RV410_XX, R420, CHIP_HAS_CRTC2 | CHIP_IS_MOBILITY),
>
> And in ati_ids.h:
>
> #define PCI_CHIP_RV410_XX 0x5653
>
> As I mentioned, this chip (M26, RV410) is supposedly closer to the X800
> (R420) than the X600 (RV380). Just in case, I tried setting it to a
> 'RV380' target as well, with similar results.
I have simillar notebook, just with 1920x1200 panel. Unfortunately new
BIOS these pieces use has information in other places, so radeonfb does
not find anything (as far as I can tell, panel ID string is not in the
BIOS image at all, and i2c busses are connected elsewhere than on
hardware radeonfb knows about).
> Mucking with module options has no discernable effect, and the LVDS
> panel information is consistently misdetected, obviously.. It would
> seem that all of the panel information is garbage. (does fetching the
> panel info from the BIOS work when running on an x86-64 system?)
It is not in the BIOS anymore. VESA call 0x4F15 works fine, but I did
not bothered with looking at the BIOS yet. With my hardware radeonfb
correctly finds that LVDS output is programmed for 1920x1200 and does
not touch it, unfortunately it has some problems with memory fetches
which cause pixels (+-)512-768 and 1536-1792 to be missing on display,
and right side of picture being black.
For now I use vesafb - unfortunately BIOS does not have 1920x1200
videomode, but 1600x1200 works more or less acceptable, those pixels are
really small...
Petr
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-30 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 3:13 radeonfb: Radeon Mobility X700 (M26) + x86-64 supported? Stuffed Crust
2005-12-30 17:37 ` Petr Vandrovec [this message]
2006-01-03 0:38 ` Benjamin Herrenschmidt
2006-01-03 20:39 ` Petr Vandrovec
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=43B57067.1010807@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).