All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hao <haokexin@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc <linuxppc-dev@lists.ozlabs.org>, Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board
Date: Sun, 28 Jul 2013 08:32:21 +0800	[thread overview]
Message-ID: <20130728003221.GA7396@pek-khao-d1.corp.ad.wrs.com> (raw)
In-Reply-To: <1374878624.30721.33@snotra>

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

On Fri, Jul 26, 2013 at 05:43:44PM -0500, Scott Wood wrote:
> On 07/25/2013 07:54:53 AM, Kevin Hao wrote:
> >The reason is that the ppc kernel assume that the BARs starting
> >at 0 is unset and will reassign it later. There is a bug in the
> >previous
> >kernel, so the kernel maybe not work well for qemu in this case. But I
> >think this has been fixed by the commit c5df457f (powerpc/pci:
> >Check the
> >bus address instead of resource address in pcibios_fixup_resources).
> 
> What ensures that the reassignment will not assign zero?

In function pcibios_resource_survey() we will reserve the low IO area
before reassignment. Please see the following comments and codes in this
function.

        /* Before we start assigning unassigned resource, we try to reserve
         * the low IO area and the VGA memory area if they intersect the
         * bus available resources to avoid allocating things on top of them
         */
        if (!pci_has_flag(PCI_PROBE_ONLY)) {
                list_for_each_entry(b, &pci_root_buses, node)
                        pcibios_reserve_legacy_regions(b);
        }    


Thanks,
Kevin

> 
> I'm not doubting the result that it does, but I'm having a hard time
> seeing it in the code.
> 
> Or are you saying that the resource assignment code will run twice,
> rather than just saying that we won't trust the firmware when we
> find zero?
> 
> -Scott

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-07-28  0:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 12:04 [PATCH 0/3] several cleanup patches for fsl pci Kevin Hao
2013-05-21 12:04 ` [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board Kevin Hao
2013-05-28 22:52   ` Scott Wood
2013-05-30 10:20     ` Kevin Hao
2013-05-30 18:54       ` Scott Wood
2013-05-31  6:41         ` Kevin Hao
2013-05-31 10:11           ` Benjamin Herrenschmidt
2013-06-01 10:59             ` Kevin Hao
2013-06-01 11:47               ` Benjamin Herrenschmidt
2013-06-02  0:07                 ` Kevin Hao
2013-06-03 16:42                   ` Scott Wood
2013-06-07  2:00                     ` Kevin Hao
2013-06-08  0:00                       ` Scott Wood
2013-07-23 22:31                       ` Scott Wood
2013-07-25 12:54                         ` Kevin Hao
2013-07-26 22:43                           ` Scott Wood
2013-07-28  0:32                             ` Kevin Hao [this message]
2013-05-31  6:43         ` Kevin Hao
2013-05-31 23:27           ` Scott Wood
2013-06-01 11:13             ` Kevin Hao
2013-05-21 12:04 ` [PATCH 2/3] powerpc/fsl-pci: fix the unreachable warning message Kevin Hao
2013-05-21 12:05 ` [PATCH 3/3] powerpc/fsl-pci: enable SWIOTLB in function setup_pci_atmu Kevin Hao

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=20130728003221.GA7396@pek-khao-d1.corp.ad.wrs.com \
    --to=haokexin@gmail.com \
    --cc=agraf@suse.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    /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.