From: John David Anglin <dave.anglin@bell.net>
To: Alex Ivanov <gnidorah@p0n4ik.tk>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: parisc debian kernel - missing modules for C8000 - linux-image-3.10-2-parisc64-smp
Date: Thu, 05 Sep 2013 17:35:15 -0400 [thread overview]
Message-ID: <5228F913.4060608@bell.net> (raw)
In-Reply-To: <413F00CF-396F-472B-8476-DF1C4084FA81@p0n4ik.tk>
On 9/5/2013 5:15 PM, Alex Ivanov wrote:
> I've added hex printing in a check and at brief view the output seems to match cp firmware.
> In my case, it's a r420_cp.bin
OK, so the problem is probably not in the firmware load. Maybe it's
the chipset coherency issue mentioned by Helge. This may break ring
test, etc.
Dave
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2013-09-05 21:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <521A7589.5000503@gmx.de>
2013-08-31 17:13 ` parisc debian kernel - missing modules for C8000 - linux-image-3.10-2-parisc64-smp John David Anglin
2013-08-31 17:41 ` John David Anglin
[not found] ` <108451378018002@web28j.yandex.ru>
[not found] ` <BLU0-SMTP1273DDE4A968FD3A43C55D97370@phx.gbl>
2013-09-02 6:43 ` gnidorah
2013-09-02 14:10 ` John David Anglin
2013-09-04 18:34 ` Alex Ivanov
2013-09-04 18:36 ` Alex Ivanov
[not found] ` <52278FBD.2010304@bell.net>
2013-09-04 23:58 ` John David Anglin
2013-09-05 20:58 ` Helge Deller
2013-09-06 8:52 ` Thomas Bogendoerfer
2013-09-06 14:12 ` Alex Ivanov
2013-09-06 14:53 ` Thomas Bogendoerfer
2013-09-06 14:50 ` James Bottomley
2013-09-06 16:11 ` Thomas Bogendoerfer
2013-09-06 17:14 ` James Bottomley
2013-09-07 21:08 ` John David Anglin
2013-09-17 7:23 ` Alex Ivanov
2013-09-05 9:23 ` Alex Ivanov
[not found] ` <BLU0-SMTP629706DAEF1E3714BE163097330@phx.gbl>
2013-09-05 21:15 ` Alex Ivanov
2013-09-05 21:35 ` John David Anglin [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=5228F913.4060608@bell.net \
--to=dave.anglin@bell.net \
--cc=gnidorah@p0n4ik.tk \
--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 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.