Messages in this thread | | | Date | Mon, 20 Jan 2003 20:12:50 +0100 | From | Sam Ravnborg <> | Subject | Re: [2.5] initrd/mkinitrd still not working |
| |
On Mon, Jan 20, 2003 at 03:52:50PM +0000, John Levon wrote: > > As to why the .o -> .ko name change was necessary, I have no idea. > > Rusty? > > For one thing, it means you can do : > > obj-$(CONFIG_OPROFILE) += oprofile.o > oprofile-y := $(DRIVER_OBJS) init.o > timer_int.o > oprofile-$(CONFIG_X86_LOCAL_APIC) += nmi_int.o op_model_athlon.o \ > op_model_ppro.o op_model_p4.o
The above mentioned possibility to list 'members' of a composite object by means of either: oprofile-y or oprofile-objs
has nothing to do with the .ko extension. But that feature may have been added in the same time-frame though.
I do not recall exactly whay Kai introduced the .ko extension, but without checking I assume that makes it easier / possible to do some added tricks in the makefiles.
Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |