From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: NSA310 + DT
Date: Fri, 2 Aug 2013 10:46:50 +0200 [thread overview]
Message-ID: <20130802104650.68a13327@skate> (raw)
In-Reply-To: <51FB6F59.4010205@uni-bremen.de>
Dear Finn Hoffmann,
On Fri, 02 Aug 2013 10:35:37 +0200, Finn Hoffmann wrote:
> I just came across one thing. Is it ok that I have different Marvell
> device with patched 3.11.0-rc3?
> With 3.10.2 it has pci id 11ab:6281, with 3.11.0-rc3 and your patch it
> has 11ab:7846.
Yes, this is expected. 3.11-rc uses a completely new PCI driver for
Marvell platforms, that has a proper Device Tree binding. This driver
uses a very different strategy than the old driver in terms of MBus
window configuration, and to achieve this it relies on an emulated
PCI-to-PCI bridge. The numbers you're seeing are the one of the
emulated PCI-to-PCI bridge.
And the patch I've done fixes this PCI-to-PCI bridge emulation. BTW,
I've officially submitted the patch, which has been taken by the PCI
maintainer and will be part of one of the next 3.11-rc, and therefore
of the final 3.11. I mentioned you as Reported-by and thought git
send-email would automatically Cc you on the patch, but it did not.
Thanks again for your report!
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-08-02 8:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51DC564A.8050002@harsszegi.com>
2013-07-09 19:36 ` NSA310 + DT Andrew Lunn
2013-07-09 20:21 ` Andrew Lunn
2013-07-10 0:53 ` tibor at harsszegi.com
2013-07-10 6:23 ` Andrew Lunn
2013-07-10 8:42 ` tibor at harsszegi.com
2013-07-10 13:41 ` Andrew Lunn
[not found] ` <51DD8E8B.2040505@harsszegi.com>
2013-07-10 16:44 ` Tibor Harsszegi
2013-07-10 16:53 ` Andrew Lunn
2013-07-10 16:57 ` Tibor Harsszegi
2013-07-10 17:13 ` Tibor Harsszegi
2013-07-10 17:15 ` Tibor Harsszegi
2013-07-10 17:23 ` Andrew Lunn
2013-07-10 17:29 ` Tibor Harsszegi
2013-07-10 1:01 ` tibor at harsszegi.com
2013-07-10 7:37 ` Andrew Lunn
2013-07-10 8:43 ` tibor at harsszegi.com
[not found] ` <51DEDB32.4080101@harsszegi.com>
2013-07-11 16:44 ` gpio_blink_set + Kirkwood Andrew Lunn
2013-07-11 18:32 ` Tibor Harsszegi
2013-07-11 18:37 ` Jason Cooper
2013-07-11 18:52 ` Tibor Harsszegi
2013-07-11 19:44 ` Jason Cooper
2013-07-29 17:05 ` NSA310 + DT Finn Hoffmann
2013-07-29 19:21 ` Jason Cooper
2013-07-29 20:43 ` Andrew Lunn
[not found] ` <51F78DA6.8010307@uni-bremen.de>
[not found] ` <20130730144752.GR24782@lunn.ch>
[not found] ` <20130730172407.3aab15c6@skate>
[not found] ` <51F7EBB9.7000504@uni-bremen.de>
[not found] ` <20130730191943.49f8070c@skate>
2013-07-30 18:36 ` Andrew Lunn
2013-07-30 19:31 ` Finn Hoffmann
2013-07-30 19:42 ` Andrew Lunn
2013-07-30 21:23 ` Thomas Petazzoni
2013-07-31 9:14 ` Thomas Petazzoni
2013-07-31 9:43 ` Finn Hoffmann
2013-07-31 9:51 ` Thomas Petazzoni
2013-07-31 11:41 ` Finn Hoffmann
2013-07-31 11:47 ` Thomas Petazzoni
2013-07-31 16:45 ` Andrew Lunn
2013-08-01 8:01 ` Finn Hoffmann
2013-08-01 16:04 ` Andrew Lunn
2013-08-01 20:43 ` Finn Hoffmann
2013-08-02 8:35 ` Finn Hoffmann
2013-08-02 8:46 ` Thomas Petazzoni [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=20130802104650.68a13327@skate \
--to=thomas.petazzoni@free-electrons.com \
--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).