From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH] ARM: bcm2835_defconfig: add minimal support for Raspberry Pi4
Date: Wed, 12 Feb 2020 19:31:47 +0100 [thread overview]
Message-ID: <a1d66025baa13b2276b12405544fc7107aac8d6c.camel@suse.de> (raw)
In-Reply-To: <20200212102009.17428-1-m.szyprowski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
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).
FYI I've been working on getting a workable configuration for arm32, short of
creating a new config altogether:
https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg163770.html
That said, if you insist on booting with bcm2835_defconfig, I have no problem
with the patch.
Regards,
Nicolas
> arch/arm/configs/bcm2835_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm/configs/bcm2835_defconfig
> b/arch/arm/configs/bcm2835_defconfig
> index 519ff58e67b3..b5e7c1bd95f2 100644
> --- a/arch/arm/configs/bcm2835_defconfig
> +++ b/arch/arm/configs/bcm2835_defconfig
> @@ -72,6 +72,7 @@ CONFIG_BLK_DEV_SD=y
> CONFIG_SCSI_CONSTANTS=y
> CONFIG_SCSI_SCAN_ASYNC=y
> CONFIG_NETDEVICES=y
> +CONFIG_BCMGENET=y
> CONFIG_USB_LAN78XX=y
> CONFIG_USB_USBNET=y
> CONFIG_USB_NET_SMSC95XX=y
> @@ -99,6 +100,8 @@ CONFIG_THERMAL=y
> CONFIG_BCM2835_THERMAL=y
> CONFIG_WATCHDOG=y
> CONFIG_BCM2835_WDT=y
> +CONFIG_REGULATOR=y
> +CONFIG_REGULATOR_GPIO=y
> CONFIG_MEDIA_SUPPORT=y
> CONFIG_MEDIA_CAMERA_SUPPORT=y
> CONFIG_DRM=y
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-12 18:31 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 [this message]
2020-02-13 7:35 ` Marek Szyprowski
2020-02-13 9:59 ` Stefan Wahren
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=a1d66025baa13b2276b12405544fc7107aac8d6c.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--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=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: 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®