(Which IMHO in many cases seems silly, as AFAIK, you can happily use
vfork() if there is
an MMU, too, in nearly (?) all cases when you can _simply_ (without
any other code change) replace fork() with vfork() anyway. )
Yes, pretty much true...
But userland software I all over the place see funny #defines for "fork"
or things like
#ifdef EMBED
p = fork();
#else
p = vfork();
#endif
Moreover the name of the "EMBED" define seems quite outdated, as
today, many embedded devices do provide an MMU.
Yes, definitely true. I tend not to use it any more.
OK, but what to do about already existing code ....
I don't know if there is some change on that issue planned (e.g.
using CONFIG_MMU, in User Land as well).
Currently I use __uClinux__ in userland for this. (Which isn't perfect
either, if you use a standard gnu linux configured gcc for compiling
uCLinux systems you need to manually define it too).
The NIOS uCLinux, I'm working with, some day soon will get a
configuration setting if or if not an MMU is to be used, as the CPU
itself can be configured to feature an MMU or not.
The "powers" (Thomas) decided that it still is called a uCLinux
distribution.....
So maybe a setting "USE_MMU" or something like this seems more appropriate.
-Michael
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
