All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torsten Duwe <duwe@lst.de>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Pedro Falcato <pfalcato@suse.de>, Bin Meng <bmeng.cn@gmail.com>,
	Andrew Goodbody <andrew.goodbody@linaro.org>,
	Matthias Brugger <mbrugger@suse.com>,
	Andrea della Porta <andrea.porta@suse.com>,
	Tom Rini <trini@konsulko.com>,
	u-boot@lists.denx.de
Subject: Re: [hack] help U-Boot find the correct PCIe inbound offset for NVMe on Raspberry Pi 5
Date: Wed, 4 Mar 2026 23:25:48 +0100	[thread overview]
Message-ID: <20260304232548.630b15e3@rocky.lan> (raw)
In-Reply-To: <CALeDE9NK_KvEitadfcYJQXe7bjoM7JRH3gAh0UzrjtLyUjJjpQ@mail.gmail.com>

On Wed, 4 Mar 2026 20:24:35 +0000
Peter Robinson <pbrobinson@gmail.com> wrote:

> On Wed, 4 Mar 2026 at 19:43, Pedro Falcato <pfalcato@suse.de> wrote:
> >
> > Hi Torsten,
> >
> > On Mon, Mar 02, 2026 at 04:42:56PM +0100, Torsten Duwe wrote:
> > > On Mon, 2 Mar 2026 13:59:40 +0100
> > > Torsten Duwe <duwe@lst.de> wrote:
> > >
> > > > This proposed patch uses the already existent dev_phys_to_bus(),
> > > > which can dig up the correct offset from associated DT nodes and
> > > > subtract it.
> > >
> > > Just to make it clear, that patch is a necessary but not a sufficient
> > > condition to boot the RPi5 from NVMe. The PCIe bus node above
> > > the NVMe is generated dynamically has no DT node with dma-ranges and so
> > > dev_phys_to_bus() still returns zero. In order to test NVMe on the
> > > RPi5 you can either:
> > >
> >
> > Say I wanted to test NVMe booting on the pi5 (which I actually do).
> > I would need:
> > 1) this patch
> > 2) one of the two BUS_ADDR() related diffs
> > 3) the fixes posted in https://lore.kernel.org/u-boot/20251105163553.15F2A227AAC@verein.lst.de/
> 
> I believe that series has been replaced with:
> https://lore.kernel.org/u-boot/20260227152046.42DE068B05@verein.lst.de/T/#t

Yes. Or on patchwork: https://patchwork.ozlabs.org/project/uboot/list/?series=493779

> > 4) anything else?
> 
> Enable NVME support in the defconfig

NVME commands and NVME_PCI. CONFIG_NVME_PCI requires CONFIG_NVME.

	Torsten


  reply	other threads:[~2026-03-04 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 12:59 [PATCH v0] Fix NVMe for non-zero bus offsets Torsten Duwe
2026-03-02 15:42 ` [hack] help U-Boot find the correct PCIe inbound offset for NVMe on Raspberry Pi 5 Torsten Duwe
2026-03-04 19:43   ` Pedro Falcato
2026-03-04 20:24     ` Peter Robinson
2026-03-04 22:25       ` Torsten Duwe [this message]
2026-03-05  9:01     ` Matthias Brugger

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=20260304232548.630b15e3@rocky.lan \
    --to=duwe@lst.de \
    --cc=andrea.porta@suse.com \
    --cc=andrew.goodbody@linaro.org \
    --cc=bmeng.cn@gmail.com \
    --cc=mbrugger@suse.com \
    --cc=pbrobinson@gmail.com \
    --cc=pfalcato@suse.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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 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.