On Fre, 12 Mär 1999 [EMAIL PROTECTED] wrote:
>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
I think all headers I need to write RTL modules (besides the base modules)
should be below /usr/include ! If this is what you meant, I haven't understood
your comment.
Still the Standard Linux headers must stay in /usr/include/linux, that's why
I proposed to put the RTL headers into /usr/include/rtlinux ( or .../rtl ).
I think it is not good to put the headers anywhere into the sources, cause I
have several /usr/src/rtl-dirs, usually, and just put the headers into
/usr/include/.../ whenever I put the corresponding modules int /lib/modules.
Moreover I set C_INCLUDE_PATH, so the compiler uses the /usr/src/rtlinux
headers without any intervention, like the system using the /lib/modules
modules and not some modules lying in /usr/src/... .
That way I have to think about all this stuff at install time and can forget it
than - actually my collegue with the RT-Linux project doesn't have to care on
that at all.
>The divsion should be on what needs the headers, not on asm vs linux.
Well, that's the way it is in good,old Linux, why not keep it.
>> 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.
Oh yes, I can follow that. My point of view was differnt, but this seems fine
to me now, too.
Greetings,
Jochen
-----------------------------------------------------------------------
Jochen Küpper
Heinrich-Heine-Universität Düsseldorf [EMAIL PROTECTED]
Institut für Physikalische Chemie I
Universitätsstr. 1, Geb 26.43 Raum 02.29 phone ++49-211-8113681
40225 Düsseldorf fax ++49-211-8115195
Germany http://www-public.rz.uni-duesseldorf.de/~jochen
-----------------------------------------------------------------------
--- [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/
