linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] doc: PCI: altera: Fix the 'ranges' property in example
Date: Tue, 5 Jan 2016 01:47:40 +0100	[thread overview]
Message-ID: <201601050147.40997.marex@denx.de> (raw)
In-Reply-To: <1451954745.3051.24.camel@ubuntu>

On Tuesday, January 05, 2016 at 01:45:45 AM, Ley Foon Tan wrote:
> On Mon, 2016-01-04 at 02:12 +0100, Marek Vasut wrote:
> > On Monday, January 04, 2016 at 01:53:22 AM, Ley Foon Tan wrote:
> > > On Mon, 2016-01-04 at 01:37 +0100, Marek Vasut wrote:
> > > > On Monday, January 04, 2016 at 01:10:13 AM, Ley Foon Tan wrote:
> > > > 
> > > > Hi!
> > > > 
> > > > > > > > Well, do you have a good explanation why the system works
> > > > > > > > with this change and doesn't work without it on my design ?
> > > > > > > > I'd really love to understand this.
> > > > > > > 
> > > > > > > Do you modify the driver to setup the translation table?
> > > > > > 
> > > > > > No, I didn't change the driver. What do you refer to please ?
> > > > > 
> > > > > There is Address Translation Table at address offset 0x1000 in the
> > > > > IP.
> > > > 
> > > > Oh, I didn't configure that in any way. Should I or does the driver
> > > > configure it in some way?
> > > > 
> > > > > Do you use the hardware design from the rocketboards.org or your
> > > > > own design?
> > > > 
> > > > I use the one from rocketboards, I just ported it over to the MCVEVK
> > > > (custom cyclone v soc board)
> > > 
> > > You may check again the base addresses use in the MCVEVK board.
> > 
> > The address map is attached ; I don't see anything which would differ
> > from the reference design.
> 
> Address map looks fine.

Well do you have any other idea then ? I guess I should pull out the SOCDK, huh?

> > btw I am honestly surprised that Quartus cannot export the address map
> > into some text file :-(
> 
> There is a *.html file in the generated directory.

Oh, I didn't know that, thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2016-01-05  0:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24  9:45 [PATCH] doc: PCI: altera: Fix the 'ranges' property in example Marek Vasut
2015-12-28  6:56 ` Ley Foon Tan
2015-12-28  7:34   ` Marek Vasut
2015-12-28  7:42     ` Ley Foon Tan
2015-12-28  8:26       ` Marek Vasut
2015-12-29  7:48         ` Ley Foon Tan
2015-12-29 13:33           ` Marek Vasut
2015-12-31  3:09             ` Ley Foon Tan
2015-12-31  9:04               ` Marek Vasut
2016-01-03 23:29                 ` Ley Foon Tan
2016-01-03 23:36                   ` Marek Vasut
2016-01-04  0:10                     ` Ley Foon Tan
2016-01-04  0:37                       ` Marek Vasut
2016-01-04  0:53                         ` Ley Foon Tan
2016-01-04  1:12                           ` Marek Vasut
2016-01-05  0:45                             ` Ley Foon Tan
2016-01-05  0:47                               ` Marek Vasut [this message]
2016-01-05  1:18                                 ` Ley Foon Tan
2016-01-05  1:53                                   ` Marek Vasut
2016-01-05 13:49                                   ` Marek Vasut
2016-01-07  8:56                                     ` Ley Foon Tan
2016-01-07 16:05                                       ` Marek Vasut

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=201601050147.40997.marex@denx.de \
    --to=marex@denx.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).