[BUG] nvme: multiple name spaces not correctly handled

[Heinrich Schuchardt]

On 9/3/22 11:22, Heinrich Schuchardt wrote:
> Hello Bin,
>
> with QEMU 7.0:
>
> -rw-rw-r-- 1 user user   33554432 Oct 23  2021 arm64.img
> -rw-rw-r-- 1 user user 3758096384 Mar 23 23:42 riscv64.img
>
> qemu-system-aarch64 -machine virt -cpu cortex-a72 -nographic \
> -bios denx/u-boot.bin \
> -device nvme,id=nvme1,serial=9ff81223 \
> -device nvme-ns,bus=nvme1,drive=nvme1n0,eui64=0x123456789ABCDEF0 \
> -drive file=arm64.img,if=none,format=raw,id=nvme1n0

My fault. Missing \

Sorry for the noise.

Best regards

Heinrich

> -device nvme-ns,bus=nvme1,drive=nvme1n1,eui64=0x0102030405060708 \
> -drive file=riscv64.img,if=none,format=raw,id=nvme1n1
>
> We should now see two block devices in U-Boot.
>
> => nvme scan
> => nvme info
> Device 0: Vendor: 0x1b36 Rev: 1.0      Prod: 9ff81223
>              Type: Hard Disk
>              Capacity: 32.0 MB = 0.0 GB (65536 x 512)
> => dm tree
> nvme      0  [ + ]   nvme          | `-- nvme#0
> blk       0  [ + ]   nvme-blk      |     `-- nvme#0.blk#1
> partition 0  [ + ]   blk_partition |         `-- nvme#0.blk#1:1
>
> => efidebug devices
>
> Device           Device Path
> ================ ====================
> 0000000046ef4a10
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/NVMe(0x1,f0-de-bc-9a-78-56-34-12)
>
> Where is the device for file riscv64.img?
>
> Best regards
>
> Heinrich