Messages in this thread | | | From | "Luck, Tony" <> | Subject | RE: [RFC] avoid indirect calls for DMA direct mappings v2 | Date | Tue, 11 Dec 2018 16:42:55 +0000 |
| |
> This should fix it: ... > +#include <linux/dma-noncoherent.h>
Not quite. Still have an issue with __phys_to_pfn(paddr)
Trying ti #include <asm-generic/memory_model.h> gave we a raft of redefined macros. So I just added
#define __phys_to_pfn(paddr) PHYS_PFN(paddr)
to arch/ia64/mm/init.c
That made the build work. But boot spontaneously resets after:
mptsas: ioc1: attaching ssp device: fw_channel 0, fw_id 6, phy 6, sas_addr 0x5000c5000ecada69 scsi 5:0:0:0: Direct-Access SEAGATE ST9146802SS 0003 PQ: 0 ANSI: 5 EFI Variables Facility v0.08 2004-May-17 sd 5:0:0:0: [sdb] 286749488 512-byte logical blocks: (147 GB/137 GiB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sdb2 sd 5:0:0:0: [sdb] Attached SCSI disk
But that might not be your fault. My ancient system is getting flaky. A v4.19 build that has booted before is also resetting :-(
-Tony
| |