From: Alex Ivanov <gnidorah@p0n4ik.tk>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc List <linux-parisc@vger.kernel.org>
Subject: Re: PCI & AGP video options
Date: Fri, 16 Aug 2013 09:13:48 +0400 [thread overview]
Message-ID: <40141376630028@web3e.yandex.ru> (raw)
In-Reply-To: <BLU0-SMTP848CBA886F0C5E2BB6645697590@phx.gbl>
10.08.2013, 18:07, "John David Anglin" <dave.anglin@bell.net>:
> On 10-Aug-13, at 2:00 AM, gnidorah@p0n4ik.tk wrote:
>
>>> =9AI'm not sure if it makes much sense to use a PA-RISC
>>> =9Amachine as desktop machine nowadays. Every Intel-based
>>> =9Amachine is faster, cheaper, better supported (graphic cards)
>>> =9Aand uses less power...
>> =9AGot your point.
>> =9AThat's true. Still would be nice to use workstation model
>> =9Aas workstation.
>
> Yes, it's a bit of a cop out.
>
> I still tend to think the bug is in the firmware load. =9AIs there an=
y
> external way to confirm that it loads
> correctly (e.g., a led on card)? =9AThe error indicates that the comm=
and
> processor (CP) isn't working.
>
> There is a manual "Radeon R5xx Acceleration" that might help debug.
>
> Dave
> --
> John David Anglin dave.anglin@bell.net
Dave,
=46orgive me for being silent.
Unfortunately, i'm not seeing a presence of any 'works ok' marker.
Thanks for the manual! I've only read a tech note on drm radeon interna=
ls:
http://www.botchco.com/agd5f/?p=3D50
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-08-16 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 11:32 PCI & AGP video options Alex Ivanov
2013-08-09 21:18 ` Helge Deller
2013-08-10 6:00 ` gnidorah
2013-08-10 14:07 ` John David Anglin
2013-08-16 5:13 ` Alex Ivanov [this message]
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=40141376630028@web3e.yandex.ru \
--to=gnidorah@p0n4ik.tk \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@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