From: khalasa@piap.pl (Krzysztof Hałasa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Fixes for CNS3xxx platform
Date: Tue, 16 Sep 2014 12:31:46 +0200 [thread overview]
Message-ID: <m3d2av3lgt.fsf@t19.piap.pl> (raw)
Hi,
1. Fix debug UART.
The debug UART ("earlyprintk") has never worked on this platform. This
should be hardly a surprise, given that the Cavium Econa CNS3xxx CPU has
8250-compatible UARTs (instead of AMBA ports) and the addresses (all the
debug UART code, in fact) seem to be simply copied unchanged from
a random other platform :-)
The patch makes it work.
2. Fix logical PCIe topology.
The CNS3xxx code used a hack which made the kernel "think" that it's not
necessary to go through the root PCIe bridge in order to reach other
PCI(e) devices. This was the source of regression described in
https://lkml.org/lkml/2014/2/28/150 (#2). Broken since v3.12-rc1.
Actually, going through the root bridge is necessary and the patch fixes
this problem.
3. Fix PCIe read size limit.
This fixes a (probably rare) PCI setup bug.
All of this stuff has been tested on Gateworks Laguna platform,
masqueraded as the CNS3xxx devel board, with v3.17-rc5. I guess this is
v3.17 material, though it doesn't make much sense for "stable" branches.
--
Krzysztof Halasa
Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next reply other threads:[~2014-09-16 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 10:31 Krzysztof Hałasa [this message]
2014-09-16 10:35 ` [PATCH 1/3] CNS3xxx: Fix debug UART Krzysztof Hałasa
2014-09-16 10:36 ` [PATCH 2/3] CNS3xxx: Fix logical PCIe topology Krzysztof Hałasa
2014-09-16 10:37 ` [PATCH 3/3] CNS3xxx: Fix PCIe read size limit Krzysztof Hałasa
2014-09-25 21:43 ` [PATCH 0/3] Fixes for CNS3xxx platform Arnd Bergmann
2014-09-29 6:26 ` Krzysztof Hałasa
2014-09-29 6:34 ` Krzysztof Hałasa
2014-09-29 6:32 ` [PATCH 1/3 V2] CNS3xxx: Fix debug UART Krzysztof Hałasa
2014-10-02 14:39 ` Arnd Bergmann
2014-10-03 10:22 ` Krzysztof Hałasa
2014-10-03 14:23 ` Arnd Bergmann
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=m3d2av3lgt.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--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 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.