Greetings all, sorry for a somewhat long winded message I'll put questions first, history of why i would like to know 2nd, a brief extract about RTLinux from there web site for reference purposes, and finally my hardware platform description. If you are into data acq & contol do look at the info on this board family, it had linux drivers and is guarenteed to do all i/o Simultaneous due to the onboard DSP engine. http://www.ueidaq.com/cgi-bin/Products.cgi?pn=PD2-MFS-8-500/14 ) WHAT I WOULD LIKE TO ASK IS :- ============================== q1. is Suse Linux product ( 6.1 or 6.4) comparable with RTLinux ? q2. or is there a RT version of SuSE Linux ? q3. or it appears that RTLinux is "merged" with Linux 2.2 kernels could it use SuSE kernel instead ? Has anybody done this task ? Q4. any other comments in relation to real time operation would be much appreciated .. especially as i would like to stay with Suse product if possible I hope you can help in this matter David Broadbent GradDipRob =========================================================== HISTORY..... In January 2000 I loaded SuSE Linux 6.1 on to a new computer I am setting up. I have just purchased ( 7th June 200) a Multi-function Data subsystem pcb ( see http://www.powerdaq.com/ ) for this computer to perform initially a specific ' Closed loop" test on some remote ( 1 metre distant of computer) phase measuring hardware. The Data Acquisition pcb supplier suggested I should use RTLinux and I have been looking at their website http://www.rtlinux.org/rtlinux.new/index.html and i quote from their faq ================================================================= Q: What's the basic idea of RTLinux? A: RTLinux is a small, deterministic, real-time operating system that is somewhat like a single POSIX process sitting on a bare machine. Hard realtime applications are threads and signal handlers in this process. Linux runs as the lowest priority thread of the RTLinux kernel and it is made always pre-emptible. The RTLinux programming model is that anything that has strict timing requirements should be written as a thread or signal handler (interrupt handler) and whatever does not need hard realtime should go into Linux. This allows us to ep the RT side small, deterministic and as fast as the hardware will permit, while still drawing on Linux for sophisticated services and applications. The basic mechanism that makes RTLinux work is protected under U.S. Patent 5,995,745 and is freely licensed to RTLinux users for commercial and non-commercial purposes ------ etc. ************************************************************ DETAILS OF MY HARDWARE PLATFORM ARE AS FOLLOWS 1. Abit MoutherBoard BP6 with Dual 466meg Celeron processors 2. 128 Meg of ecc memory ( soon to be 256Meg ) 3. 2 only Ultra DMA66 ide with Segate Medalist 17.2 gig hard drives 4. UEI PowerDAQ II (pci bus) Multi-Function board ( see this web address for more details on board as it looks very interesting and powerfulhttp://www.ueidaq.com/cgi-bin/Products.cgi?pn=PD2-MFS-8-500/14 ) with 6 channel Simultaneous Sampling 1meg sampling 12 bit a/d, 2 by 200khz - 12 bit d/a's, digital i/o, counter-timers with a Motorola 66Mhz DSP 56301 as onboard processing engine. 5 S3 ViRGE/DX on board Video card (pci bus) 6a. AdvanSys ABP-3925 Scsi card (pci bus) 6b. CD reader/writer ( pci bus) 7. Creative Labs Ct4810 sound card (pci bus) 8. EZ-32000PCT+ network card (pci bus) ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com -- [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/
