From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Sven Luther <sven.luther@wanadoo•fr>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
Dale Farnsworth <dale@farnsworth•org>,
sl@bplan-gmbh•de, linuxppc-embedd@ozlabs•org,
Nicolas DET <det.nicolas@free•fr>
Subject: Re: mv643xx_eth SA_SHIRQ support patch
Date: Wed, 09 Mar 2005 18:39:27 +1100 [thread overview]
Message-ID: <1110353967.32524.83.camel@gaston> (raw)
In-Reply-To: <20050309071722.GA25622@pegasos>
On Wed, 2005-03-09 at 08:17 +0100, Sven Luther wrote:
> vendor-id 0x11AB (4523)
> device-id 0x6460 (25696)
> revision-id 0x3 (3)
> class-code 0x60000 (393216)
> subsystem-id 0x0 (0)
> subsystem-vendor-id 0x0 (0)
> .vendor-name "Marvell"
> .part-number "MV6436x"
> .description "System Controller for PowerPC Processors"
> .class "Bridge Device"
> .subclass "Host/PCI"
> devsel-speed 0x0 (0)
> min-grant 0x0 (0)
> max-latency 0x0 (0)
> name "host"
> reg 0:0
> assigned-addresses
Ok, teach them the interest in having a "model" and "compatible"
property in them for their next version...
> In the /pci/host node, i also have :
>
> model "Pegasos2"
>
> In the root node, and in the new OF, we even have a /discovery2/port@1 or
> something such, but it is unreleased yet.
Ugh ? What is that supposed to be ?
If it's an ethernet port, it should be called "ethernet".
> The thing is not that there is no info, just to chose which info is best.
>
> Christoph suggested to not do that though, but use the normal pci stuff and
> match on the host pci id with pci_dev_present. This is what i was thinking of
> doing too, and may be more logical, no ?
Yah, if there is no meaningful OF name, then probably.
Ben.
next prev parent reply other threads:[~2005-03-09 7:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:14 [PATCH][PPC32] mv64x60 updates Mark A. Greer
2005-02-24 8:25 ` Sven Luther
2005-02-24 15:28 ` Mark A. Greer
2005-02-24 16:04 ` Sven Luther
2005-02-24 17:08 ` Mark A. Greer
2005-02-24 17:05 ` Sven Luther
2005-02-24 17:24 ` Dale Farnsworth
2005-03-05 19:27 ` Sven Luther
2005-03-05 20:32 ` Sven Luther
2005-03-05 22:51 ` Dale Farnsworth
2005-03-06 7:02 ` Sven Luther
2005-03-06 10:29 ` Dale Farnsworth
2005-03-06 19:10 ` Sven Luther
2005-03-06 19:48 ` Nicolas DET
2005-03-07 1:00 ` [PATCH][PPC32] " Dale Farnsworth
2005-03-07 6:52 ` Sven Luther
2005-03-07 10:56 ` Nicolas DET
2005-03-07 10:58 ` Nicolas DET
2005-03-07 12:30 ` James Chapman
2005-03-07 12:46 ` Sven Luther
2005-03-07 12:57 ` Nicolas DET
2005-03-07 13:20 ` Sven Luther
2005-03-07 17:24 ` Mark A. Greer
2005-03-07 13:23 ` Linwoes
2005-03-07 22:54 ` mv643xx_eth SA_SHIRQ support patch Dale Farnsworth
2005-03-08 6:49 ` Sven Luther
2005-03-08 7:27 ` Benjamin Herrenschmidt
2005-03-08 12:20 ` Dale Farnsworth
2005-03-08 12:15 ` Sven Luther
2005-03-08 12:42 ` Sven Luther
[not found] ` <20050308164310.GA9891@pegasos>
2005-03-08 22:31 ` Benjamin Herrenschmidt
2005-03-09 7:17 ` Sven Luther
2005-03-09 7:39 ` Benjamin Herrenschmidt [this message]
2005-03-09 7:40 ` Sven Luther
2005-03-08 18:19 ` Mark A. Greer
2005-03-08 18:19 ` Sven Luther
2005-03-08 19:28 ` [PATCH] final mv643xx_eth pegasos patch set Sven Luther
2005-03-08 19:52 ` Sven Luther
2005-03-08 23:18 ` Nicolas DET
2005-03-09 2:03 ` mv64x60 updates Benjamin Herrenschmidt
2005-03-09 2:01 ` Benjamin Herrenschmidt
2005-03-09 15:59 ` Chris Friesen
2005-03-05 21:58 ` [PATCH][PPC32] " Dale Farnsworth
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=1110353967.32524.83.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=dale@farnsworth$(echo .)org \
--cc=det.nicolas@free$(echo .)fr \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc-embedd@ozlabs$(echo .)org \
--cc=sl@bplan-gmbh$(echo .)de \
--cc=sven.luther@wanadoo$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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