From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andreas Seltenreich <s_selten@informatik.uni-karlsruhe.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: partial success with matroxfb
Date: Fri, 20 Sep 2002 18:10:52 +0200 [thread overview]
Message-ID: <257F2C27A66@vcnet.vc.cvut.cz> (raw)
On 20 Sep 02 at 17:50, Andreas Seltenreich wrote:
> * Petr Vandrovec <VANDROVE@vc.cvut.cz> [2002-09-20 12:12]:
> > boot with 'video=matrox:novga'. It looks like that Matrox responded
>
> No success with novga or no_pci_retry either. It results in the same crash.
Can you verify (with lspci -xxx) that PCI dword register 0x40 in matroxfb
configuration space has not set bit 8 (it is lowest bit in register
0x41). 0=>disable legacy VGA, 1=>enable legacy VGA. Old Millennium I
always responded to framebuffer accesses, and it was fixed in Millennium II.
I thought that it was fixed in Mystique too. You can fix it with
setpci, if matroxfb gets it wrong.
> > Can you print DAC registers 0x4C,0x4D,0x4E,0x4F after this message?
> > 0x4C..0x4E should contain 8,7E,3, and 0x4F should contain 0 when
> > PLL is not locked, and 0x40 if PLL is locked.
>
> Ok, the code around the message now looks like this:
> DAC register 4c=8
> DAC register 4d=7e
> DAC register 4e=1f
> DAC register 4f=0
Strange. Stalls it for 5 seconds here, or goes it through immediately?
> DAC register 4c=8
> DAC register 4d=7e
> DAC register 4e=1f
> DAC register 4f=40
Petr
next reply other threads:[~2002-09-20 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 16:10 Petr Vandrovec [this message]
2002-09-20 16:59 ` [parisc-linux] Re: partial success with matroxfb Andreas Seltenreich
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 10:11 Petr Vandrovec
2002-09-20 15:50 ` 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=257F2C27A66@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