public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "André Przywara" <andre.przywara@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] Pine64: rename defconfig
Date: Wed, 4 May 2016 23:14:39 +0100	[thread overview]
Message-ID: <572A744F.6030501@arm.com> (raw)
In-Reply-To: <CALeDE9MrAvQ1Pmzbyxkkdr9LzFrM_OP0Z9pqxF4-Ccau8-9DWw@mail.gmail.com>

On 04/05/16 22:46, Peter Robinson wrote:
> On Wed, May 4, 2016 at 10:15 PM, Andre Przywara <andre.przywara@arm.com> wrote:
>> Rename the defconfig file for the Pine64 from pine64_plus_defconfig to
>> pine64_defconfig.
>> The differences between the two versions (more RAM and a different
>> Ethernet PHY) don't justify two board versions, so lets stick with the
>> generic name and try to differentiate between the versions at runtime
>> if this is needed later.
>>
>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>> ---
>>  configs/pine64_defconfig      | 20 ++++++++++++++++++++
>>  configs/pine64_plus_defconfig | 20 --------------------
>>  2 files changed, 20 insertions(+), 20 deletions(-)
>>  create mode 100644 configs/pine64_defconfig
>>  delete mode 100644 configs/pine64_plus_defconfig
>>
>> diff --git a/configs/pine64_defconfig b/configs/pine64_defconfig
>> new file mode 100644
>> index 0000000..0977334
>> --- /dev/null
>> +++ b/configs/pine64_defconfig
>> @@ -0,0 +1,20 @@
>> +CONFIG_ARM=y
>> +CONFIG_ARCH_SUNXI=y
>> +CONFIG_MACH_SUN50I=y
>> +CONFIG_DRAM_CLK=672
>> +CONFIG_DRAM_ZQ=3881915
>> +# CONFIG_VIDEO is not set
>> +CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pine64-plus"
> 
> If you're building a single u-boot for all variants of Pine64,

Yes!

> something which I'd prefer, I don't think we can just set a default
> but rather need some logic to specify the DT name based on which board
> is booting. This is done for example in the BeagleBone config to
> detect the various variants of the BeagleBones.

OK, I will look at this.

I wonder if we can just use the plus .dts and then remove the parts that
the non-plus is missing and push that through to the kernel.
U-Boot already takes care of one difference: the DRAM size.
I think we could also detect the different Ethernet PHY (or deduce this
from the DRAM size?) and fix that up.
For the third difference - camera and LCD connectors - U-Boot itself
doesn't even care. But it would be nice if having a 512 MB board would
result in the respective DT nodes to be deleted.
This way we would have _one_ DT source - the U-Boot repository - and
automatically deliver a fixed up version to every OS.

What do you think?

Cheers,
Andre.

>> +# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
>> +CONFIG_HUSH_PARSER=y
>> +# CONFIG_CMD_IMLS is not set
>> +# CONFIG_CMD_FLASH is not set
>> +CONFIG_CMD_MMC=y
>> +# CONFIG_CMD_FPGA is not set
>> +CONFIG_CMD_DHCP=y
>> +CONFIG_CMD_MII=y
>> +CONFIG_CMD_PING=y
>> +CONFIG_CMD_EXT2=y
>> +CONFIG_CMD_EXT4=y
>> +CONFIG_CMD_FAT=y
>> +CONFIG_CMD_FS_GENERIC=y
>> diff --git a/configs/pine64_plus_defconfig b/configs/pine64_plus_defconfig
>> deleted file mode 100644
>> index 0977334..0000000
>> --- a/configs/pine64_plus_defconfig
>> +++ /dev/null
>> @@ -1,20 +0,0 @@
>> -CONFIG_ARM=y
>> -CONFIG_ARCH_SUNXI=y
>> -CONFIG_MACH_SUN50I=y
>> -CONFIG_DRAM_CLK=672
>> -CONFIG_DRAM_ZQ=3881915
>> -# CONFIG_VIDEO is not set
>> -CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pine64-plus"
>> -# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
>> -CONFIG_HUSH_PARSER=y
>> -# CONFIG_CMD_IMLS is not set
>> -# CONFIG_CMD_FLASH is not set
>> -CONFIG_CMD_MMC=y
>> -# CONFIG_CMD_FPGA is not set
>> -CONFIG_CMD_DHCP=y
>> -CONFIG_CMD_MII=y
>> -CONFIG_CMD_PING=y
>> -CONFIG_CMD_EXT2=y
>> -CONFIG_CMD_EXT4=y
>> -CONFIG_CMD_FAT=y
>> -CONFIG_CMD_FS_GENERIC=y
>> --
>> 2.7.3
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
> 

  reply	other threads:[~2016-05-04 22:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 21:15 [U-Boot] [PATCH 0/6] arm64: Pine64 fixes and updates Andre Przywara
2016-05-04 21:15 ` [U-Boot] [PATCH 1/6] arm/arm64: Move barrier instructions into separate header Andre Przywara
2016-05-08  0:36   ` André Przywara
2016-05-04 21:15 ` [U-Boot] [PATCH 2/6] Revert "sunxi: Reserve ATF memory space on A64" Andre Przywara
2016-05-15 10:12   ` [U-Boot] [U-Boot, " Hans de Goede
2016-05-04 21:15 ` [U-Boot] [PATCH 3/6] arm64: sunxi: reserve space for boot0 header Andre Przywara
2016-05-06 21:15   ` Steve Rae
2016-05-06 21:27     ` André Przywara
2016-05-06 21:35       ` Steve Rae
2016-05-15 10:13   ` [U-Boot] [U-Boot, " Hans de Goede
2016-05-04 21:15 ` [U-Boot] [PATCH 4/6] arm64: sunxi: adjust default load addresses Andre Przywara
2016-05-15 10:12   ` [U-Boot] [U-Boot, " Hans de Goede
2016-05-04 21:15 ` [U-Boot] [PATCH 5/6] arm64: Pine64: update FDT files Andre Przywara
2016-05-15 10:13   ` [U-Boot] [U-Boot,5/6] " Hans de Goede
2016-05-15 12:48     ` André Przywara
2016-05-04 21:15 ` [U-Boot] [PATCH 6/6] Pine64: rename defconfig Andre Przywara
2016-05-04 21:46   ` Peter Robinson
2016-05-04 22:14     ` André Przywara [this message]
2016-05-06 15:11       ` Tom Rini
2016-05-06 15:20         ` Andre Przywara
2016-05-06 15:31           ` Tom Rini
2016-05-15 10:30   ` [U-Boot] [U-Boot,6/6] " Hans de Goede
2016-05-15 12:49     ` André Przywara
2016-05-15 13:28       ` Hans de Goede
2016-05-15 20:19       ` Alexander Graf
2016-05-04 21:53 ` [U-Boot] [PATCH 0/6] arm64: Pine64 fixes and updates Peter Robinson
2016-05-04 22:05   ` André Przywara
2016-05-04 22:15     ` Peter Robinson
2016-05-04 22:36       ` André Przywara
2016-05-05  1:03         ` Chen-Yu Tsai
2016-05-06 15:09 ` Tom Rini
2016-05-06 17:03   ` Andre Przywara
2016-05-06 17:22     ` Tom Rini

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=572A744F.6030501@arm.com \
    --to=andre.przywara@arm.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