From: Stefan Wahren <wahrenst@gmx.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>, 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 19:06:00 +0100 [thread overview]
Message-ID: <3688a55b-e929-6cef-66c6-affed97d938b@gmx.net> (raw)
In-Reply-To: <20200107172459.28444-1-nsaenzjulienne@suse.de>
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?
_______________________________________________
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:06 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 [this message]
2020-01-07 18:11 ` Nicolas Saenz Julienne
2020-01-07 18:28 ` Florian Fainelli
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=3688a55b-e929-6cef-66c6-affed97d938b@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.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 \
/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;
as well as URLs for NNTP newsgroup(s).