From: Florian Fainelli <f.fainelli@gmail.com>
To: "Linus Walleij" <linus.walleij@linaro.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: 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 09:32:37 -0800 [thread overview]
Message-ID: <944e92e3-16b2-0c67-02b7-80c7679707de@gmail.com> (raw)
In-Reply-To: <20221107134901.1422710-1-linus.walleij@linaro.org>
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.
--
Florian
_______________________________________________
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 17:33 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 [this message]
2022-11-07 22:25 ` Linus Walleij
2022-11-07 22:38 ` Rafał Miłecki
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=944e92e3-16b2-0c67-02b7-80c7679707de@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=zajec5@gmail.com \
/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