From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 10/10] ARM: socfpga: arria10: add support for building Arria10
Date: Mon, 23 Nov 2015 08:36:14 -0600 [thread overview]
Message-ID: <5653245E.6010604@opensource.altera.com> (raw)
In-Reply-To: <201511201349.52169.marex@denx.de>
On 11/20/2015 06:49 AM, Marek Vasut wrote:
> On Friday, November 20, 2015 at 12:28:47 AM, Dinh Nguyen wrote:
>> On 11/19/2015 04:45 PM, Marek Vasut wrote:
>>> On Thursday, November 19, 2015 at 10:35:47 PM,
>>> dinguyen at opensource.altera.com
>>>
>>> wrote:
>>>> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>>>>
>>>> Update Makefile to build Arria 10.
>>>>
>>>> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
>>>> ---
>>>>
>>>> arch/arm/mach-socfpga/Makefile | 7 +++++--
>>>> arch/arm/mach-socfpga/arria10/Makefile | 7 +++++++
>>>> 2 files changed, 12 insertions(+), 2 deletions(-)
>>>> create mode 100644 arch/arm/mach-socfpga/arria10/Makefile
>>>>
>>>> diff --git a/arch/arm/mach-socfpga/Makefile
>>>> b/arch/arm/mach-socfpga/Makefile index 316b326..0dbe9bb 100644
>>>> --- a/arch/arm/mach-socfpga/Makefile
>>>> +++ b/arch/arm/mach-socfpga/Makefile
>>>> @@ -6,15 +6,18 @@
>>>>
>>>> #
>>>> # SPDX-License-Identifier: GPL-2.0+
>>>> #
>>>>
>>>> -
>>>> +ifneq ($(CONFIG_TARGET_SOCFPGA_ARRIA10),y)
>>>>
>>>> obj-y += misc.o timer.o reset_manager.o system_manager.o
>>>
>>> clock_manager.o \
>>>
>>>> fpga_manager.o scan_manager.o
>>>>
>>>> obj-$(CONFIG_SPL_BUILD) += spl.o freeze_controller.o
>>>>
>>>> -
>>>>
>>>> # QTS-generated config file wrappers
>>>> obj-y += wrap_pll_config.o
>>>> obj-$(CONFIG_SPL_BUILD) += wrap_iocsr_config.o wrap_pinmux_config.o \
>>>>
>>>> wrap_sdram_config.o
>>>>
>>>> +else
>>>> +obj-y += arria10/
>>>
>>> So why exactly does A10 have it's own dedicated dir if most of the code
>>> is probably shared between A10 and AV/CV ?
>>
>> Yes, there are some sharing. But I think that there will be enough
>> differences that will ultimately warrant it's own directory. I think
>> with it's own directory, the Makefile changes stay a bit cleaner. I
>
> Linux doesn't seem to require a separate directory though, does it ?
> I'm not convinced we need one either.
>
>> One of the biggest differences is that the A10's SDRAM support is going
>> to be a bit ugly.
>
> The SDRAM code goes into drivers/ddr/ , no problem.
>
>> The main point is that we need to program the FPGA
>> during U-Boot booting up with a ~>10 MB rbf file while being limited to
>> the OCRAM's size. I would like to contain this ugliness in it's own
>> directory.
>
> What's the problem with this ? We already support loading files from storage
> in SPL, so just compile the FPGA manager into SPL as well and use it.
>
Ok, let me re-work it all under the c5/a5 directory. Thanks for reviewing.
Dinh
next prev parent reply other threads:[~2015-11-23 14:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 21:35 [U-Boot] [PATCH 00/10] ARM: socfpga: Add minimal support for Arria10 dinguyen at opensource.altera.com
2015-11-19 21:35 ` [U-Boot] [PATCH 01/10] ARM: socfpga: arria10: add base address map " dinguyen at opensource.altera.com
2015-11-19 22:26 ` Marek Vasut
2015-11-23 23:16 ` Dinh Nguyen
2015-11-19 21:35 ` [U-Boot] [PATCH 02/10] ARM: socfpga: arria10: add system manager defines dinguyen at opensource.altera.com
2015-11-19 22:27 ` Marek Vasut
2015-11-19 21:35 ` [U-Boot] [PATCH 03/10] ARM: socfpga: arria10: add reset manager for Arria10 dinguyen at opensource.altera.com
2015-11-19 22:35 ` Marek Vasut
2015-11-19 21:35 ` [U-Boot] [PATCH 04/10] ARM: socfpga: arria10: add stub sdram init " dinguyen at opensource.altera.com
2015-11-23 12:25 ` Pavel Machek
2015-11-23 12:57 ` Marek Vasut
2015-11-19 21:35 ` [U-Boot] [PATCH 05/10] ARM: socfpga: arria10: add misc functions " dinguyen at opensource.altera.com
2015-11-19 22:37 ` Marek Vasut
2015-11-19 21:35 ` [U-Boot] [PATCH 06/10] ARM: socfpga: arria10: add socfpga_arria10_socdk config dinguyen at opensource.altera.com
2015-11-19 22:43 ` Marek Vasut
2015-11-19 21:35 ` [U-Boot] [PATCH 07/10] ARM: socfpga: arria10: add board files for the Arria10 SoCDK dinguyen at opensource.altera.com
2015-11-23 12:43 ` Pavel Machek
2015-11-19 21:35 ` [U-Boot] [PATCH 08/10] ARM: socfpga: arria10: add socfpga_arria10_defconfig dinguyen at opensource.altera.com
2015-11-19 21:35 ` [U-Boot] [PATCH 09/10] ARM: socfpga: arria10: add config option build for arria10 dinguyen at opensource.altera.com
2015-11-19 21:35 ` [U-Boot] [PATCH 10/10] ARM: socfpga: arria10: add support for building Arria10 dinguyen at opensource.altera.com
2015-11-19 22:45 ` Marek Vasut
2015-11-19 23:28 ` Dinh Nguyen
2015-11-20 12:49 ` Marek Vasut
2015-11-23 14:36 ` Dinh Nguyen [this message]
2015-11-23 15:38 ` Marek Vasut
2015-11-23 22:32 ` Dinh Nguyen
2015-11-23 22:46 ` Marek Vasut
2015-11-23 22:50 ` Dinh Nguyen
2015-11-23 23:03 ` Marek Vasut
2015-11-23 23:04 ` Dinh Nguyen
2015-11-23 23:20 ` Marek Vasut
2015-11-23 23:25 ` Dinh Nguyen
2015-11-24 3:17 ` Chin Liang See
2015-11-24 9:31 ` Marek Vasut
2015-11-24 12:29 ` Heiko Schocher
2015-11-24 9:33 ` Chin Liang See
2015-11-24 13:22 ` Chin Liang See
2015-11-24 13:31 ` Pavel Machek
2015-11-24 13:36 ` Chin Liang See
2015-11-24 13:52 ` Marek Vasut
2015-11-24 14:01 ` Pavel Machek
2015-11-24 15:09 ` Marek Vasut
2015-11-24 13:34 ` Chin Liang See
2015-11-24 13:53 ` Marek Vasut
2015-11-23 12:51 ` Pavel Machek
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=5653245E.6010604@opensource.altera.com \
--to=dinguyen@opensource.altera.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