From: Thierry Reding <thierry.reding@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 0/3] tegra2: Add paz00 support
Date: Sun, 20 Nov 2011 13:05:58 +0100 [thread overview]
Message-ID: <20111120120558.GA9653@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1321735649-27138-1-git-send-email-swarren@nvidia.com>
* Stephen Warren wrote:
> This patch series adds support for the Toshiba AC100 Tegra netbook.
>
> I'm posting it as an RFC because:
>
> a) The AC100 is designed by Compal and marketed by Toshiba. Should we put
> the files into board/nvidia (since it uses an NVIDIA SoC), or create a
> board/toshiba or board/compal directory to contain this?
I don't think it should go into board/nvidia. Directories below board are
supposed to be vendor directories and NVIDIA isn't the vendor of the AC100.
I have a slight tendency for preferring toshiba over compal mostly because I
think that's what people will be looking for first.
Thierry
> b) It'll need rebasing on top of some of the many outstanding Tegra
> patches before it can be applied.
>
> Stephen Warren (3):
> MAINTAINERS: Fix my email address
> tegra2: Fix conflicting pinmux for UARTA
> tegra2: Add support for Paz00 (Toshiba AC100)
>
> MAINTAINERS | 3 +-
> board/nvidia/common/board.c | 12 ++++++
> board/nvidia/paz00/Makefile | 49 ++++++++++++++++++++++++
> board/nvidia/paz00/paz00.c | 88 +++++++++++++++++++++++++++++++++++++++++++
> boards.cfg | 1 +
> include/configs/paz00.h | 59 +++++++++++++++++++++++++++++
> 6 files changed, 211 insertions(+), 1 deletions(-)
> create mode 100644 board/nvidia/paz00/Makefile
> create mode 100644 board/nvidia/paz00/paz00.c
> create mode 100644 include/configs/paz00.h
>
> --
> 1.7.5.4
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111120/95c5cf06/attachment.pgp>
next prev parent reply other threads:[~2011-11-20 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:47 [U-Boot] [RFC PATCH 0/3] tegra2: Add paz00 support Stephen Warren
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 1/3] MAINTAINERS: Fix my email address Stephen Warren
2011-11-28 18:58 ` Wolfgang Denk
2011-11-28 19:01 ` Wolfgang Denk
2011-11-28 19:34 ` Stephen Warren
2011-11-28 19:41 ` Wolfgang Denk
2011-11-28 19:45 ` Stephen Warren
2011-11-28 20:39 ` Wolfgang Denk
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 2/3] tegra2: Fix conflicting pinmux for UARTA Stephen Warren
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 3/3] tegra2: Add support for Paz00 (Toshiba AC100) Stephen Warren
2011-11-20 12:10 ` Thierry Reding
2011-11-20 17:39 ` Marc Dietrich
2011-11-21 16:46 ` Stephen Warren
2011-11-20 12:05 ` Thierry Reding [this message]
2011-11-20 17:45 ` [U-Boot] [RFC PATCH 0/3] tegra2: Add paz00 support Marc Dietrich
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=20111120120558.GA9653@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--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