From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 5/5] x86: Add Intel Cougar Canyon 2 board
Date: Sun, 14 Feb 2016 11:03:27 +0800 [thread overview]
Message-ID: <CAEUhbmWX1qYWVzWx=w2Lk3+PircPTw6fZXAur70Ys2mOMorhbQ@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ0Sd0Pi131nHa2Hu7mVuP6GvM2bAqiHL=rOB1vOm-dShw@mail.gmail.com>
Hi Simon,
On Wed, Feb 10, 2016 at 6:23 AM, Simon Glass <sjg@chromium.org> wrote:
> Hi Bin,
>
> On 5 February 2016 at 23:08, Bin Meng <bmeng.cn@gmail.com> wrote:
>> This adds basic support to Intel Cougar Canyon 2 board, a board
>> based on Chief River platform with an Ivy Bridge processor and
>> a Panther Point chipset.
>>
>> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>> Acked-by: Simon Glass <sjg@chromium.org>
>>
>> ---
>>
>> Changes in v2:
>> - Change include order - <asm/...> go after the normal includes
>> - Use PCH uclass driver and change to use dm pci config APIs
>>
>> arch/x86/cpu/ivybridge/Kconfig | 4 ++
>> arch/x86/dts/Makefile | 1 +
>> arch/x86/dts/cougarcanyon2.dts | 104 ++++++++++++++++++++++++++++++
>> board/intel/Kconfig | 9 +++
>> board/intel/cougarcanyon2/Kconfig | 25 +++++++
>> board/intel/cougarcanyon2/MAINTAINERS | 6 ++
>> board/intel/cougarcanyon2/Makefile | 7 ++
>> board/intel/cougarcanyon2/cougarcanyon2.c | 58 +++++++++++++++++
>> board/intel/cougarcanyon2/start.S | 9 +++
>> configs/cougarcanyon2_defconfig | 21 ++++++
>> include/configs/cougarcanyon2.h | 34 ++++++++++
>> 11 files changed, 278 insertions(+)
>> create mode 100644 arch/x86/dts/cougarcanyon2.dts
>> create mode 100644 board/intel/cougarcanyon2/Kconfig
>> create mode 100644 board/intel/cougarcanyon2/MAINTAINERS
>> create mode 100644 board/intel/cougarcanyon2/Makefile
>> create mode 100644 board/intel/cougarcanyon2/cougarcanyon2.c
>> create mode 100644 board/intel/cougarcanyon2/start.S
>> create mode 100644 configs/cougarcanyon2_defconfig
>> create mode 100644 include/configs/cougarcanyon2.h
>
> Can you update README.x86 to mention this board and how to get the
> required binaries?
>
Sure, will do in v3.
Regards,
Bin
prev parent reply other threads:[~2016-02-14 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 6:08 [U-Boot] [PATCH v2 0/5] x86: ivybridge: Add Intel FSP support Bin Meng
2016-02-06 6:08 ` [U-Boot] [PATCH v2 1/5] x86: ivybridge: Add " Bin Meng
2016-02-06 6:08 ` [U-Boot] [PATCH v2 2/5] superio: Add SMSC SIO1007 driver Bin Meng
2016-02-09 22:23 ` Simon Glass
2016-02-06 6:08 ` [U-Boot] [PATCH v2 3/5] x86: fsp: Make sure HOB list is not overwritten by U-Boot Bin Meng
2016-02-06 6:08 ` [U-Boot] [PATCH v2 4/5] x86: ivybridge: bd82x6x: Support FSP enabled configuration Bin Meng
2016-02-09 22:23 ` Simon Glass
2016-02-06 6:08 ` [U-Boot] [PATCH v2 5/5] x86: Add Intel Cougar Canyon 2 board Bin Meng
2016-02-09 22:23 ` Simon Glass
2016-02-14 3:03 ` Bin Meng [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='CAEUhbmWX1qYWVzWx=w2Lk3+PircPTw6fZXAur70Ys2mOMorhbQ@mail.gmail.com' \
--to=bmeng.cn@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.