Hi Geert, On Tue, Jan 19, 2016 at 3:16 AM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > Hi Magnus, > > On Mon, Jan 18, 2016 at 6:48 AM, Magnus Damm <magnus.damm@xxxxxxxxx> wrote: >> ARM: shmobile: r8a7795 Salvator-X IPMMU 4 GiB RAM test code >> >> [PATCH/RFC 01/02] iommu/ipmmu-vmsa: Use 64-bit masks >> [PATCH/RFC 02/02] arm64: dts: Salvator-X: Enable 4 GiB of RAM >> >> This code simply enables 4 GiB of RAM on Salvator-X after >> adjusting the IPMMU driver to tell the Linux driver model >> that the device it is managing is able to do 64-bit bus >> mastering. > > Thanks for your patches! Thanks for testing! >> Not for upstream merge. Patch 1/2 will be rolled into a larger >> series for the IPMMU driver in the future. Patch 2/2 depends >> on firmware updates, so the integration needs to be correctly >> ordered to keep things smooth. > > I assume the below means I need a firmware upgrade? > > Booting Linux on physical CPU 0x0 > Linux version 4.4.0-salvator-x-08629-g82658e5263e549fc (geert@ramsan) > (gcc version 4.9.0 (GCC) ) #378 SMP Mon Jan 18 19:11:13 CET 2016 > Boot CPU: AArch64 Processor [411fd073] > bootconsole [uart0] enabled > debug: ignoring loglevel setting. > efi: Getting EFI parameters from FDT: > efi: UEFI not found. > On node 0 totalpages: 1048576 > DMA zone: 3584 pages used for memmap > DMA zone: 0 pages reserved > DMA zone: 262144 pages, LIFO batch:31 > Normal zone: 10752 pages used for memmap > Normal zone: 786432 pages, LIFO batch:31 > Unable to handle kernel paging request at virtual address 3fffffbe01bfe148 > pgd = ffffffc0014b6000 > [3fffffbe01bfe148] *pgd=000000073fdfc003, *pud=000000073fdfc003, > *pmd=006000073fe00711 > Internal error: Oops: 96000004 [#1] SMP > Modules linked in: > CPU: 0 PID: 0 Comm: swapper Not tainted > 4.4.0-salvator-x-08629-g82658e5263e549fc #378 > Hardware name: Renesas Salvator-X board based on r8a7795 (DT) > task: ffffffc000743100 ti: ffffffc000738000 task.ti: ffffffc000738000 > PC is at set_pfnblock_flags_mask+0x4c/0x94 > LR is at set_pageblock_migratetype+0x50/0x58 Yeah, lets try again after updating the firmware on the boards! Cheers, / magnus
