On Tue, Oct 26, 2004 at 01:24:50AM +0200, Jan Kiszka wrote:
> 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):
> add-ons/
What about 'addons'? RTAI-3.x has rtai-addons
saves 1 character :)
> examples/
I'll begin with examples reorganisation after this mail...looks good
> rtcap/
> rtnetproxy/
> core/
> rtnet.ko
> ipv4/
> rtipv4.ko
> packet/
> rtpacket.ko
Is ipv4.ko and packet.ko already hotplugable (i.e. seperately loadable)?
If not, it makes no sense to build seperate modules ATM, makes it?
> rtcfg/
> rtcfg.ko
> rtmac/
> rtmac.ko
> nomac/
> nomac.ko
> tdma/
> tdma.ko
How do you think about a version number in tdma? Like -1.0 or -v1? To
prevent confusion with the new tdma incarnation.
> drivers/
I've just comitted the new drivers layout to CVS errr... SVN
Works (compiles) here....
> Comments/suggestions/etc. are welcome!
Marc
--
<dapeta> Use Windows - REBOOT
Use Linux - be ROOT
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
RTnet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/rtnet-users
