From: "Martin K. Petersen" <mkp@mkp.net>
To: Kurt Fitzner <kfitzner@excelcia.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PCI card in C160
Date: Mon, 15 Aug 2005 11:46:50 -0400 [thread overview]
Message-ID: <yq1slxbfbit.fsf@wilson.lab.mkp.net> (raw)
In-Reply-To: <29513.193.160.141.5.1124091800.squirrel@www.puszczka.com> (Andy Walker's message of "Mon, 15 Aug 2005 09:43:20 +0200 (CEST)")
>>>>> "Andy" == Andy Walker <ajwalker@broadpark.no> writes:
Andy> I think HP did this due to bugs in the Dino PCI bridge.
Yup.
Andy> Certain revisions have bugs that will quite likely corrupt data
Andy> on cards that HP haven't certified as working correctly (i.e. HP
Andy> cards are known not to exercise the bugs).
Well. The old rev. Dino does corrupt data (Actually, the HP errata
note is funny. It states that Dino will cause corruption but *only*
when you do I/O through it. Good thing I/O is not something you do on
a regular basis 8).
Anyway. For a graphics card it's not a big deal whether a pixel on
the display gets corrupted. And consequently - as far as I remember -
the firmware will reject anything but Visualize cards.
The solution is to find a new I/O daughterboard on ebay. There's
probably a higher success rate in terms of getting a newer rev. Dino
if you get a board from a scrapped C180/C200/C240. Join the exclusive
circle of Frankenbox owners!
--
Martin K. Petersen http://mkp.net/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-08-15 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 6:28 [parisc-linux] PCI card in C160 Kurt Fitzner
2005-08-15 6:51 ` Max Grabert
2005-08-15 7:43 ` Andy Walker
2005-08-15 15:46 ` Martin K. Petersen [this message]
2005-08-15 7:01 ` Max Grabert
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=yq1slxbfbit.fsf@wilson.lab.mkp.net \
--to=mkp@mkp.net \
--cc=kfitzner@excelcia.org \
--cc=parisc-linux@lists.parisc-linux.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