From: "Rafał Miłecki" <zajec5@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: config: Add BCM53xx defconfig
Date: Mon, 7 Nov 2022 23:38:01 +0100 [thread overview]
Message-ID: <d3c20f99-6bc5-235c-781e-a1839a5df8d7@gmail.com> (raw)
In-Reply-To: <CACRpkdZp+qvcJQJ_rBLR=aFR-TLEUxeLbytHYXij-=etEvS3gg@mail.gmail.com>
On 7.11.2022 23:25, Linus Walleij wrote:
> On Mon, Nov 7, 2022 at 6:32 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 11/7/22 05:49, Linus Walleij wrote:
>>> This adds a BCM530x ARM-based Broadcom default config, typically
>>> for use with NorthStar systems. This is needed because it took
>>> me quite a lot of time to figure out all the different drivers and
>>> intricacies that needed to be enabled to bring a typical specimen
>>> from these systems up.
>>>
>>> By simply using this it is easy to configure and boot a mainline
>>> Linux kernel on these systems.
>>>
>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>>> ---
>>> I suppose Florian can merge this, I can also send it directly to
>>> the SOC tree if preferred.
>>
>> ARM SoC maintainers would not let us have a cygnus_defconfig many years
>> ago, so I doubt they would accept this one. defconfigs are easy to
>> maintain out of tree, for better or for worse.
>
> Why not, I had to spend hours to come up with this one, it has
> general use and is good for my compile tests. Also policies
> change, consistency isn't our best game.
>
> Arnd, Olof: can I have this defconfig?
>
> Itr's not like I can't deal with rejection but I want some rationale.
>
> I can send it directly to SoC so you don't need to deal
> with it as long as you approve of the usefulness.
I'd find it quite useful to have more defconfigs mainline. I didn't
submit one after finding some old discussions we don't have more
defconfigs in kernel.
I'd really appreciate some official policy and explanation on this.
On this particular patch: there are few symbols we should discuss. I
don't see why there is CONFIG_EXT4_FS=y and some others too. Let's get
this policy cleared first though.
Linus: you could also ask me before spending so many hours on this. I'd
recommend looking at
https://git.busybox.net/buildroot/tree/board/broadcom/northstar/linux.config
https://git.busybox.net/buildroot/commit/?id=1500b7d5c818fb021eaa8741eec8130cbbf3477e
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-07 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:49 [PATCH] ARM: config: Add BCM53xx defconfig Linus Walleij
2022-11-07 17:32 ` Florian Fainelli
2022-11-07 22:25 ` Linus Walleij
2022-11-07 22:38 ` Rafał Miłecki [this message]
2022-11-08 14:55 ` Linus Walleij
2022-11-07 22:48 ` Florian Fainelli
2022-11-08 14:59 ` Linus Walleij
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=d3c20f99-6bc5-235c-781e-a1839a5df8d7@gmail.com \
--to=zajec5@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
/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