Changeset View
Standalone View
sys/conf/files.arm64
Show First 20 Lines • Show All 565 Lines • ▼ Show 20 Lines | cloudabi64_vdso.o optional compat_cloudabi64 \ | ||||
compile-with "${CC} -x assembler-with-cpp -shared -nostdinc -nostdlib -Wl,-T$S/compat/cloudabi/cloudabi_vdso.lds $S/contrib/cloudabi/cloudabi_vdso_aarch64.S -o ${.TARGET}" \ | compile-with "${CC} -x assembler-with-cpp -shared -nostdinc -nostdlib -Wl,-T$S/compat/cloudabi/cloudabi_vdso.lds $S/contrib/cloudabi/cloudabi_vdso_aarch64.S -o ${.TARGET}" \ | ||||
no-obj no-implicit-rule \ | no-obj no-implicit-rule \ | ||||
clean "cloudabi64_vdso.o" | clean "cloudabi64_vdso.o" | ||||
cloudabi64_vdso_blob.o optional compat_cloudabi64 \ | cloudabi64_vdso_blob.o optional compat_cloudabi64 \ | ||||
dependency "cloudabi64_vdso.o" \ | dependency "cloudabi64_vdso.o" \ | ||||
compile-with "${OBJCOPY} --input-target binary --output-target elf64-littleaarch64 --binary-architecture aarch64 cloudabi64_vdso.o ${.TARGET}" \ | compile-with "${OBJCOPY} --input-target binary --output-target elf64-littleaarch64 --binary-architecture aarch64 cloudabi64_vdso.o ${.TARGET}" \ | ||||
no-implicit-rule \ | no-implicit-rule \ | ||||
clean "cloudabi64_vdso_blob.o" | clean "cloudabi64_vdso_blob.o" | ||||
# Xen | |||||
dev/xen/devicetree/xen-dt.c optional xenhvm fdt | |||||
royger: Should this rather be in sys/dev/xen rather than in an Arm specific directory? | |||||
Done Inline ActionsMaybe. Depends upon whether this can reasonably be shared by multiple architectures. This would likely share with implementation attempts for aarch32 or other ARM on aarch64 Xen. I'm less sure about how well it will share with RISC-V. ehem_freebsd_m5p.com: Maybe. Depends upon whether this can reasonably be shared by multiple architectures. This… | |||||
Done Inline ActionsThe device-tree node is pretty generic. So I would hope that any architecture using Device-Tree would end up to use/improve it rather than reinventing the wheel. julien_xen.org: The device-tree node is pretty generic. So I would hope that any architecture using Device-Tree… | |||||
Done Inline ActionsI don't see anything in this file that couldn't be shared, it's all pretty standard fdt/newbus stuff. I'm excluding xen_init(), which I think we agree will go elsewhere under sys/arm64/. So yes, this should go in the generic code under sys/dev/xen. Please also make this line optional on fdt. mhorne: I don't see anything in this file that couldn't be shared, it's all pretty standard fdt/newbus… | |||||
Done Inline ActionsPreferences between sys/dev/xen/dt/xen-dt.c, sys/dev/xen/devicetree/xen-dt.c or other? I was going to argue for the first due to being shorter, but thanks to filename completion I'm thinking the second.
On the queue. ehem_freebsd_m5p.com: Preferences between sys/dev/xen/dt/xen-dt.c, sys/dev/xen/devicetree/xen-dt.c or other?
I was… | |||||
Done Inline Actions
ehem_freebsd_m5p.com: > I don't see anything in this file that couldn't be shared, it's all pretty standard… | |||||
Done Inline ActionsDepending on fdt is now done. ehem_freebsd_m5p.com: Depending on fdt is now done. |
Should this rather be in sys/dev/xen rather than in an Arm specific directory?