All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Xserver development <xorg@freedesktop.org>,
	fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Who is stomping PCI config space?
Date: Thu, 3 Mar 2005 14:03:43 -0500	[thread overview]
Message-ID: <9e4733910503031103552514b9@mail.gmail.com> (raw)

I have two video cards:
PCI Rage128
AGP Radeon

X is loaded on the Rage128 on VT7
X is not configured to support the radeon

I switch to VT1 and load radeonfb
This works fine.

Now I switch to VT7 and dump PCI config space for the radeon

[root@jonsmirl 0000:01:00.0]# hexdump config >/foo
[root@jonsmirl 0000:01:00.0]# diff /foo /bar
1c1
< 0000000 1002 4966 0080 02b0 0001 0300 4010 0080
---
> 0000000 1002 4966 0083 02b0 0001 0300 4010 0080
4c4
< 0000030 0000 fea0 0058 0000 0000 0000 010b 0008
---
> 0000030 0000 fe90 0058 0000 0000 0000 010b 0008
[root@jonsmirl 0000:01:00.0]#

Somebody is changing PCI command from 83 to 80 and disabling my
radeon's memory and iospace. Who is doing this? It has to be X since
it doesn't happen if I switch to VT6 or VT8.

Why is X mucking with a card it doesn't have a driver loaded for? 
Where is this happening in the X code?

-- 
Jon Smirl
jonsmirl@gmail.com

             reply	other threads:[~2005-03-03 19:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 19:03 Jon Smirl [this message]
2005-03-03 23:07 ` Who is stomping PCI config space? Benjamin Herrenschmidt
2005-03-04  0:15   ` Jon Smirl
2005-03-04  3:03     ` Jon Smirl
2005-03-04  6:40       ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-04 12:07         ` Egbert Eich
2005-03-04 17:35           ` Jon Smirl
2005-03-04 22:42             ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 19:06               ` Egbert Eich
2005-03-05 22:42                 ` Benjamin Herrenschmidt
2005-03-07 11:19                   ` Egbert Eich
2005-03-08  3:21                     ` Benjamin Herrenschmidt
2005-03-05 17:33             ` Egbert Eich
2005-03-04 17:58           ` Jon Smirl
2005-03-04 22:45             ` Benjamin Herrenschmidt
2005-03-05 19:07               ` Egbert Eich
2005-03-05 22:43                 ` Benjamin Herrenschmidt
2005-03-04 22:27           ` Benjamin Herrenschmidt
2005-03-05 18:26             ` Egbert Eich
2005-03-05 22:39               ` Benjamin Herrenschmidt
2005-03-07 11:05                 ` Egbert Eich
2005-03-04 12:02       ` Egbert Eich
2005-03-04 11:25   ` Egbert Eich
2005-03-04 22:16     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 17:36       ` Egbert Eich
2005-03-04 11:12 ` Egbert Eich
2005-03-04 22:51   ` Benjamin Herrenschmidt
     [not found] ` <42278AEC.4080706@dunaweb.hu>
2005-03-04 11:21   ` Egbert Eich

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=9e4733910503031103552514b9@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=xorg@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.