From: Stefan Wahren <stefan.wahren@i2se.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: bcm2835_defconfig: add minimal support for Raspberry Pi4
Date: Thu, 13 Feb 2020 10:59:46 +0100 [thread overview]
Message-ID: <916c0113-9910-26cd-3720-15399fde507b@i2se.com> (raw)
In-Reply-To: <5adcb2de-3570-9c4d-5e5b-726b94fb2029@samsung.com>
Hi Marek,
On 13.02.20 08:35, Marek Szyprowski wrote:
> Hi Nicolas
>
> On 12.02.2020 19:31, Nicolas Saenz Julienne wrote:
>> Hi Marek,
>> On Wed, 2020-02-12 at 11:20 +0100, Marek Szyprowski wrote:
>>> Add drivers for the minimal set of devices needed to boot Raspberry Pi4
>>> board.
>>>
>>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> Just so you know, the amount of support on the RPi4 you might be able to get
>> updating bcm2835_defconfig's config is very limited. Only 1GB of ram and no
>> PCIe (so no USBs).
> Yes, I know. A lots of core features is missing: SMP, HIGHMEM, LPAE, PCI
> and so on, but having a possibility to boot RPi4 with this defconfig
> increases the test coverage.
in case you want to increase test coverage, we better enable all
Raspberry Pi 4 relevant hardware parts (hwrng, thermal, PCI ...). This
is what we did for older Pi boards.
SMP, HIGHMEM, LPAE are different and shouldn't be enabled in
bcm2835_defconfig from my PoV.
Best regards
Stefan
next prev parent reply other threads:[~2020-02-13 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200212102022eucas1p1c49daf15d3e63eda9a56124bc4eafb57@eucas1p1.samsung.com>
2020-02-12 10:20 ` Marek Szyprowski
2020-02-12 18:31 ` Nicolas Saenz Julienne
2020-02-13 7:35 ` Marek Szyprowski
2020-02-13 9:59 ` Stefan Wahren [this message]
2020-02-14 12:25 ` Marek Szyprowski
2020-02-14 15:14 ` Nicolas Saenz Julienne
2020-02-17 12:22 ` Marek Szyprowski
2020-02-17 20:18 ` Nicolas Saenz Julienne
2020-02-17 21:44 ` Florian Fainelli
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=916c0113-9910-26cd-3720-15399fde507b@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.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
all inboxes | Powered by JetHome®