From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: Add icnova-a20-swac defconfig and dts file
Date: Mon, 19 Oct 2015 13:42:57 +0200 [thread overview]
Message-ID: <5624D741.1060509@redhat.com> (raw)
In-Reply-To: <5624C82F.7030704@denx.de>
Hi,
On 19-10-15 12:38, Stefan Roese wrote:
> Hi Hans,
>
> On 17.10.2015 15:47, Hans de Goede wrote:
>> On 01-10-15 11:41, Stefan Roese wrote:
>>> The ICnova-A20-SWAC is a baseboard, equipped with the ICnova-A20 SoM from
>>> In-Circuit:
>>>
>>> http://wiki.in-circuit.de/index.php5?title=ICnova_A20_SODIMM
>>> http://linux-sunxi.org/In-Circuit_ICnova_A20
>>>
>>> This patch adds support for this board, including ethernet, LCD and USB
>>> support.
>>
>> Thanks, I've merged this and it will show up in u-boot-sunxi/next soon.
>
> Thanks.
>
>> I've made 2 small changes, see comments inline.
>
> <snip>
>
>>> diff --git a/configs/icnova-a20-swac_defconfig
>>> b/configs/icnova-a20-swac_defconfig
>>> new file mode 100644
>>> index 0000000..bd6e0c5
>>> --- /dev/null
>>> +++ b/configs/icnova-a20-swac_defconfig
>>> @@ -0,0 +1,21 @@
>>> +CONFIG_ARM=y
>>> +CONFIG_ARCH_SUNXI=y
>>> +CONFIG_MACH_SUN7I=y
>>> +CONFIG_DRAM_CLK=384
>>> +CONFIG_OLD_SUNXI_KERNEL_COMPAT=y
>>
>> I've dropped this, I understand that you need it, but I do not believe that
>> ANY defconfig's as shipped upstream should set this.
>
> Hmmm. I would prefer to have this added to the defconfig as well.
> As it very likely leads to confusion when updating to a newer
> U-Boot version which will not support the old kernel. Why not give
> the users / maintainers the freedom to choose this for themselves?
Users are free to choose this, they can always enable this themselves
after running make foo_defconfig.
As for why not give the MAINTAINERS a choice on this, as said
I believe that we should not shipp defconfigs with this set by default
as part of mainline u-boot. The reasons for this are:
1) It is inconsistent with what we are doing for all other sunxi boards
where we are primarily targetting mainline
2) It communicates that CONFIG_OLD_SUNXI_KERNEL_COMPAT is an officially
supported end-user feature, where as in reality it is targeted at developers
who need to run an old sunxi kernel every now and then to see how that
kernel exactly programs certain registers, etc.
3) It means we ship with a severely crippled defconfig for mainline kernel
users, mainline users will loose both smp and hyp mode support on the A20
when this option is set.
I'm sorry but I'm not going to budge on this one, having
CONFIG_OLD_SUNXI_KERNEL_COMPAT=y in a defconfig is simply not acceptable
IMHO. It is not a board specific thing, and there are very good reasons
why it defaults to n in board/sunxi/Kconfig
>>> +CONFIG_MMC0_CD_PIN="PI5"
>>> +CONFIG_USB0_VBUS_PIN="PG11"
>>> +CONFIG_USB0_VBUS_DET="PH7"
>>> +CONFIG_USB1_VBUS_PIN="PG10"
>>> +CONFIG_VIDEO_LCD_MODE="x:800,y:480,depth:24,pclk_khz:33000,le:45,ri:209,up:22,lo:22,hs:1,vs:1,sync:3,vmode:0"
>>>
>>> +CONFIG_VIDEO_LCD_POWER="PH22"
>>> +CONFIG_VIDEO_LCD_PANEL_LVDS=y
>>> +CONFIG_DEFAULT_DEVICE_TREE="sun7i-a20-icnova-a20-swac"
>>> +# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
>>> +CONFIG_SPL=y
>>> +CONFIG_SYS_EXTRA_OPTIONS="AXP209_POWER,SUNXI_GMAC,CMD_BMP,CMD_UNZIP"
>>
>> I've dropped AXP209_POWER from these, in u-boot-sunxi/next this has been
>> turned into a Kconfig bool which is enabled by default on sun7i.
>
> Understood.
>
> Thanks,
> Stefan
Regards,
Hans
next prev parent reply other threads:[~2015-10-19 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 9:41 [U-Boot] [PATCH] arm: sunxi: Add icnova-a20-swac defconfig and dts file Stefan Roese
2015-10-17 13:47 ` Hans de Goede
2015-10-18 9:34 ` Maxime Ripard
2015-10-19 10:48 ` Stefan Roese
2015-10-19 11:44 ` Hans de Goede
2015-10-19 11:53 ` Stefan Roese
2015-10-20 8:06 ` Ian Campbell
2015-10-21 14:31 ` Maxime Ripard
2015-10-21 14:44 ` Stefan Roese
2015-10-22 7:57 ` Maxime Ripard
2015-10-19 10:38 ` Stefan Roese
2015-10-19 11:42 ` Hans de Goede [this message]
2015-10-20 8:05 ` Ian Campbell
2015-10-19 10:38 ` Stefan Roese
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=5624D741.1060509@redhat.com \
--to=hdegoede@redhat.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