From: Stefan Bosch <stefan_b@posteo.net>
To: u-boot@lists.denx.de
Subject: [PATCH v1 0/1] arm: Add support for SoC S5P4418
Date: Tue, 07 Jan 2020 22:43:41 +0100 [thread overview]
Message-ID: <80a2d0977057b86e5ea1020d2e804258@posteo.de> (raw)
In-Reply-To: <20200106210720.GM4866@bill-the-cat>
Hi Tom,
thanks a lot for your quick reply.
On 06.01.2020 22:07, Tom Rini wrote:
> On Mon, Jan 06, 2020 at 09:58:47PM +0100, Stefan Bosch wrote:
>> This patch adds support for SAMSUNG's ARM Cortex-A9 based S5P4418 SoC,
>> especially FriendlyARM's NanoPi2 and NanoPC-T2 boards. It is based on
>> https://github.com/friendlyarm/u-boot/tree/nanopi2-v2016.01. For
>> v2016.01 I
>> have also made a working SPL (FriendlyARM U-Boot is using a closed
>> source
>> 2nd-bootloader). My plan is to migrate this also to the current
>> U-Boot.
>>
>> Issues:
>> Please send me a value for "#define MACH_TYPE_S5P4418" for
>> arch/arm/include/asm/mach-types.h.
>
> Do you really need to support non-DT kernels?
>
I have adopted this from the original Code. What is the alternative?
Could you please give me more details (e.g. an example-board).
>> The size of the patch is over 700kB, so I will upload it on
>> http://www.denx.de/wiki/attach/U-Boot/TooBigPatches if not otherwise
>> instructed.
>
> Ah, I would suggest splitting things up into smaller logical chunks (a
> patch per driver, separate SoC from board, etc) so they're all able to
> make it to patchwork, thanks!
Ok, I will try to split the patch into chunks <= 100kB without loosing
the logic ;-)
Regards,
Stefan
next prev parent reply other threads:[~2020-01-07 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 20:58 [PATCH v1 0/1] arm: Add support for SoC S5P4418 Stefan Bosch
2020-01-06 21:07 ` Tom Rini
2020-01-07 21:43 ` Stefan Bosch [this message]
2020-01-07 10:57 ` Lukasz Majewski
2020-01-07 21:46 ` Stefan Bosch
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=80a2d0977057b86e5ea1020d2e804258@posteo.de \
--to=stefan_b@posteo.net \
--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