On Tue, Jan 04, 2000 at 07:58:18PM -0800, phil wilshire wrote:
> void rtl_release_global_irq( unsigned int irq);
> Question do we need to assign an IRQ to a CPU ??
rtl_focus_global_irq(irq,bitmap);
> rtl_pthread_t * rtl_pthread_create( char * name,rtl_pthread_attr_t *
> attr
> void * ( *start_routine)(void *), void * arg);
>
One should not be required to run /proc to run RTLinux.
There are several overheads and it also makes it impossible to
run the RTkernel freestanding, which is necessary for some applications.
How about
rtl_proc_name_thread("name",thread)
> Notes...
> allocate from a preset stack of task structures
Not always a good idea. This should definitley be user selectable.
> " real " Pthreads.
RTLinux pthreads are real.
>
> rtl_fifo_t * rtl_fifo_create( char * name , int size );
>
> Note the fifo has a name like the task that appears in /proc/rtl/fifos
> An arbitary fifo number will be used .
I very much like the way we do it now with the posixio module.
1. if you want the raw interface, you use numbers
2. if you want the posix interface you use open("/dev/rftx").
>
> Shm
Tomasz should comment.
> Don't worry about how it is going to work for now just think about the
> presentation and features.
Keep in mind
(A) no user should have to pay a cost in program size, complexity, or
performance for a "feature" she does not need.
(B) the components should be as freestanding as possible and not
have gratuitous interdependencies.
--- [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/
