From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm/dt: tegra: add dts file for paz00
Date: Wed, 26 Oct 2011 22:18:55 +0200 [thread overview]
Message-ID: <24453918.Ulhj1xIogt@ax5200p> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173E1B4536@HQMAIL01.nvidia.com>
On Tuesday 25 October 2011 23:43:06 Stephen Warren wrote:
> Marc Dietrich wrote at Tuesday, October 25, 2011 1:05 PM:
> > On Monday 24 October 2011 22:16:15 Stephen Warren wrote:
> > > Marc Dietrich wrote at Saturday, October 22, 2011 2:17 PM:
> > > > * NOT FOR COMMIT *
> > > >
> > > > This just adds the dts for paz00. I like to add it to board-dt
> > > > as
> > > > well as soon as I find out which tree to base it on.
> > >
> > > ...
> > >
> > > > +++ b/arch/arm/boot/dts/tegra-paz00.dts
> > >
> > > One thing that cross my mind when writing the TrimSlice support and
> > > I
> > > forgot to mention: Should these files be named ${soc}-${board}.dts
> > > or
> > > ${vendor}-${board}.dts (tegra-paz00.dts or toshiba-paz00.dts or
> > > compal-paz00.dts). I'm OK either way; just want to follow any
> > > outside
> > > expectations.
> >
> > I also don't know. I prefer compal for paz00 because Toshiba's code name
> > was procyon (I think) and I don't want to change all the naming. Also
> > Toshiba showed no interest in helping us, so I don't see why they
> > should get the fame.
> Well, it's more about correctly defining what the HW is than advertising,
> fame, or support!
define "what the HW is". Warning: the following list is purely fictitious. Any
similarities between the companies or products mentiond, real or imaginary,
are coincidental.
- company A creates a cpu (only the IP) and license it to company N.
- company N adds some more stuff around it (interfaces, gpu, ...) and
creates real cpu hw.
- company T likes the cpu and asks company C to build a computer around it
- company C takes the evaluation board from company N, modifies it a bit,
and builds a whole netbook around it
- company T gets the netbook from company C and adds a operating system
which will displeased their customers
So how would you define that hw? Or the real question, who made it? And please
don't take my second argument too serious. I just expressed my anger in an
improper way at an improper place. Sorry for that.
Marc
next prev parent reply other threads:[~2011-10-26 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1319313019.git.marvin24@gmx.de>
[not found] ` <90ee88bcde84141e0280ffa4ccbd288462489eba.1319313020.git.marvin24@gmx.de>
2011-10-25 5:16 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Stephen Warren
2011-10-25 19:05 ` Marc Dietrich
2011-10-26 6:43 ` Stephen Warren
2011-10-26 20:18 ` Marc Dietrich [this message]
2011-10-25 19:51 ` Rob Herring
2011-10-26 6:40 ` Stephen Warren
2011-10-31 19:58 [PATCH v3 0/3] paz00 updates for 3.3 Marc Dietrich
2011-10-31 19:58 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Marc Dietrich
2011-10-31 20:14 ` Stephen Warren
2011-10-31 22:20 ` Marc Dietrich
-- strict thread matches above, loose matches on Subject: below --
2011-11-01 20:37 [PATCH v4 0/3] paz00 updates for 3.3 Marc Dietrich
2011-11-01 20:37 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Marc Dietrich
2011-11-01 22:37 ` Stephen Warren
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=24453918.Ulhj1xIogt@ax5200p \
--to=marvin24@gmx.de \
--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).