Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andreas Seltenreich <s_selten@informatik.uni-karlsruhe.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: partial success with matroxfb
Date: Fri, 20 Sep 2002 12:11:21 +0200	[thread overview]
Message-ID: <251F50824F2@vcnet.vc.cvut.cz> (raw)

On 20 Sep 02 at 2:27, Andreas Seltenreich wrote:

> Bus    HPA       Module Type      Path  Slt Md Sev  Estat Requestor  Responder
> --- ---------- ---------------- -------- -- -- ---- ----- ---------- ----------
>  0  0xfff88000 I/O Adapter      8         2  0  he   0x3d 0xf2000000 0x000a1000 
>  0  0xfff8a000 I/O Adapter      10        2  2  he   0x0d 0x00000000 0x00000000 

> anotherhpmachien:~# cat /proc/iomem 
> 00000000-0fffffff : System RAM
> f2000000-f3ffffff : GSC Bus [8/]

Hi Andreas,
  boot with 'video=matrox:novga'. It looks like that Matrox responded
to the access to legacy VGA region 0xA0000-0xBFFFF. It does not happen
when CPU accesses this memory because of Matrox does not see this access
at all in such situation, because of host bridge directs it immediately 
to the system ram, without accessing PCI. But when access originated from 
some PCI busmaster, other PCI devices sees this access, and Mystique
claims it.

  And now both host bridge (for system RAM) and Mystique (for VGA region)
accepted bus cycle, and hardware went mad...

  I have no idea what second error reports, but it may be just triggered
by previous one.
                                                            Petr Vandrovec
                                                            

             reply	other threads:[~2002-09-20 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 10:11 Petr Vandrovec [this message]
2002-09-20 15:50 ` [parisc-linux] Re: partial success with matroxfb Andreas Seltenreich
  -- strict thread matches above, loose matches on Subject: below --
2002-09-20 16:10 Petr Vandrovec
2002-09-20 16:59 ` Andreas Seltenreich

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=251F50824F2@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=s_selten@informatik.uni-karlsruhe.de \
    /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