From: Jon Smirl <jonsmirl@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
covici@ccs.covici.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 dies when X tries to initialize PCI radeon 9200 SE
Date: Sun, 16 Jan 2005 05:33:05 -0500 [thread overview]
Message-ID: <9e473391050116023344a5f954@mail.gmail.com> (raw)
In-Reply-To: <21d7e997050116020859687c4a@mail.gmail.com>
I use PCI Rage128 cards which are working fine.
I suspect it is this code from radeon_drv.c. There is probably
something wrong with card's BIOS or whatever and it is saying that it
is an AGP card when it is really a PCI one. We used to specify this
manually in xconfig but now DRM code does it automatically. Fix is
probably to add a special case on the PCI_ID of the card that is
failing.
/* There are signatures in BIOS and PCI-SSID for a PCI card,
but they are not very reliable.
Following detection method works for all cards tested so far.
Note, checking AGP_ENABLE bit after drmAgpEnable call can also
give the correct result.
However, calling drmAgpEnable on a PCI card can cause some
strange lockup when the server
restarts next time.
*/
pci_read_config_dword(dev->pdev, RADEON_AGP_COMMAND_PCI_CONFIG, &save);
pci_write_config_dword(dev->pdev, RADEON_AGP_COMMAND_PCI_CONFIG,
save | RADEON_AGP_ENABLE);
pci_read_config_dword(dev->pdev, RADEON_AGP_COMMAND_PCI_CONFIG, &temp);
if (temp & RADEON_AGP_ENABLE)
dev_priv->flags |= CHIP_IS_AGP;
DRM_DEBUG("%s card detected\n",
((dev_priv->flags & CHIP_IS_AGP) ? "AGP" : "PCI"));
pci_write_config_dword(dev->pdev, RADEON_AGP_COMMAND_PCI_CONFIG, save);
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-01-16 10:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 10:30 2.6.10 dies when X tries to initialize PCI radeon 9200 SE Helge Hafting
2005-01-13 11:00 ` John covici
2005-01-13 21:06 ` Dave Airlie
2005-01-15 18:57 ` Helge Hafting
2005-01-16 10:08 ` Dave Airlie
2005-01-16 10:33 ` Jon Smirl [this message]
2005-01-16 10:37 ` Dave Airlie
2005-01-16 10:35 ` Jon Smirl
2005-01-16 10:50 ` Helge Hafting
2005-01-16 11:04 ` Jon Smirl
2005-01-16 11:07 ` Dave Airlie
2005-01-16 11:34 ` Jon Smirl
2005-01-16 11:41 ` Dave Airlie
2005-01-21 18:26 ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Helge Hafting
2005-01-21 18:49 ` John covici
2005-01-16 12:26 ` 2.6.10 dies when X tries to initialize PCI radeon 9200 SE John covici
2005-01-16 12:18 ` Helge Hafting
2005-01-16 20:25 ` Mike Houston
2005-01-16 22:08 ` Jon Smirl
2005-01-16 22:24 ` Helge Hafting
2005-01-17 17:19 ` Helge Hafting
2005-01-14 2:20 ` David Lang
2005-01-14 10:35 ` Helge Hafting
2005-01-14 12:41 ` John covici
2005-01-15 8:23 ` Dave Airlie
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=9e473391050116023344a5f954@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@gmail.com \
--cc=covici@ccs.covici.com \
--cc=helgehaf@aitel.hist.no \
--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).