[Prev][Next][Index][Thread]
Re: oskit/linux?!?
If you are starting with 2.4 code, probably the easiest thing to do is make
a separate linux/2.4/{src,dev,...} similarly to how the freebsd/3.x
directoy was added alongside old freebsd 2.x code. That is, if the
existing glue code is not easy to adapt, just copy and tweak it for 2.4
instead. (Though it might be easy to make the single set of glue source
files use #if LINUX_KERNEL_VERSION for the differences.)
It's pretty doable (and worthwhile) to upgrade the x86 and arm code from
linux to 2.4 as well, but that is a bit of work for those who know how to
do it and probably a world of frustration for those just trying to figure
it out. (My plan, should I ever get a large sack of round tuits, would be
to first update to the latest 2.2.x there is, which should really not be
much work (you just have to do it right) and produce a relatively stable
result people can use instead of the current oskit; then do a wholesale
update to 2.4 code, which will be more work and is likely to become
unstable for a while.)
References: