Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Andrea della Porta <andrea.porta@suse.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kamal Dasu <kamal.dasu@broadcom.com>,
	Al Cooper <alcooperx@gmail.com>,
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH v5 0/4] Add minimal boot support for Raspberry Pi 5
Date: Fri, 31 May 2024 12:00:07 +0200	[thread overview]
Message-ID: <36642bd8-c981-4190-9f44-072ac3c97c6b@gmx.net> (raw)
In-Reply-To: <cover.1717061147.git.andrea.porta@suse.com>

Hi Andrea,

Am 30.05.24 um 12:11 schrieb Andrea della Porta:
> Hi,
>
> This patchset adds minimal support for the Broadcom BCM2712 SoC and for
> the on-board SDHCI controller on Broadcom BCM2712 in order to make it
> possible to boot (particularly) a Raspberry Pi 5 from SD card and get a
> console through uart.
> Changes to arm64/defconfig are not needed since the actual options work
> as they are.
> This work is heavily based on downstream contributions.
>
> Tested on Tumbleweed substituting the stock kernel with upstream one,
> either chainloading uboot+grub+kernel or directly booting the kernel
> from 1st stage bootloader. Steps to reproduce:
> - prepare an SD card from a Raspberry enabled raw image, mount the first
>    FAT partition.
> - make sure the FAT partition is big enough to contain the kernel,
>    anything bigger than 64Mb is usually enough, depending on your kernel
>    config options.
> - build the kernel and dtbs making sure that the support for your root
>    fs type is compiled as builtin.
> - copy the kernel image in your FAT partition overwriting the older one
>    (e.g. kernel*.img for Raspberry Pi OS or u-boot.bin for Tumbleweed).
> - copy arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb on FAT partition.
> - make sure you have a cmdline.txt file in FAT partition with the
>    following content:
>    # cat /boot/efi/cmdline.txt
>    root=/dev/mmcblk0p3 rootwait rw console=tty ignore_loglevel earlycon
>    console=ttyAMA10,115200
> - if you experience random SD issues during boot, try to set
>    initial_turbo=0 in config.txt.
was this an issue since the beginning of this series?

What kind of SD issues?

Is there a downstream reference?

  parent reply	other threads:[~2024-05-31 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 10:11 [PATCH v5 0/4] Add minimal boot support for Raspberry Pi 5 Andrea della Porta
2024-05-30 10:11 ` [PATCH v5 1/4] dt-bindings: arm: bcm: Add BCM2712 SoC support Andrea della Porta
2024-05-30 10:11 ` [PATCH v5 2/4] dt-bindings: mmc: Add support for BCM2712 SD host controller Andrea della Porta
2024-05-30 10:12 ` [PATCH v5 3/4] mmc: sdhci-brcmstb: Add BCM2712 support Andrea della Porta
2024-05-30 10:12 ` [PATCH v5 4/4] arm64: dts: broadcom: Add minimal support for Raspberry Pi 5 Andrea della Porta
2024-06-01  8:27   ` Stefan Wahren
2024-06-05 12:07   ` Florian Fainelli
2024-05-30 12:45 ` [PATCH v5 0/4] Add minimal boot " Rob Herring (Arm)
2024-05-31 10:00 ` Stefan Wahren [this message]
2024-05-31 12:59   ` Andrea della Porta
2024-06-01  8:17     ` Stefan Wahren
2024-06-04 11:13 ` Ulf Hansson

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=36642bd8-c981-4190-9f44-072ac3c97c6b@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=adrian.hunter@intel.com \
    --cc=alcooperx@gmail.com \
    --cc=andrea.porta@suse.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=kamal.dasu@broadcom.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=rjui@broadcom.com \
    --cc=robh@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=ulf.hansson@linaro.org \
    /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