RTL doesn't have any requirements as to how much you build into the
kernel. The question seems to come down to how much can you strip down
vanilla Linux. You shouldn't need many daemons (or any, really) for a
minimal system with a network.
You can do xmon or kgdb debugging via a serial line, they're built into the
tree and I use them pretty often.
If you could be more specific about what network services you need, do you
need any disk controller drivers and how much memory you're going to have
it would be easier to tell you if you if linux/ppc + rtl can do the job.
My general feeling and answer is with a little work it can do the job very
well.
} I guess that's one of the things I'm trying to find out. The more there is,
} the
} more we have to port and maintain. All that's needed is enough OS to
} simultaneously support TCP/IP applications and real-time applications. The
} real-time applications would communicate with the TCP applications using
} the RT-FIFOs; the TCP applications would communicate with the outside
} world. It would be nice to have remote GDB debugging facilities (via
} existing
} Ethernet or a serial line). If that is not available, we can use JTAG/COP
} into
} the PowerPC processor.
}
} I suppose to have the TCP stack, the networking daemons and a Flash file
} system are also required?
}
} It sounds like most RTL implementations are full-Linux over the real-time
} kernel, so far. (We're currently using VxWorks for embedded real-time
} stuff.)
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
