linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: RE: [PATCH 1/2] Add sysdev/pci_quirks.c file into PowerPCarchitecture with ULI chip quirk functions.
Date: Thu, 02 Aug 2007 11:23:19 +1000	[thread overview]
Message-ID: <1186017799.5495.546.camel@localhost.localdomain> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C74D58E@zch01exm26.fsl.freescale.net>

On Thu, 2007-08-02 at 09:17 +0800, Zhang Wei-r63237 wrote:
> Hi, Ben,
>  
> > 
> > Are we sure that any powerpc machine that uses that ULI chip will need
> > the same quirk setting ?
> > 
> 
> We can ensure current platforms (as far as we know, MPC8544DS and
> MPC8641HPCN) using ULI chips in powerpc of kernel need the same quirk
> setting.
> And we hope to make them more generic. And if there are some different
> setting in the future, we can add special codes.

All right.

Ben.

  reply	other threads:[~2007-08-02  1:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  8:14 [PATCH 0/2] Use common quirks routines for ULI chips Zhang Wei
2007-08-01  8:14 ` [PATCH 1/2] Add sysdev/pci_quirks.c file into PowerPC architecture with ULI chip quirk functions Zhang Wei
2007-08-01  8:14   ` [PATCH 2/2] Remove ULI chip quirks functions from MPC8641HPCN and MPC8544DS boards Zhang Wei
2007-08-01 21:56   ` [PATCH 1/2] Add sysdev/pci_quirks.c file into PowerPC architecture with ULI chip quirk functions Benjamin Herrenschmidt
2007-08-02  1:17     ` [PATCH 1/2] Add sysdev/pci_quirks.c file into PowerPCarchitecture " Zhang Wei-r63237
2007-08-02  1:23       ` Benjamin Herrenschmidt [this message]
2007-08-02  4:29         ` Kumar Gala
2007-08-03  6:32           ` Zang Roy-r61911

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=1186017799.5495.546.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=Wei.Zhang@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).