Quoth [EMAIL PROTECTED]: > As I know, uclinux has flat address memory space,all the > applications are in the same address space,right? > > So,does it mean it doesn't differentiate kernel space and user space?
On systems with MMUs, it's just like regular Linux. On systems without MMUs, user and kernel share the same address space, so it's *possible* to violate the normal rules and eg. return a direct pointer from a driver and access it from user space, or entirely within user code manipulate memory-mapped registers and the like. (Or, for that matter, have a rogue userspace program completely screw up your kernel memory.) Just because it's possible, though, doesn't make it good practice. It's still better to try to keep things logically separate and keep driver-like code in the kernel (especially because it has better support for that sort of thing). And of course without doing truly evil things you still have to put all ISRs in the kernel. _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
