From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: tegra: Add e2220-1170 board
Date: Fri, 31 Jul 2015 09:27:47 +0200 [thread overview]
Message-ID: <20150731072746.GA7328@ulmo.nvidia.com> (raw)
In-Reply-To: <55BA6932.5060106@wwwdotorg.org>
On Thu, Jul 30, 2015 at 12:13:06PM -0600, Stephen Warren wrote:
> On 07/29/2015 05:02 PM, Simon Glass wrote:
> >Hi Stephen,
> >
> >On 29 July 2015 at 13:48, Stephen Warren <swarren@wwwdotorg.org> wrote:
> >>
> >
> >Commit message?
>
> I guess I can add one, but there really much useful additional information I
> can give.
>
> I've also been "guilty" of pushing for commit messages for cases like this,
> but I wonder if we shouldn't just consider the commit subject as part of the
> overall description and hence allow empty commit descriptions when they
> won't add anything?
>
> Anyway, since I'm likely to spin the patch for e2220-1170.h at least, I can
> add something.
FWIW, here's the commit message from the Linux kernel commit that I've
queued up for P2371:
arm64: tegra: Add NVIDIA P2371 support
The NVIDIA P2371 is an internal reference design that uses a P2530
compute module hooked up to a P2595 base board and an optional display
module for a 1200x1920 MIPI DSI panel.
and here's the one for P2595:
arm64: tegra: Add NVIDIA P2595 base board support
The NVIDIA P2595 base board is used in several reference designs and
provides the connectors to connect the P2530 compute module to the
outside world. It features a USB 3.0 network adapter, a USB 3.0 port,
an HDMI port, a SATA port, an audio codec, a microSD card slot and a
display connector, among others.
and finally for P2530:
arm64: tegra: Add NVIDIA P2530 compute module support
The NVIDIA P2530 is a compute module used in several reference designs.
It features a Tegra210 SoC, 4 GiB of LPDDR4 RAM, 16 GiB eMMC and various
other essentials. It is typically connected to some base board that
provides the connectors needed to hook it up to the outside world.
This doesn't go into a lot of detail, but I think it's nice to give
people some amount of information about what kind of board this is. It
shows the capabilities, which I think is vital if we want people to
actually use Tegra. With this kind of information people may actually
start being interested in the device. If we don't have any information
at all, people are likely going to ignore the board.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150731/1f529243/attachment.sig>
prev parent reply other threads:[~2015-07-31 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:48 [U-Boot] [PATCH 1/2] ARM: tegra: Add e2220-1170 board Stephen Warren
2015-07-29 19:48 ` [U-Boot] [PATCH 2/2] ARM: tegra: Add p2371-0000 board Stephen Warren
2015-07-29 20:06 ` Tom Warren
2015-07-29 23:02 ` [U-Boot] [PATCH 1/2] ARM: tegra: Add e2220-1170 board Simon Glass
2015-07-30 2:42 ` Tom Warren
2015-07-30 18:03 ` Stephen Warren
2015-07-30 18:11 ` Tom Warren
2015-07-30 18:17 ` Simon Glass
2015-07-30 18:13 ` Stephen Warren
2015-07-30 18:23 ` Simon Glass
2015-07-30 20:05 ` Stephen Warren
2015-07-31 7:27 ` Thierry Reding [this message]
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=20150731072746.GA7328@ulmo.nvidia.com \
--to=treding@nvidia.com \
--cc=u-boot@lists.denx.de \
/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