From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: orion/kirkwood pcie issue still open with rc6
Date: Mon, 9 Nov 2009 10:06:15 +0100 [thread overview]
Message-ID: <200911091006.15757.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091109094958.4ba72970@marrow.netinsight.se>
Am Montag 09 November 2009 09:49:58 schrieb Simon Kagstrom:
> On Mon, 9 Nov 2009 09:33:46 +0100
> Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:
>
> > Ronan Shitrit from marvell gave me the information to clear bit 2 of physical
> > address 0xf1020100 to enable bus scanning.
> > I don't know what this really does but it helped to get my kernel up and running.
>
> You have that in the functional specification for the kirkwood
> processors:
>
> http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
>
> See Appendix A for the register set and lookup address 0x20100 (the CPU
> configuration register). Bit 2 in that register turns on/off error
> propagation:
>
> Mbus-L Error propogation
> For a list of errors see "Error Handling".
> 0 = NoErrProp: Error indications are not propagated to Mbus-L. The
> transactions are completed normally.
> 1 = ErrProp: Error indications are propagated to Mbus-L.
>
> and clearing it sounds quite a bit like hiding the real problem :-).
>
I've seen this and you're absolutely right. Thats why I've posted!
>
> Probably it's best to try to find out what's causing this error (see
> the Error Handling section of the PCIe chapter in the reference manual
> above) so that that a proper fix can be implemented!
And here my problems are starting ;)
How can I implement error handling for that kind of reported errors?
I'm sorry but I've absolutely no idea.
>
> // Simon
Many thanks,
Dieter
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2009-11-09 9:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 8:33 orion/kirkwood pcie issue still open with rc6 Dieter Kiermaier
2009-11-09 8:49 ` Simon Kagstrom
2009-11-09 9:06 ` Dieter Kiermaier [this message]
2009-11-10 15:26 ` Ronen Shitrit
2009-11-11 14:29 ` orion/kirkwood pcie issue still open with 2.6.32-rc6 (marvell stock 2.6.22.18 works!) Dieter Kiermaier
2009-11-11 15:21 ` Lennert Buytenhek
2009-11-11 16:43 ` Dieter Kiermaier
2009-11-11 16:59 ` Lennert Buytenhek
2009-11-11 17:18 ` Dieter Kiermaier
2009-11-11 16:50 ` Dieter Kiermaier
2009-11-11 16:53 ` Lennert Buytenhek
2009-11-11 17:11 ` Dieter Kiermaier
2009-11-11 17:19 ` Lennert Buytenhek
2009-11-11 17:46 ` Dieter Kiermaier
2009-11-12 1:35 ` [PATCH] ARM: enable PCI bridges after assigning resources (was orion/kirkwood pcie issue still open with 2.6.32-rc6 (marvell stock 2.6.22.18 works!)) Maxime Bizon
2009-11-12 7:23 ` Dieter Kiermaier
2009-11-12 7:31 ` Simon Kagstrom
2009-11-12 7:42 ` Dieter Kiermaier
2009-11-12 19:56 ` Lennert Buytenhek
2009-11-13 14:35 ` Maxime Bizon
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=200911091006.15757.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).