From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] arm64: dts: Add a devicetree for the ARMv8 4xA53 4xA57 FVP
Date: Wed, 11 Dec 2013 16:08:53 +0000 [thread overview]
Message-ID: <1386778133.3447.6.camel@linaro1.home> (raw)
In-Reply-To: <20131211150433.GD17681@e106331-lin.cambridge.arm.com>
On Wed, 2013-12-11 at 15:04 +0000, Mark Rutland wrote:
> On Wed, Dec 11, 2013 at 02:11:48PM +0000, Mark Brown wrote:
> > On Wed, Dec 11, 2013 at 01:55:36PM +0000, Mark Rutland wrote:
> > > On Wed, Dec 11, 2013 at 01:13:23PM +0000, Mark Brown wrote:
[...]
> >
> > > > +/ {
> > > > + model = "FVP Base";
> >
> > > FVP Base (is as the name implies) a base upon which particular model
> > > instances are built. This name should be clarified (e.g. "FVP Base A57x4
> > > A53x4").
> >
> > > That also applies to the filename.
> >
> > I can update these, though they do seem to come from what you guys are
> > releasing - you might want to follow up on this internally (this applies
> > to almost all of your review comments, sorry). It's probably going to
> > be a bit confusing for users to have the filename change but ho hum :/
>
> I'll try to chase up the issues, thanks for making me aware.
>
> I don't see the name issue as a big problem. This DT has never been part
> of the kernel tree, so there's no filename compatibility issue to deal
> with. Existing users of the DT will already have to be modified to get
> the DTs from a new source.
>
> There should be nothing hanging off the compatible string for the
> platform yet -- we have no board files or platform blobs in the arm64
> port. If the model name is being used as anything other than a handy
> indicator to users, then that's broken anyway.
I believe Android uses model names to determine the filenames of init
scripts to run. That's not a kernel problem, but thought I would point
out one 'broken' use that I have first hand experience of, having been
tripped up before by ARM's twice yearly lets-rename-everything-again
exercise ;-)
--
Tixy
next prev parent reply other threads:[~2013-12-11 16:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 13:13 [PATCH 1/6] arm64: Add asm/cpu.h Mark Brown
2013-12-11 13:13 ` [PATCH 2/6] arm64: dts: Add a virtio disk to the RTSM motherboard Mark Brown
2013-12-11 13:13 ` [PATCH 3/6] arm64: dts: Add a devicetree for the ARMv8 4xA53 4xA57 FVP Mark Brown
2013-12-11 13:55 ` Mark Rutland
2013-12-11 14:11 ` Mark Brown
2013-12-11 15:04 ` Mark Rutland
2013-12-11 16:00 ` Mark Brown
2013-12-11 16:08 ` Jon Medhurst (Tixy) [this message]
2013-12-11 16:41 ` Ryan Harkin
2013-12-11 17:09 ` Mark Rutland
2013-12-11 17:50 ` Mark Brown
2013-12-11 13:13 ` [PATCH 4/6] arm64: topology: Implement basic CPU topology support Mark Brown
2013-12-11 14:12 ` Will Deacon
2013-12-11 14:15 ` Mark Brown
2013-12-11 14:24 ` Catalin Marinas
2013-12-11 14:30 ` Mark Brown
2013-12-11 14:49 ` Catalin Marinas
2013-12-11 16:13 ` Mark Brown
2013-12-12 6:59 ` Hanjun Guo
2013-12-12 10:27 ` Mark Brown
2013-12-12 11:22 ` Hanjun Guo
2013-12-16 10:57 ` Lorenzo Pieralisi
2013-12-16 11:33 ` Mark Brown
2013-12-16 12:29 ` Mark Brown
2013-12-16 14:46 ` Lorenzo Pieralisi
2013-12-16 15:12 ` Mark Brown
2013-12-17 11:47 ` Catalin Marinas
2013-12-17 12:17 ` Mark Brown
2013-12-16 14:45 ` Alex Shi
2013-12-16 15:22 ` Mark Brown
2013-12-17 7:19 ` Alex Shi
2013-12-17 12:02 ` Mark Brown
2013-12-11 13:13 ` [PATCH 5/6] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2013-12-11 14:47 ` Catalin Marinas
2013-12-11 17:31 ` Mark Brown
2013-12-11 19:27 ` Nicolas Pitre
2013-12-12 11:56 ` Morten Rasmussen
2013-12-12 12:22 ` Mark Brown
2013-12-12 13:42 ` Morten Rasmussen
2013-12-12 14:26 ` Vincent Guittot
2013-12-11 13:13 ` [PATCH 6/6] arm64: dts: Add CPU topology properties for ARMv8 4xA53 4xA57 FVP Mark Brown
2013-12-11 14:10 ` [PATCH 1/6] arm64: Add asm/cpu.h Catalin Marinas
2013-12-11 14:23 ` Mark Brown
2013-12-11 14:27 ` Catalin Marinas
2013-12-12 6:50 ` Hanjun Guo
2013-12-12 10:36 ` Mark Rutland
2013-12-12 11:20 ` Hanjun Guo
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=1386778133.3447.6.camel@linaro1.home \
--to=tixy@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).