[Top] [All Lists]

Re: [PATCH] OF: MIPS: sead3: Implement OF support.

To: Ralf Baechle <>
Subject: Re: [PATCH] OF: MIPS: sead3: Implement OF support.
From: Florian Fainelli <>
Date: Wed, 12 Dec 2012 16:01:59 +0100
Cc: Lars-Peter Clausen <>, "Steven J. Hill" <>,
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UhJPmKxXUfPQv8cRkaK6ZaWphfGH1Z0vKVeUBUwUw/Q=; b=z75k6nBsXv3L0gInj0WiZpONVYw2xF6jAQdzeCf7EfLlkR7fb7p7Tk6np4kwgeC6W9 eRMXeBhW628WpxKSVBEJah7+yTDMPNmGoXHjHj8FofnqwKTAZQTCVLHg5pOKbbaUwZO4 a9GIWd3DM9JS3tfLHzFo0/K6TrlP85h2OA7PEFuFs+2DP29TDBX6VMVtyQb1eSEpJnm6 kHS43cugQcRSYyHz6T3uIfHBHovBTVVCyhUcjcvApdSuR7rLZBDun4VU3nF2wULzXRuo Nt4M2ZcqOcRyUzH2uhGcxoZxkAr6O9CwdbwwYPVZ/jSBViwuFVEsZEAnLW8qhEgzHZLY wmvQ==
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Organization: OpenWrt
References: <> <> <> <>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
Le 12/12/12 15:55, Ralf Baechle a écrit :
On Wed, Dec 12, 2012 at 03:53:32PM +0100, Lars-Peter Clausen wrote:

This is one compatible string though, what you describe is for when use
multiple compatible string. E.g.
compatible = "mips14KEc", "mips14Kc", "mips";

The "mips" in Stevens patch is probably the vendor prefix. Maybe a more
correct compatible would be.
How about using something like mti (for MIPS Technologies, Inc.) instead
of MIPS to differenciate the architecture from the company name?

The convention for vendor prefixes is to use the stock exchange prefix, giving us "mips". The same problem exist for ARM Ltd. vs architecture and they use "arm" as a prefix unconditionaly.

<Prev in Thread] Current Thread [Next in Thread>