linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/9] [POWERPC] mv64x60: change FDT compatible prefix to mrvl
Date: Tue, 1 Apr 2008 12:53:42 +1100	[thread overview]
Message-ID: <20080401015342.GB32615@localhost.localdomain> (raw)
In-Reply-To: <20080331165605.GD13750@farnsworth.org>

On Mon, Mar 31, 2008 at 09:56:05AM -0700, Dale Farnsworth wrote:
> On Mon, Mar 31, 2008 at 10:44:20AM +1100, David Gibson wrote:
> > On Fri, Mar 28, 2008 at 05:47:25PM -0600, Grant Likely wrote:
> > > On Fri, Mar 28, 2008 at 5:42 PM, Dale Farnsworth <dale@farnsworth.org> wrote:
> > > > From: Dale Farnsworth <dale@farnsworth.org>
> > > >
> > > >  Follow the convention that compatible names are prefixed by the
> > > >  vendor's stock ticker symbol.  For Marvell Technology Group Ltd.,
> > > >  that's MRVL.
> > > >
> > > >  Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
> > > >  Acked-by: Mark A. Greer <mgreer@mvista.com>
> > > 
> > > Are there any boards "in the wild" using the old string?  If so are
> > > does changing this string risk complicating upgrades to a new kernel
> > > version?
> > 
> > In particular are there any pre-flattened-tree real-OF systems in the
> > wild using "marvell" as the vendor prefix (there might be Apple or IBM
> > systems out there with Marvell PHYs for example).
> 
> It's difficult to prove a negative.  However, I've seen no evidence of
> such systems.  When Mark invented the "marvell," prefix, it wasn't based
> on existing practice.
> 
> However, I believe that the Genesi Pegasos board uses OF and has a
> Marvell bridge chip.  They may have copied the "marvell," prefix.
> 
> Matt, can you check whether any of the Genesi boards contain device node
> descriptions for the Marvel 64[34]60, and let us know what prefix is used
> in their compatible properties?

Ok, fair enough.  As long as you've been duly diligent about checking
for existing practice I'm happy.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2008-04-01  1:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 23:39 [PATCH 0/9] powerpc: mv64x60 and prpmc2800 DTS cleanups Dale Farnsworth
2008-03-28 23:42 ` [PATCH 1/9] [POWERPC] mv64x60: change FDT compatible prefix to mrvl Dale Farnsworth
2008-03-28 23:47   ` Grant Likely
2008-03-29  0:00     ` Dale Farnsworth
2008-03-29  0:12       ` Grant Likely
2008-03-30 23:44     ` David Gibson
2008-03-31 16:56       ` Dale Farnsworth
2008-04-01  1:53         ` David Gibson [this message]
2008-03-28 23:44 ` [PATCH 2/9] [POWERPC] prpmc2800: convert DTS to v1 and add labels Dale Farnsworth
2008-03-28 23:45 ` [PATCH 3/9] [POWERPC] prpmc2800: fix frequencies in prpmc2800.dts Dale Farnsworth
2008-03-28 23:47 ` [PATCH 4/9] [POWERPC] mv64x60: Fix FDT compatible names: mv64x60 => mv64360 Dale Farnsworth
2008-03-29 21:57   ` Olof Johansson
2008-03-30 19:20     ` Segher Boessenkool
2008-03-31 16:33     ` Dale Farnsworth
2008-03-28 23:48 ` [PATCH 5/9] [POWERPC] mv64x60: remove device tree absolute path references Dale Farnsworth
2008-03-28 23:49 ` [PATCH 6/9] [POWERPC] prpmc2800: clean up dts properties Dale Farnsworth
2008-03-29 21:59   ` Olof Johansson
2008-03-30 10:11     ` David Gibson
2008-03-31 16:43       ` Dale Farnsworth
2008-04-01  1:17         ` Segher Boessenkool
2008-04-01  2:22         ` David Gibson
2008-03-28 23:50 ` [PATCH 7/9] [POWERPC] mv643xx_eth: prepare to support multiple silicon blocks Dale Farnsworth
2008-03-28 23:51 ` [PATCH 8/9] [POWERPC] Document the mv64x60 device tree bindings Dale Farnsworth
2008-03-28 23:52 ` [PATCH 9/9] [POWERPC] prpmc2800 needs a dtbImage Dale Farnsworth
2008-03-28 23:56   ` Grant Likely

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=20080401015342.GB32615@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=dale@farnsworth.org \
    --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).