linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Li Li <r64360@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Wood Scott <scottwood@freescale.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Phillips Kim <Kim.Phillips@freescale.com>,
	Li Tony <Tony.Li@freescale.com>
Subject: Re: [PATCH] powerpc: Add MPC837x PCIE controller RC mode support
Date: Thu, 03 Jan 2008 13:56:16 +0800	[thread overview]
Message-ID: <1199339776.7375.1.camel@Guyver> (raw)
In-Reply-To: <901A2F2F-D072-4F03-AA39-9AB6A56EA635@kernel.crashing.org>

On Wed, 2008-01-02 at 23:23 +0800, Kumar Gala wrote:
> 
> On Jan 2, 2008, at 5:16 AM, Li Li wrote:
> 
> > * The MPC837x PCIE controller hardware resources and SerDes are  
> > initiated in u-boot. 
> > * Merge the MPC837x PCIE code into arch/powerpc/sysdev/fsl_pci.c 
> > * The MPC837x PCIE controller`s configure address bit field is
> uniqe: 
> >       bus number:             bits 31-24 
> >       device number:          bits 23-19 
> >       function number:        bits 18-16 
> >       ext reg number:         bits 11-8 
> >       reg number:             bits 7-2 
> > * Add mpc837x_exclude_device to fixup a controller bug.
> 
> what is the bug that is being worked around?
> 
For Type 0 configure transactions, the PCIE controller do not check the
device number bits and just assume the device number bits are 0.

- tony

  reply	other threads:[~2008-01-03  6:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 11:16 [PATCH] powerpc: Add MPC837x PCIE controller RC mode support Li Li
2008-01-02 11:53 ` Arnd Bergmann
2008-01-03  6:40   ` Li Li
2008-01-03  8:14     ` Arnd Bergmann
2008-01-03  8:31       ` Li Li
2008-01-03 10:14         ` Arnd Bergmann
2008-01-03 10:08           ` Li Li
2008-01-02 15:23 ` Kumar Gala
2008-01-03  5:56   ` Li Li [this message]
2008-01-02 15:51 ` Olof Johansson

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=1199339776.7375.1.camel@Guyver \
    --to=r64360@freescale.com \
    --cc=Kim.Phillips@freescale.com \
    --cc=Tony.Li@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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 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).