From: David Daney <ddaney@caviumnetworks.com>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: Jonas Gorski <jogo@openwrt.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Olof Johansson <olof@lixom.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Kumar Gala <galak@codeaurora.org>,
Ralf Baechle <ralf@linux-mips.org>,
David Daney <david.daney@cavium.com>,
Rob Herring <robh+dt@kernel.org>,
Linux-MIPS <linux-mips@linux-mips.org>,
Qais Yousef <qais.yousef@imgtec.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
John Crispin <blogic@openwrt.org>,
Mark Rutland <mark.rutland@arm.com>,
Jayachandran C <jchandra@broadcom.com>,
Paul Burton <paul.burton@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/7] MIPS: Move device-tree files to a common location
Date: Wed, 27 Aug 2014 12:33:35 -0700 [thread overview]
Message-ID: <53FE328F.5040204@caviumnetworks.com> (raw)
In-Reply-To: <CAL1qeaFTw=0XMEkag1Z8C4jKkWnwBeGJLYxHGiYfKXBk-9o0Yw@mail.gmail.com>
On 08/27/2014 11:30 AM, Andrew Bresticker wrote:
> On Mon, Aug 25, 2014 at 8:17 AM, Jonas Gorski <jogo@openwrt.org> wrote:
>> On Sat, Aug 23, 2014 at 9:50 PM, Geert Uytterhoeven
>> <geert@linux-m68k.org> wrote:
>>> On Sat, Aug 23, 2014 at 8:31 AM, Olof Johansson <olof@lixom.net> wrote:
>>>>>> arch/arm/boot/dts/<vendor>/
>>>>>>
>>>>>> Is this something we should do for the MIPS and update the other architectures
>>>>>> to follow that scheme?
>>>>>
>>>>> I recall reading that as well and that it would be adopted for ARM64,
>>>>> but that hasn't seemed to have happened. Perhaps Olof (CC'ed) will no
>>>>> more.
>>>>
>>>> Yeah, I highly recommend having a directory per vendor. We didn't on ARM,
>>>> and the amount of files in that directory is becoming pretty
>>>> insane. Moving to a subdirectory structure later gets messy which is
>>>> why we've been holding off on it.
>>>
>>> It would mean we can change our scripts to operate on "interesting"
>>> DTS files from
>>>
>>> do-something-with $(git grep -l $vendor, -- arch/arm/boot/dts)
>>>
>>> to
>>>
>>> do-something-with arch/arm/boot/dts/$vendor/*
>>>
>>> which is easier to type...
>>
>> Btw, do you mean chip-vendor or device-vendor with vendor?
>> Device-vendor could get a bit messy on the source part as the router
>> manufacturers tend to switch them quite often. E.g. d-link used arm,
>> mips and ubi32 chips from marvell, ubicom, broadcom, atheros, realtek
>> and ralink for their dir-615 router, happily switching back and forth.
>> There are 14 known different hardware revisions of it where the chip
>> differed from the previous one.
>
> I'm going to assume it means chip/SoC vendor. That would result in
> the following structure (I think):
>
> Octeon -> cavium/
To match the state of the art naming we have in other MIPS related
directories, it should probably be "cavium-octeon/" (See
arch/mips/cavium-octeon, and arch/mips/include/asm/mach-cavium-octeon)
David Daney
next prev parent reply other threads:[~2014-08-27 19:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 20:04 [PATCH 0/7] MIPS: Move device-tree files to a common location Andrew Bresticker
2014-08-21 20:04 ` [PATCH 1/7] MIPS: Create common infrastructure for building built-in device-trees Andrew Bresticker
2014-08-21 20:04 ` [PATCH 2/7] MIPS: Add support for building device-tree binaries Andrew Bresticker
2014-08-21 20:04 ` [PATCH 3/7] MIPS: Octeon: Move device-trees to arch/mips/boot/dts/ Andrew Bresticker
2014-08-21 20:04 ` [PATCH 4/7] MIPS: Lantiq: " Andrew Bresticker
2014-08-21 20:04 ` [PATCH 5/7] MIPS: sead3: " Andrew Bresticker
2014-08-21 20:04 ` [PATCH 6/7] MIPS: Netlogic: " Andrew Bresticker
2014-08-21 20:04 ` [PATCH 7/7] MIPS: ralink: " Andrew Bresticker
[not found] ` <CAGVrzcZobuL4z0WNX+Sz4p_uwaPL-S5yvEmgRUwZPJi4+qq0tg@mail.gmail.com>
2014-08-22 20:57 ` [PATCH 0/7] MIPS: Move device-tree files to a common location David Daney
2014-08-22 22:10 ` Andrew Bresticker
2014-08-22 23:16 ` Jonas Gorski
2014-08-23 0:24 ` Andrew Bresticker
2014-08-22 21:10 ` Andrew Bresticker
2014-08-23 6:31 ` Olof Johansson
2014-08-23 13:56 ` Arnd Bergmann
2014-08-23 14:48 ` Jonas Gorski
2014-08-23 14:59 ` Arnd Bergmann
2014-08-23 16:14 ` Olof Johansson
2014-08-24 23:43 ` Rob Herring
2014-08-25 8:12 ` Arnd Bergmann
2014-08-25 14:49 ` Ralf Baechle
2014-08-23 19:50 ` Geert Uytterhoeven
2014-08-25 15:17 ` Jonas Gorski
2014-08-25 15:26 ` Geert Uytterhoeven
2014-08-27 18:30 ` Andrew Bresticker
2014-08-27 19:33 ` David Daney [this message]
2014-08-28 15:04 ` Rob Herring
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=53FE328F.5040204@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=abrestic@chromium.org \
--cc=blogic@openwrt.org \
--cc=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=james.hogan@imgtec.com \
--cc=jchandra@broadcom.com \
--cc=jogo@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=paul.burton@imgtec.com \
--cc=pawel.moll@arm.com \
--cc=qais.yousef@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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