From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Add support for the Terasic DE-0 Atlas board
Date: Wed, 2 Sep 2015 10:05:21 +0200 [thread overview]
Message-ID: <201509021005.21485.marex@denx.de> (raw)
In-Reply-To: <CADhT+wfk_h55wji50c1DER_N-HjbbVemQiAw5=ee+3yXicpvHQ@mail.gmail.com>
On Tuesday, September 01, 2015 at 11:37:20 PM, Dinh Nguyen wrote:
> On Tue, Sep 1, 2015 at 10:36 AM, Marek Vasut <marex@denx.de> wrote:
> > On Tuesday, September 01, 2015 at 05:12:40 PM, Dinh Nguyen wrote:
> >> On 09/01/2015 03:33 AM, Marek Vasut wrote:
> >> > On Tuesday, September 01, 2015 at 09:38:23 AM, Pavel Machek wrote:
> >> >> On Tue 2015-09-01 00:23:49, Marek Vasut wrote:
> >> >>> On Monday, August 31, 2015 at 09:57:05 PM,
> >> >>> dinguyen at opensource.altera.com
> >> >
> >> > wrote:
> >> >>>> From: Dinh Nguyen <dinguyen@opensource.altera.com>
> >> >>>>
> >> >>>> Add support for the Terasic DE0-Nano/Atlas-SoC Kit, which is a
> >> >>>> CycloneV based board. The board can boot from SD/MMC. Ethernet is a
> >> >>>> bit different because it has a KSZ9031 PHY, so for now, ethernet
> >> >>>> doesn't quite work yet, as a few patches are needed to support the
> >> >>>> PHY.
> >> >>>
> >> >>> I thought we did support the KSZ9031 PHY. What's the problem ?
> >> >>>
> >> >>>> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> >> >>>> ---
> >> >>>> Hi Marek,
> >> >>>>
> >> >>>> This patch is based on your u-boot-socfpga/wip/boards branch.
> >> >>>
> >> >>> OK, that makes sense.
> >> >>>
> >> >>>> Thanks,
> >> >>>> Dinh
> >> >>>> ---
> >> >>>>
> >> >>>> arch/arm/dts/Makefile | 1 +
> >> >>>> arch/arm/dts/socfpga_cyclone5_de0_sockit.dts | 61 +++
> >> >>>> arch/arm/mach-socfpga/Kconfig | 7 +
> >> >>>> board/terasic/de0/MAINTAINERS | 5 +
> >> >>>> board/terasic/de0/Makefile | 9 +
> >> >>>
> >> >>> I think it might be clearer to rename it to de0-nano-soc, what do
> >> >>> you think ? What's the difference between de0-nano-soc and atlas
> >> >>> btw ?
> >> >>
> >> >> Unless they are going to make "de0-mega".. I'd say "de0" is clean
> >> >> enough.
> >> >
> >> > They already make de0-cv , which is cycloneV SoC based, so de0 is not
> >> > clear enough, no way. They also make de0-nano , which is cycloneIV
> >> > based (without soc).
> >>
> >> After looking around the site a bit more, I think "de0_nano_sockit" is
> >> more appropriate?
> >
> > It's de0-nano-soc, that's what they call it on that website, right ?
> > SoCkit is a separate board.
>
> Ah yes, it's de0-nano-soc<space>kit. So "de0-nano-soc" ?
Yeah, exactly :)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-09-02 8:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 19:57 [U-Boot] [PATCH] arm: socfpga: Add support for the Terasic DE-0 Atlas board dinguyen at opensource.altera.com
2015-08-31 22:23 ` Marek Vasut
2015-09-01 4:56 ` Chin Liang See
2015-09-01 8:31 ` Marek Vasut
2015-09-01 7:38 ` Pavel Machek
2015-09-01 8:33 ` Marek Vasut
2015-09-01 15:12 ` Dinh Nguyen
2015-09-01 15:36 ` Marek Vasut
2015-09-01 21:37 ` Dinh Nguyen
2015-09-02 8:05 ` Marek Vasut [this message]
2015-09-01 15:09 ` Dinh Nguyen
2015-09-01 15:37 ` Marek Vasut
2015-09-01 4:54 ` Chin Liang See
2015-09-01 8:30 ` Marek Vasut
2015-09-01 8:45 ` Chin Liang See
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=201509021005.21485.marex@denx.de \
--to=marex@denx.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