From: Steven B. <sb...@st...> - 2003-08-08 17:11:07
|
On Fri, Aug 08, 2003 at 06:21:03PM +0200, Robin Farine wrote: > On Fri, 2003-08-08 at 17:18, Steven Bytnar wrote: > > * One set using the target compiler, or only udisetup, so you can install > > UDI binaries on the target host. Also, parts of the linux source tree > > are required at udisetup time so the UDI's ELF object file can be linked > > into a kernel module. > > Is this second set absolutely required? Can't I build a host version of > udisetup that builds target kernel modules? Sure, you could do this, but you'd have to teach udisetup to drop the built modules in a local directory instead of /lib/modules/*. > Or would it simplify things if I run the UDI environment in a user > space process using the POSIX env? In fact, I'd prefer this > configuration since it better matches my views of a reliable OS, more > particulary on embedded systems where you cannot easily reach the > reset button. But then I guess I would have to add a mechanism > responsible for translating hardware interrupts into user space > threads events, hmm ... Major changes would be needed to make the UDI Posix environment able to be a UDI execution context for the kernel. The ideal way to do this would be to implement UDI Domains. A quicker way would be to implement a udi_mei_call transport/bridge/syscall from kernel to userland and make the interrupt preprocessing translist be the only thing that executes directly in kernel context. Calling back into userland would be a bit more tricky though, since udi_mei_call is a bi-directional interface. The time to implement UDI Domains or UDI Posix-Kernel transisions would be much larger than reworking the existing UDI build environment to do cross-building. By the way, if you've got a budget or time constraint that you'd like to meet, Software Technologies Group, the company I work for, could help you achieve your goal. We've done this stuff before. http://www.stg.com/ --Steve _______________________________________________ UDI-Tech mailing list UDI...@pr... http://lists.projectudi.org/mailman/listinfo/udi-tech |