On Sat, Mar 13, 1999 at 02:10:35PM +0100, Jochen Kuepper wrote:
> It's kind of easy where to put the headers, it just needs to be defined. The
> asm files can go with the Standard-Linux asm's into /usr/include/asm. (Well,
There are two kinds of headers. Headers that belong to RTL modules alone and headers
needed for the patched Linux. The headers that are not needed to compile linux should
go in rtl/include and I have been separating out headers so that rtl modules make
minimal
reference to Linux kernel include files.
I think the hierarchy should be
rtlinux
linux rtl
rtl/include
The divsion should be on what needs the headers, not on asm vs linux.
> The modules should go into the current kernels module dir - that is
> /lib/modules/`uname -r`/misc/ usually, but on RedHat it needs some more
> tweaking.
Yes.
> One step further would be to put everything in the /usr/src/linux tree
> initially and let make modules and make modules_install (from Standard Linux
> Makefiles) do the job. This adds some complexity to the patch, but to me it
> looks like a nice aim.
I want to keep a separation. RTL programmers don't need to be kernel hackers and
vice-versa.
That is, if you want to learn how to write RTL tasks and handlers, you should not
necessarily
need to learn the Linux kernel os tree. Furthermore, it's not good modularity to put
rtl headers, only
referenced by rtl modules, in the linux kernel tree. Ideally, one should be able to
pop a new patched linux kernel
into rtlinux/linux or a new rtl distribution into rtlinux/rtl without worrying about
the other side.
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
