>>  > I meant it to be port dependent, so the addition to sh3 was a mistake.
>>  > Although it can probably be shared between various ports with the
>>  > same CPU eventually.
>> Eventually?  Sounds like a hard-requirement.  Now LKMs for procfs
>> for the same MACHINE_ARCH are not compatible.
>If an LKM contains port-specific information that can't be avoided
>of course. procfs currently has no port specific information
>(not in default mode, which will probably never have that, nor
>in linux mode).

	distrib/setes/lists/base/ad.m68k lists lkm/procfs.o, so it leads me to
	believe that lkm/procfs.o is per CPU.  i think either distribution
	file list, or sys/arch/*/*/procfs_machdep.c, should be corrected
	somehow.

itojun