Hello,
now with SVN up and running, it is much less painful to move some files or even directories around in RTnet. We will have to think about the source tree structure anyhow as kernel 2.6 support requires that only one .ko file is produced per directory.
So, let's take this chance and reorganise some things. Here is the structure I would like to propose (only directories and modules are listed):
Documentation/
add-ons/
examples/
frag_ip/
frag_ip.ko
raw_packets/
raw_packets.ko
round_trip_time
client/
rt_client.ko
server/
rt_server.ko
rtmac/
event/
handler/
rt_handler.ko
collector/
rt_collector.ko
netshm/
netshm.ko
kernel_demo/ rtt/
multi_client/
rt_multi_client.ko
client/
rt_client.ko
server/
rt_server.ko
lxrt/
select/
rt_server.ko
rtcap/
rtcap.ko
rtnetproxy/
rtnetproxy.koconfig/
autoconf/core/
rtnet.ko
include/
<according to layout of core/>
ipv4/
rtipv4.ko
packet/
rtpacket.ko
rtcfg/
rtcfg.ko
rtmac/
rtmac.ko
nomac/
nomac.ko
tdma/
tdma.kodrivers/
experimental/
3c59x/
3c59x-rt.ko
8139too/
8139too-rt.ko
eepro100/
eepro100-rt.ko
loopback/
loopback-rt.ko
mpc8260_fcc_enet/
mpc8260_fcc_enet-rt.ko
mpc8xx_enet/
mpc8xx_enet-rt.ko
mpc8xx_fec/
mpc8xx_fec-rt.ko
natsemi/
natsemi-rt.ko
pcnet32/
pcnet32-rt.ko
smc91111/
smc91111-rt.ko
tulip/
tulip-rt.ko
via-rhine/
via-rhine-rt.kortai_rtdm/
rtai_rtdm.kotools/
Comments/suggestions/etc. are welcome!
Jan
smime.p7s
Description: S/MIME Cryptographic Signature

