From: Florian Fainelli <f.fainelli@gmail.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Stefan Wahren <wahrenst@gmx.net>,
f.fainelli@gmail.com
Cc: mbrugger@suse.com, Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org, hch@lst.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] ARM: add bcm2711_defconfig
Date: Tue, 7 Jan 2020 10:28:01 -0800 [thread overview]
Message-ID: <5db5ed47-adab-8d31-c3f7-4d7f63258e22@gmail.com> (raw)
In-Reply-To: <65e976494676a7081b154961ba51048892c2a779.camel@suse.de>
On 1/7/20 10:11 AM, Nicolas Saenz Julienne wrote:
> On Tue, 2020-01-07 at 19:06 +0100, Stefan Wahren wrote:
>> Hi Nicolas,
>>
>> Am 07.01.20 um 18:24 schrieb Nicolas Saenz Julienne:
>>> The Raspberry Pi 4 depends on LPAE in order to use its PCIe port, which
>>> is essential, as it ultimately provides USB2/3 connectivity. As this
>>> setup doesn't fit any generic purpose configuration this adds
>>> bcm2711_defconfig which is based on the current Raspberry Pi foundation
>>> config file[1] with as little changes as possible
>>
>> i really dislike the Foundation config file, because it contains so many
>> unnecessary features. Bisecting with such a kernel config is horrible.
>>
>> How about finding a compromise between bcm2835_defconfig and
>> multi_v7_defconfig + LPAE?
>
> If there is a consensus this is the right approach (creating a new config
> file), I'll be happy to try that out.
>
> Now that I think of it, maybe we shouldn't add bcm2711_thermal into
> multi_v7_defconfig.
It there a mechanism that can be used such that bcm2711_defconfig would
be simply a fragment that enables CONFIG_ARM_LPAE=y (and other relevant
2711 only options) and that you could easily run/test with, something like:
ARCH=arm make bcm2835_defconfig+bcm2711_defconfig
or something along those lines?
--
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:[~2020-01-07 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:24 [RFC] ARM: add bcm2711_defconfig Nicolas Saenz Julienne
2020-01-07 18:06 ` Stefan Wahren
2020-01-07 18:11 ` Nicolas Saenz Julienne
2020-01-07 18:28 ` Florian Fainelli [this message]
2020-01-08 13:53 ` Nicolas Saenz Julienne
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=5db5ed47-adab-8d31-c3f7-4d7f63258e22@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mbrugger@suse.com \
--cc=nsaenzjulienne@suse.de \
--cc=wahrenst@gmx.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