Re: Bug: qemu_arm64: Cannot access the second flash bank

2021-09-13 Thread Peter Maydell
On Mon, 13 Sept 2021 at 10:31, Matthias Brugger wrote: > > Hi Robin, > > It's a long long time that you reported this issue. > > I prepared a fix in qemu for it. Would you mind to try it out? You can find a > branch with the fix on top here: > https://github.com/mbgg/qemu/tree/vrit-flash-dtb-bug

Re: Bug: qemu_arm64: Cannot access the second flash bank

2021-09-13 Thread Matthias Brugger
On 13/09/2021 11:40, Peter Maydell wrote: On Mon, 13 Sept 2021 at 10:31, Matthias Brugger wrote: Hi Robin, It's a long long time that you reported this issue. I prepared a fix in qemu for it. Would you mind to try it out? You can find a branch with the fix on top here:

Re: Bug: qemu_arm64: Cannot access the second flash bank

2021-09-13 Thread Matthias Brugger
Hi Robin, It's a long long time that you reported this issue. I prepared a fix in qemu for it. Would you mind to try it out? You can find a branch with the fix on top here: https://github.com/mbgg/qemu/tree/vrit-flash-dtb-bug Basically I fix the reg property to reflect the fact that the

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-04-08 Thread Matthias Brugger
Hi Robin, On 09/01/2020 16:21, Robin Randhawa wrote: > On Thu, 2020-01-09 at 15:57 +0100, Matthias Brugger wrote: > > [...] > >> The property expects size-cells to be two, but U-Boot will use one >> cell if no >> size-cells are defined in the device node (which is not the case) and >> therefor

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-01-10 Thread Peter Maydell
On Thu, 9 Jan 2020 at 13:11, Robin Randhawa wrote: > I dumped the DTB to the host filesystem using GDB and 'dump mem' then > dtc'd it to get the DTS. The easier way to dump the DTB is to pass QEMU the extra command line option -machine dumpdtb=file.dtb (plus all the other arguments for the

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-01-09 Thread Robin Randhawa
On Thu, 2020-01-09 at 15:57 +0100, Matthias Brugger wrote: [...] > The property expects size-cells to be two, but U-Boot will use one > cell if no > size-cells are defined in the device node (which is not the case) and > therefor > will see > > Bank1: Flashbase 0x0 0x0 Flashsize

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-01-09 Thread Matthias Brugger
[adding Stefan as the maintainer of drivers/mtd/cfi_*] On 09/01/2020 14:11, Robin Randhawa wrote: > Hi Matthias. > > On Thu, 2020-01-09 at 12:12 +0100, Matthias Brugger wrote: > > [...] > >> Can you pinpoint me to where I can find the DTS used by U-boot. > > As per my understanding the DTB

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-01-09 Thread Robin Randhawa
Hi Matthias. On Thu, 2020-01-09 at 12:12 +0100, Matthias Brugger wrote: [...] > Can you pinpoint me to where I can find the DTS used by U-boot. As per my understanding the DTB for this virtual platform is generated by qemu and handed to u-boot. I dumped the DTB to the host filesystem using

Re: Bug: qemu_arm64: Cannot access the second flash bank

2020-01-09 Thread Matthias Brugger
Hi Robin, On 01/01/2020 19:20, Robin Randhawa wrote: > Hi folks. > > [CC'ing some hopefully relevant folks]. > > As of: > > commit 0ba41ce1b7816c229cc19e0621148b98f990cb68 > libfdt: return correct value if #size-cells property is not present > > .. accesses to the second flash bank on the

Bug: qemu_arm64: Cannot access the second flash bank

2020-01-01 Thread Robin Randhawa
Hi folks. [CC'ing some hopefully relevant folks]. As of: commit 0ba41ce1b7816c229cc19e0621148b98f990cb68 libfdt: return correct value if #size-cells property is not present .. accesses to the second flash bank on the qemu_arm64 virtual board appear broken. To demonstrate, consider that the