From: Marek Szyprowski <m.szyprowski@samsung.com> To: Stefan Wahren <stefan.wahren@i2se.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: Fri, 14 Feb 2020 13:25:59 +0100 [thread overview] Message-ID: <8bd7a25a-359d-5b30-4c95-004032d78cb6@samsung.com> (raw) In-Reply-To: <916c0113-9910-26cd-3720-15399fde507b@i2se.com> Hi Stefan, On 13.02.2020 10:59, Stefan Wahren wrote: > On 13.02.20 08:35, Marek Szyprowski wrote: >> On 12.02.2020 19:31, Nicolas Saenz Julienne wrote: >>> 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. Okay, I will add thermal in v2. HWRNG is already selected as module. Enabling PCI without LPAE makes no sense as the driver won't be able to initialize properly. > SMP, HIGHMEM, LPAE are different and shouldn't be enabled in > bcm2835_defconfig from my PoV. Maybe it would make sense to also add bcm2711_defconfig or bcm2835_lpae_defconfig? Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com> To: Stefan Wahren <stefan.wahren@i2se.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: Fri, 14 Feb 2020 13:25:59 +0100 [thread overview] Message-ID: <8bd7a25a-359d-5b30-4c95-004032d78cb6@samsung.com> (raw) In-Reply-To: <916c0113-9910-26cd-3720-15399fde507b@i2se.com> Hi Stefan, On 13.02.2020 10:59, Stefan Wahren wrote: > On 13.02.20 08:35, Marek Szyprowski wrote: >> On 12.02.2020 19:31, Nicolas Saenz Julienne wrote: >>> 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. Okay, I will add thermal in v2. HWRNG is already selected as module. Enabling PCI without LPAE makes no sense as the driver won't be able to initialize properly. > SMP, HIGHMEM, LPAE are different and shouldn't be enabled in > bcm2835_defconfig from my PoV. Maybe it would make sense to also add bcm2711_defconfig or bcm2835_lpae_defconfig? Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland _______________________________________________ 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-02-14 12:26 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20200212102022eucas1p1c49daf15d3e63eda9a56124bc4eafb57@eucas1p1.samsung.com> 2020-02-12 10:20 ` [PATCH] ARM: bcm2835_defconfig: add minimal support for Raspberry Pi4 Marek Szyprowski 2020-02-12 10:20 ` Marek Szyprowski 2020-02-12 18:31 ` Nicolas Saenz Julienne 2020-02-12 18:31 ` Nicolas Saenz Julienne 2020-02-13 7:35 ` Marek Szyprowski 2020-02-13 7:35 ` Marek Szyprowski 2020-02-13 9:59 ` Stefan Wahren 2020-02-13 9:59 ` Stefan Wahren 2020-02-14 12:25 ` Marek Szyprowski [this message] 2020-02-14 12:25 ` Marek Szyprowski 2020-02-14 15:14 ` Nicolas Saenz Julienne 2020-02-14 15:14 ` Nicolas Saenz Julienne 2020-02-17 12:22 ` Marek Szyprowski 2020-02-17 12:22 ` Marek Szyprowski 2020-02-17 20:18 ` Nicolas Saenz Julienne 2020-02-17 20:18 ` Nicolas Saenz Julienne 2020-02-17 21:44 ` Florian Fainelli 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=8bd7a25a-359d-5b30-4c95-004032d78cb6@samsung.com \ --to=m.szyprowski@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=nsaenzjulienne@suse.de \ --cc=stefan.wahren@i2se.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.