On Wed, Jan 16, 2019 at 10:46:45AM +0100, Thomas Huth wrote: > > +obj-$(CONFIG_HTIF) += riscv_htif.o > > riscv_htif.o seems to belong to the spike machine, so I think you don't > need a separate config switch for that and could simply use CONFIG_SPIKE > here. > > > +obj-$(CONFIG_HART) += riscv_hart.o > > +obj-$(CONFIG_SIFIVE) += sifive_e.o > > +obj-$(CONFIG_SIFIVE) += sifive_clint.o > > +obj-$(CONFIG_SIFIVE) += sifive_prci.o > > +obj-$(CONFIG_SIFIVE) += sifive_plic.o > > +obj-$(CONFIG_SIFIVE) += sifive_test.o > > +obj-$(CONFIG_SIFIVE) += sifive_u.o > > Looking at the output of "qemu-system-riscv64 -M help", sifive_e and > sifive_u are two separate machines. So should we use two different > config switches here? > > > +obj-$(CONFIG_SIFIVE) += sifive_uart.o > > +obj-$(CONFIG_SPIKE) += spike.o > > +obj-$(CONFIG_RISCV_VIRTIO) += virt.o > > The machine is only called "virt", so I'd suggest to call the config > switch CONFIG_RISCV_VIRT only. > > Thomas
Hello Thomas, Thanks, i did below changes +obj-$(CONFIG_SPIKE) += riscv_htif.o +obj-$(CONFIG_HART) += riscv_hart.o +obj-$(CONFIG_SIFIVE_E) += sifive_e.o +obj-$(CONFIG_SIFIVE) += sifive_clint.o +obj-$(CONFIG_SIFIVE) += sifive_prci.o +obj-$(CONFIG_SIFIVE) += sifive_plic.o +obj-$(CONFIG_SIFIVE) += sifive_test.o +obj-$(CONFIG_SIFIVE_U) += sifive_u.o +obj-$(CONFIG_SIFIVE) += sifive_uart.o +obj-$(CONFIG_SPIKE) += spike.o +obj-$(CONFIG_RISCV_VIRT) += virt.o Regards, Yang