I mostly work from a split screen editor.

I steal from myself,  and anyone else handy.

You can't write a manual detailed and unambiguous enough for someone to write working code in even two or three tries,
but most people can get a modified example to compile after two tries,  to run after three,  and to do what was wanted in less than a doxen tries.
 

The examples that ship with a product ultimately determine how it will be used,  and by whom.

Since rtl makes both real-time and unix knowledge demands on its users,  it is narrowing the base rather quickly to very few poeple.

The "out of the box experience" is likely to be frustrating for a neophyte with a deadline.
 

By the way,  in my experience,  the minute you have a gui  up with some of your own data and functionality,  you develope
a great deal of interest,  and some degree of authority in the minds of a beholder.

Functionality as well as style are best learned by example.

The viability of rtl will be deermined largely by the ability of the unfamiliar to use it to impress the uninformed.
 

YES,  lets have lots of working examples that are considered a regression suite;  that is,  all examples that are included in the
release.

Regards,
 

Mike
 
 
 
 

John VanLoon wrote:

If you are busy do not read this. I made a programming mistake plain and
simple.

Thanks to everyone for their replies. In my typical form I had assumed
that my code was wrong. After playing with trying to delay the exit and
using printk and rtl_printf (very nice BTW) nothing was helping. Then I
tried running it at the console and messages started showing up. Right at
that time I read a message saying rtl_printf only works at a console not
under X. To this I concur and am glad to be able to reproduce the
experiment :.}. However the machine still hung at rmmod.
Then after all of this I noticed that I had used
close(rt_fifo[COMMAND_FIFO]); in place of rtl_destroy(COMMAND_FIFO);
Let me just mention that this is likely to freeze the machine if you put
it in a module (The close function is available to your code). After
changing it to rtl_destroy everything was happy!

Is there a desire for a template to use to start from? Something like a
thread with shared memory and a little gui on the user side. Throw in a
make file and Tada. So that is what I have, mostly. I will freeze this
and hold on to it for a week or so. If people would like it please email
me, I can clean it up a little and document it properly. Perhaps we could
include it into the distribution examples as a starting point for new
inductees.
Any takers?
John
[EMAIL PROTECTED]
--- [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/

-- 
  Alcatel USA                        Internet: [EMAIL PROTECTED]
  1000 Coit Road Plano, Texas 75075
  **** The opinions expressed are not those of DSC Communications, Inc ****
  
  
  
  "Keep things as simple as possible,   but no simpler".   A. Einstein
 
begin:vcard 
n:cravens;mike
tel;home:(972) 423-9463
tel;work:(972) 477-7077
x-mozilla-html:TRUE
adr:;;1000 Coit Rd;Plano;Tx;75075;USA
version:2.1
email;internet:[EMAIL PROTECTED]
title:Senior Software Engineer
x-mozilla-cpt:;-10560
fn:[EMAIL PROTECTED]
end:vcard


Reply via email to