mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/15] PCI bridges and Tegra PCI stuff
Date: Thu, 25 Sep 2014 22:46:55 +0200	[thread overview]
Message-ID: <1411678015.2207.2.camel@tellur.intern.lynxeye.de> (raw)
In-Reply-To: <20140925230238.18b41a52be8f3d5cc45d9bc7@gmail.com>

Am Donnerstag, den 25.09.2014, 23:02 +0400 schrieb Antony Pavlov:
> On Thu, 25 Sep 2014 19:04:54 +0200
> Lucas Stach <dev@lynxeye.de> wrote:
> 
> > Ok, I'm sending this out before it gathers any more dust.
> > 
> > This still doesn't work on Tegra K1 and I also haven't got
> > around to finish the rtl8169 network driver, but it seems
> > this pile is already a worthwile improvement.
> > 
> > First 7 patches are general barebox PCI improvements for
> > better tracking of PCI resources and handling bridge setup.
> 
> I have tryed this series.
> 
> I have got several 
>   'BAR does not fit within bus IO res'
> messages on qemu-malta. So not all available pci devices were registered.
> 
I think that's because patch 2 fixes a problem where IO resources would
be populated from the host controllers MEM resource. IO resources are
now properly accounted.

From a quick look at the code it seems you aren't properly assigning the
resource.end for the IO region on malta. Can you please check this?
Otherwise please post the PCI debug messages.

Regards,
Lucas



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-09-25 20:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 17:04 Lucas Stach
2014-09-25 17:04 ` [PATCH 01/15] pci: split out device init Lucas Stach
2014-09-25 17:04 ` [PATCH 02/15] pci: add resource enum Lucas Stach
2014-09-25 17:04 ` [PATCH 03/15] pci: properly populate prefetchable BARs Lucas Stach
2014-09-25 17:04 ` [PATCH 04/15] pci: setup bridges and traverse buses behind them Lucas Stach
2014-09-25 17:04 ` [PATCH 05/15] pci: prettyprint device names Lucas Stach
2014-09-25 17:05 ` [PATCH 06/15] pci: track parent<->child relationship Lucas Stach
2014-09-25 17:05 ` [PATCH 07/15] commands: lspci: go down into subordinate busses Lucas Stach
2014-09-25 17:05 ` [PATCH 08/15] clk: tegra: add PLLE setup functions Lucas Stach
2014-09-25 17:05 ` [PATCH 09/15] clk: tegra30: add PCIe clocks Lucas Stach
2014-09-25 17:05 ` [PATCH 10/15] i2c: tegra: move to fs initcall Lucas Stach
2014-09-25 17:05 ` [PATCH 11/15] ARM: tegra: beaver: enable PEX voltage rail Lucas Stach
2014-09-25 17:05 ` [PATCH 12/15] tegra: pmc: add powerdomain handling Lucas Stach
2014-09-25 17:05 ` [PATCH 13/15] of: import pci range parser from linux Lucas Stach
2014-09-25 17:05 ` [PATCH 14/15] pci: add Tegra host controller driver Lucas Stach
2014-09-25 17:05 ` [PATCH 15/15] ARM: tegra: advertise PCI support Lucas Stach
2014-09-25 19:02 ` [PATCH 00/15] PCI bridges and Tegra PCI stuff Antony Pavlov
2014-09-25 20:46   ` Lucas Stach [this message]
2014-10-01  6:17     ` Sascha Hauer
2014-10-01  7:19       ` Antony Pavlov

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=1411678015.2207.2.camel@tellur.intern.lynxeye.de \
    --to=dev@lynxeye.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@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