> > config XILINX_EDK
> > bool
> > depends on XILINX_VIRTEX || XILINX_MICROBLAZE
> > default y
>
> I don't have any problem with adding XILINX_EDK (or
> whatever), but think particular layout is back-assward.
> Rather than XILINX_EDK depending on XILINX_VIRTEX/MICROBLAZE,
> XILINX_VIRTEX/MICROBLAZE should 'select' XILINX_EDK and you
> need to drop the 'default y' line.
> Otherwise the XILINX_EDK option shows up in non-edk config files.
Good point...
> Why still have XILINX_EDK? I thought you meant replace
> XILINX_EDK with XILINX_DRIVERS.
Yes, that's what I was suggesting.
But I think that Andrei still wants to use XILINX_EDK to pull in the
stuff in drivers/xilinx_common.
# The Xilinx OS common code
obj-$(CONFIG_XILINX_EDK) += xbasic_types.o xpacket_fifo_l_v2_00_a.o \
xpacket_fifo_v2_00_a.o xversion.o \
xdma_channel.o xdma_channel_sg.o
Which you wouldn't want if you were able to build a kernel completely
from 'non-edk' drivers.
Steve
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
