|
From: Tom H. <to...@co...> - 2005-03-30 13:12:50
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> Instead, it would be better to put the Kal module/subsystem
> in its own directory, kal, and put all the arch/os specific bits
> just for Kal in there:
>
> kal/pub_core_kal.h -- services exported from kal; core but not
> tools may use these
> kal/pub_tool_kal.h -- services exported from kal; both core and
> tools may use these
How are we going to decide what is and isn't exported? Do we make
everything core only to start with and move it to the tool header
if a tool needs it? or make everything available to tools unless
we have some reason to believe it can only work in the core?
> kal/kal-x86-linux.c -- x86-linux specific implementation
> kal/kal-amd64-linux.c -- amd64-linux specific implementation
> kal/any_other_name.c -- generic implementation
I'm not sure you can have a generic implementation of anything in the
kernel abstraction layer ;-)
I also added a kal-linux.c for things common to all linux builds
regardless of architecture.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|