From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/3] [POWERPC] Add pci node to sequoia dts
Date: Mon, 27 Aug 2007 08:38:48 +0200 [thread overview]
Message-ID: <200708270838.48675.sr@denx.de> (raw)
In-Reply-To: <20070827062135.GC7306@localhost.localdomain>
On Monday 27 August 2007, David Gibson wrote:
> On Mon, Aug 27, 2007 at 08:07:17AM +0200, Stefan Roese wrote:
> [snip]
>
> > > I usually put device_type, compatible and reg at the top of the block,
> > > to announce what the node actually is before giving all the details.
> > >
> > > Also, apart from the stray space in the compatible, I'm guessing that
> > > the 440EPx bridge is actually more-or-less like the PCI bridges on
> > > other 4xx chips, so we should have a more general compatible string
> > > too.
> >
> > Yes, it is "more-or-less" like any other 4xx PCI core. So it really would
> > make sense to define it more generally. Something like:
> >
> > compatible = "ibm,pci-440epx", "ibm,pci4xx";
> >
> > or even:
> >
> > compatible = "ibm,pci-440epx", "ibm,pci";
> >
> > ?
>
> Hrm.. "xx" is ugly, and "ibm,pci" isn't specific enough. I think
> we're better off just using the oldest similar chip. Since this is
> vanilla PCI, I think that makes it "ibm,pci-405gp"
Fine with me.
> > > Is the 440EPx a vanilla PCI or a PCI-X bridge? If the later that
> > > should be reflected in the name and compatible as well.
> >
> > It's a vanilla PCI bridge.
>
> Ok, so it is different from 440GP which is PCI-X.
Yes. There are some common parts (IIRC), but there are differences. Perhaps
both, IBM-PCI and IBM-PCI-X can be integrated into one source too, but I
think we should start with PCI-only right now.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
=====================================================================
next prev parent reply other threads:[~2007-08-27 6:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 9:29 [PATCH 0/3][POWERPC] Add PCI support for 44xEPx Vitaly Bordug
2007-08-25 9:29 ` [PATCH 1/3] [POWERPC] Merge 32 and 64 bit pci_process_bridge_OF_ranges() instances Vitaly Bordug
2007-08-27 1:15 ` David Gibson
2007-08-27 6:31 ` Vitaly Bordug
2007-08-27 7:49 ` David Gibson
2007-08-27 8:31 ` Vitaly Bordug
2007-08-25 9:29 ` [PATCH 2/3] [POWERPC] Add pci node to sequoia dts Vitaly Bordug
2007-08-25 9:49 ` Segher Boessenkool
2007-08-26 10:27 ` Vitaly Bordug
2007-08-26 19:10 ` Segher Boessenkool
2007-08-27 1:55 ` David Gibson
2007-08-25 9:51 ` Segher Boessenkool
2007-08-27 5:56 ` Stefan Roese
2007-08-27 1:54 ` David Gibson
2007-08-27 6:07 ` Stefan Roese
2007-08-27 6:21 ` David Gibson
2007-08-27 6:38 ` Stefan Roese [this message]
2007-08-27 6:50 ` Vitaly Bordug
2007-08-25 9:30 ` [PATCH 3/3] [POWERPC] Add PCI support for AMCC 440EPx (sequoia) Vitaly Bordug
2007-08-27 1:57 ` David Gibson
2007-08-27 6:21 ` Stefan Roese
2007-08-27 17:22 ` Josh Boyer
2007-08-28 0:21 ` David Gibson
2007-08-27 6:55 ` Vitaly Bordug
2007-08-27 8:05 ` Stefan Roese
2007-09-05 17:28 ` Valentine Barshak
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=200708270838.48675.sr@denx.de \
--to=sr@denx.de \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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 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.