[rtl] test
test. Please ignore. -- Key fingerprint = B3DC 5F98 96F2 0C00 830F DC94 AD46 5F13 FFB2 4F73 PGP signature
Re: [rtl] what is the recommended distribution of Linux for rtlinux 3.0?
On Thu, Mar 08, 2001 at 03:03:31PM -0500, Stebbins, Andrew wrote: > what is the recommended distribution of Linux for rtlinux 3.0? There really isn't one, especially considering that some distributions don't cover all three platforms that we currently support (ia32, PowerPC, and Alpha). I suppose you could take our packaging RTLinux as RPMs as an endorsement of any distribution that uses RPMs; truth be told, most of those RPMs were built on Debian systems :-) I discourage using Mandrake because it doesn't install many needed development utilities by default. RedHat seems okay for ia32 and maybe Alpha, just stay away from 7.0 (try 6.2). Yellowdog seems really decent for PowerPC. Me, personally, I use Debian. It's stable, consistent and runs on all three platforms we currently develop on. It's just hard to install and doesn't have some packages because of licensing issues (ie no KDE). -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] bug in rtf handler ??
On Fri, Mar 02, 2001 at 03:18:09PM -0700, Nathan Paul Simons wrote: > Okay, I'll see if I can get a patch coded up right quick. I'll > (hopefully) post it to the list in about an hour. On second examination, it looks like this is gonna take a little longer. I forgot it was a long time ago I did this patch. Hopefully I will have it done by tomorrow night. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] bug in rtf handler ??
On Fri, Mar 02, 2001 at 01:47:59PM +0100, Olaf Petzold wrote: > Imo it's a bug/design fault- if I need to write to the rtf to kick the thread > to fill me the buffer I don't need a handler on user read ops. > > To Nathan: Imo to poll() is an access. I ask for new data - if there are new I > get it from the buffer. If I don't want to get the prepered data I can leave > the handler - the task is reponsible for filling the rtf with data even is > there is no callback. Therefore poll() gets only data if the kernel task has > data. handler callback is asyncronous to the rt task. Okay, I'll see if I can get a patch coded up right quick. I'll (hopefully) post it to the list in about an hour. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] bug in rtf handler ??
On Fri, Mar 02, 2001 at 09:36:00AM +0100, Olaf Petzold wrote:
> never called imo:
>
> int rtfHandler(size_t fifo)
> {
> size_t sz;
> const char *msg = "Hallo World\n";
> sz = strlen(msg);
> rtf_put(number(), &sz, sizeof(sz));
> rtf_put(number(), (void*)msg, sz);
> return 0;
> }
>
> The first read op from user space should call the handler above. It puts at
> first the stringlength and then the string self. On each call the rtf buffer is
> filled with the same string. I'm on a wrong way ?
It looks right, but I'll double-check it when I get some free time.
> Is it really neccessary ? man page says:
>
> rtf_create_handler installs a handler which is executed when data is written
> to or read from a real-time fifo (RT-FIFO). fifo is an RT-FIFO that must
> have previously been created with a call to rtf_create. handler is
> then called whenever a Linux process accesses that fifo.
"accesses" is a bit vague. For instance, is a call to poll() on that
device an "access"? On the other hand, "when data is written to or read from"
could easily be interpreted as not calling the FIFO handler when the FIFO is
empty and something tries to read from it, because no data will be read from
the FIFO. I will have to look into getting the docs changed, one way or
another.
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
Re: [rtl] bug in rtf handler ??
*Never* called? Or just not called when the FIFO is empty and you
do a read from it? This is a known problem that I had a quick "fix" for,
but was never put in to any releases of RTLinux. I say "fix" because I am not
sure if it would be compliant with POSIX to act this way (in other words, it
may be correct by POSIX standards to not call the handler on reads when the
FIFO is empty). This does seem to severely limit the usefulness of FIFOs,
though. My suggestion is to do sort of an ack an response scheme in your
handler where the userspace program sends a request via another FIFO, then
the handler that gets called for that FIFO writes to the FIFO that the user
space program is reading from. That, or just have a real-time task write
data to the FIFO whenever it has some to write, until the FIFO is full, and
have the user space program poll on that FIFO.
On Thu, Mar 01, 2001 at 09:27:47AM +0100, Olaf Petzold wrote:
> Hello,
>
> the following installed rtf handler doesn't work on read ops from user space.
> On write ops the handler is called. Refering to the man page, both should work.
> My fault or a bug in rtf_fifo of 2.2.18-rtl3-final?
>
> Regards
> Olaf
> ---
> [...]
> #define RTF 0
> size_t number(void) { return RTF; }
>
> int rtfHandler(size_t fifo) // never called on read ops from user mode
> {
> size_t sz;
> const char *msg = "Hallo World\n";
>
> DBG("notify Rtf%d\n", fifo);
> sz = strlen(msg);
> rtf_put(number(), &sz, sizeof(sz));
> rtf_put(number(), (void*)msg, sz);
>
> return 0;
> }
>
> int init_module(void)
> {
> int ret;
> size_t sz = 4000;
>
> (void)rtf_destroy(number());
>
> if((ret = rtf_create(number(), sz)) < 0) {
> ERROR("Error opening RTF%d\n", number());
> return -1;
> }
>
> if((ret = rtf_create_handler(number(), &rtfHandler)) < 0) {
> ERROR("Error installing handler on RTF%d\n", number());
> (void)rtf_destroy(number());
> return -1;
>
> }
>
> return 0;
> }
>
>
> void cleanup_module(void)
> {
> (void)rtf_destroy(number());
> }
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
> --
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
Re: [rtl] unresolved symbol
On Tue, Feb 20, 2001 at 01:36:43PM +0100, Bas Benschop wrote: > Today I tried to install rtlinux-3.0 on a Debian 2.2 system (kernel > 2.2.18) with 2 processors and SMP enabled. Builds without any problem but > when I try to insmod rtl.o I get the message: > > rtl.o: unresolved symbol rtlinux_suspend_linux_init > rtl.o: unresolved symbol rtlinux_suspend_linux_cleanup > > What can be wrong? Which compiler version are you using? the gcc272 package or the standard one that comes with Debian by default (2.95.2)? I haven't run into this myself, and I test and develop on Debian stable. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] root id
On Wed, Feb 21, 2001 at 05:56:40PM -0500, Frederic Cazenave wrote: > gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs > gcc version 2.96 2731 (Red Hat Linux 7.0) Erk . . . um, there have been known problems compiling the kernel with RedHat's "stable" distribution because they decided to put a cutting edge compiler in it. I don't know if that version of the compiler (2.96) miscompiles RTLinux, but I wouldn't rule that out. Have you tried getting the updates for RedHat or using a different version of the compiler (2.7.2.x comes to mind right away)? -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] RTL + Low Latency patch interference?
On Tue, Jan 16, 2001 at 08:38:30AM -0700, [EMAIL PROTECTED] wrote: > You could have asked me: aside from getting wierd OS failures (which is > always fun) there is a really interesting area in which "soft" realtime > applications interact with hard realtime applications: e.g. hard RT > collects frames, feeds them to a soft RT which does some mixing, and hard > RT outputs. > I think that the area in which hard and soft RT cooperate is one of the most > important research&development areas in OS. I stand humbled. My apologies if I seemed overly negative towards the question of using the low latency patch. It's just that it seems like applications that require low latency could be deftly handled by using hard real time, and the low latency patch has a lot of provisos for its use. There was much discussion on the Linux kernel list about the issues that the low latency patch raised. While many people said that it Worked For Them(tm), it looked like the patch would not be compatible with many drivers and perhaps even platforms (did anyone ever test the patch on anything besides ia32?). However, if you get the low latency patch and our RTLinux patch to apply cleanly and work, all the more power to you. I'd be interested to hear how it works out. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] Double Serial
On Tue, Jan 16, 2001 at 08:56:15AM +0100, Carsten Fischer wrote: > I'm looking for a driver for a Dual RS-232 serial ports -card (using > PCMCIA) (SILICOM). Can you give any more details on this piece of hardware? Also, have you tried looking in the 2.4 kernel section that has PCMCIA serial drivers to see if this card is supported? > I have got a Toshiba Notebook with just one serial port, but I need two > I/O ports. > There are no problems by using rt_com-driver and ttyS0 . -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] RTL + Low Latency patch interference?
On Tue, Jan 16, 2001 at 10:26:36AM +0100, Bart Thissen wrote: > Does any body has experience with the low latency kernel patch and > RTL together? I did try this combination once, and found serious > problems under heavy load, maybe related to bad memory. Excuse me for asking, but *why* would you want to do this? If you have RTLinux you get hard real-time guarantees, which can be used in the same way low latency can. As I remember, the low latency patch just sprinkled schedule() randomly on the kernel source like magic faery dust. Shouldn't make a damn bit of difference to RTLinux, since it preempts the regular Linux kernel anytime it wants. Don't know if there are any adverse effects the other way around, since I haven't tried this, since I don't see the point. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] Update rtl2.2 to 3.0p10
Well, the first thing i can pick out that might be making this not
work is that you need to set the scheduling for the thread where you do the
wait. See below where i inserted code as to how i would do it.
On Tue, Jan 09, 2001 at 07:58:38PM +0100, Peter Helbig wrote:
> Hello Everybody!
>
> I updated from rtlV2.2 to V3.0p10 and found a different behaviour of
> pthread_make_periodic_np(...,...,0). In V2.2 it works as suspected: The
> thread is called once and is sentenced to wait with a
> pthread_wait_np() afterwards. In V3.0p10 the call of
> pthread_wait_np() blocks the thread forever.
>
> Code example:
>
> void *thread_code(void *param)
> {
>
struct sched_param my_sparam;
> // blabla
> --- snip ---
> do
> {
>min_diff = 20;
> max_diff = -20;
>
> for (i = 0; i < ntests; i++)
> {
> now = clock_gethrtime(rtl_getschedclock());
> if (advance && !mode)
> {
> if (now < expected)
> {
> rtl_delay (expected - now);
> }
> now = clock_gethrtime(CLOCK_UST);
> }
>
> /* start of next time element */
> do_rayonic_start();
> do_rayonic(loops);
> do_rayonic_fini();
>
> /* finished user part of measurement */
> fini = clock_gethrtime(rtl_getschedclock());
> samp.fini = fini;
>
> /* calculate time for next activation */
> /* 1) difference from expectation */
> diff = now - expected;
> samp.diff = diff;
> if (diff < min_diff)
> {
> min_diff = diff;
> }
>
> if (diff > max_diff)
> {
> max_diff = diff;
> }
>
> /* 2) theoretical sleeping duration */
> sleepfor = CYCLETIME-(fini-now);
> samp.sleepfor = sleepfor;
>
> /* 3) adaptive control towards expected time */
> sleepfor -= diff;
>
> /* 4) avoid processor overload */
> expected += CYCLETIME;
> while (sleepfor < MAXLOAD)
> {
> sleepfor += CYCLETIME;
> expected += CYCLETIME;
> samp.skipped ++;
> }
>
> /* 5) absolute time for reactivation */
> sleepto = (now+sleepfor);
> samp.sleepto = sleepto;
>
my_sparam.sched_priority = 1;
if (
(retval =
pthread_setschedparam(pthread_self(), SCHED_FIFO,
&my_sparam)) != 0) {
return (void *) retval;
}
> pthread_make_periodic_np
> (pthread_self(),sleepto,0);
> //
> // In V3.0p10 the next call blocks the thread
> forever,
> // in V2.2 it works properly
> //
> pthread_wait_np();
> }
>
> samp.min = min_diff;
> samp.max = max_diff;
> write (fifo_monitor, &samp, sizeof(samp));
>
> } while (1);// endless...
>
> - snap
> ---
> } // thread end
>
>
> Any hints will be welcome!
>
>
> Peter
>
>
> Peter Helbig
> Rayonic Sensor Systems GmbH
> Entwicklung Software
> Bayreuther Strasse 108
> D-91301 Forchheim
>
> Tel: ++49 (0) 9191 72 818-0
> Fax: ++49 (0) 9191 640 333
> Email: [EMAIL PROTECTED]
> http://www.rayonic.de
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
>
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
Re: [rtl] RTL Debugger
On Thu, Jan 04, 2001 at 06:51:23PM +0200, Felix Radensky wrote: > Hi, > > Can I user RTL debugger to debug non-rtl kernel modules (e.g. NIC > driver) > or code compiled directly into the kernel (not module) ? If yes, some > basic > instructions will be very appreciated. > > Thanks in advance. No, but there are patches available to add kernel debugging support to the Linux kernel separate of RTLinux. Take a look around the web for "kdb", or "kgdb". i believe that SGI also has a project working on kdb somewhere, although i can't find where right now. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] unable to handle kernel paging request
On Tue, Dec 12, 2000 at 03:35:01PM +, Raul wrote: > Hi there > I get the following error on allocating a variable on > memory: > "unable to handle kernel paging request" That's typically a memory fault in kernel. How exactly are you allocating this variable? > I have to say that this variable is a structure which > in turn contains more structures, that is, a quite > large one. How large? And how exactly are you accessing it? > after this the module remains uninitialized and I > cannot remove it from kernel space. > Any idea why I get this error? If the memory fault is occurring in init_module(), init_module() will not exit and be stuck. Try loading debugger/rtl_debug.o before loading your module to catch the exception and see where it is happening. Also, you should be able to remove the module if you have rtl_debug.o loaded. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] A beginner
On Mon, Dec 11, 2000 at 02:09:46AM -0500, Stebbins wrote: > I read the report on the 2nd Real-Time Linux Workshop, > and saw that "Documentation is currently sparse. However, > Philip Daly of the National Optical Astronomy Observatories > has written a book on real-time Linux which will be > published soon by O'Reilly." > > Would anyone know when this book might be published? Or > could anyone point me to a place where I could find some > good starting documentation? Since I am new to rtlinux I > would like to find some good starting documentation. O'Reilly should have information available on their web site (http://www.ora.com/, i believe). -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] segmentation fault because of sin()
On Thu, Dec 07, 2000 at 02:51:44PM -0500, Mohsen Mahvash Mohammadi wrote: > I have found that using sin() and cos() in real time task has caused > segmentation fault for user program.here is part of my program which > causes the problem: Couple of things to check: 1) Make sure floating point support is turned on when you configure RTLinux. 2) Make sure you enable floating point support for the thread you will be doing floating point in by calling pthread_setfp_np(pthread_self(), 1) before you do anything else in that thread (even initialization of floating point variables). -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] booting the kernel
On Thu, Dec 07, 2000 at 01:25:21PM -0600, Troy Davis wrote: > Hello- > I have recently started trying to run rtlinux on its own. What I've done > is created /dev/hdb1 on a new hard drive. Then I copy the rtlinux gzipped > file over to hdb1 (by mounting it under /newdrive) and unzip it. Then I do > the same with lilo. I compile the rtlinux kernel, and lilo. I then modify > lilo.conf so that it will treat hdb1 as though it was hda1 and run lilo. I > boot the kernel. It seems to boot but then gives Kernel Panic: Unable to > find init. What is init? Do I need another package installed in addition > to the rtlinux kernel and lilo? Any clues to this would be very helpful! Traditionally, init is the program that starts all other programs. It's the first userland program the kernel runs. In your case it sounds like you might want to make a script to load your RTLinux modules and tell the kernel to run that as init. Note that you will need an interpreter for the script (ie /bin/bash), the script, your RTLinux program in the form of a module, insmod (which comes with modutils), supporting libraries (ie libc) unless you compile everything static, and lastly a place to put all this, ie a file system of some sort (maybe a RAMdisk?). You might just want to start with Nicholas McGuire's miniRTL and go from there. -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] malloc and calloc
On Wed, Nov 29, 2000 at 12:55:04PM +, Raul wrote: > Can the functions malloc() and calloc() be used in > rtl. > I have this file that make calls upon those funcions. > The compilation presents no problems but when I try to > load the module the following error comes up: > unresolve symbol malloc > unresolve symbol calloc > > If they cannot be used is there anyother similar > function? In kernel, it's called kmalloc(), and there is a memset() as well. -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] The RTLinux Manifesto
On Fri, Nov 17, 2000 at 08:55:47AM +, Alan Cheasley wrote: > Please, has anybody heard of the "RT LInux Manifesto" ? > > If so how may I obtain a copy of it ? i'm not sure, but i think this may be it: http://www.fsmlabs.com/archive/rtlmanifesto.pdf -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] RTLinux + UMLinux ???
On Thu, Nov 02, 2000 at 03:56:01PM +0200, Denis Karpov wrote: > i have a question. since i'm new to RTLinux and kernel programming i > need some safe way to experiment with stuff. > is it possible to run RTLinux in User Mode Linux > [http://user-mode-linux.sourceforge.net/] > > that means one needs to apply UMLinux and RTLinux kernel patches > together > to 'straight' kernel source. is it going to work ? did any1 try it ? Don't know about UMLinux, but you might want to try user-level signals in RTLinux. The actual code still runs in kernel space, but you don't have to know nearly as much about kernel programming to use it. -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] RTL on a 486
On Wed, Nov 01, 2000 at 02:33:14PM +, Trevor Woolven wrote: > Hi Guys, > I posted this question last week and have been rather suprised by the > under-whelming response :-) > Do I take it that RTL doesn't run on a 486 anymore? > Answers on a postcard please... Sorry we haven't responded very quickly, been busy. RTL should run on 486, we even compile the kernel for 486, so i don't think it should be a problem. -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] problem with ethernet card.
On Mon, Oct 30, 2000 at 05:57:59PM +0530, Ramesh K wrote: > Hello, > I have installed RTlinux in my PC. My ethernet card doesn't > work now. But if I boot the machine with older kernel, the card works. > Immediately after this, if I boot with RT kernel, the card works, but if > booted after some time the network is inaccessible- may the settings are > lost during power down. > My card is an smc-ultra, with 8390 chip set. I compiled the RTKernel > with these options. In regular kernel (Linux 2.2.5), lsmod gives the > following > smc-ultra > 8390 > When booted with RT Kernel, these listings are not there. I tried to > follow Phil's Installation instructions, and added '/sbin/modprobe eth0' > in /etc/rc.d/rc.sysinit, but this reports eth0 not found, at boot. > I downloaded the smc-ultra and 8390 modules from rtlinux.org. When I > loaded this using insmod with arguments io=0x300 and irq=11 (similar to > my old settings), the card is now recognized as eth1, and still the > network is not accessible. Please give some suggestions. > > Thanks for your time and patience. Have you tried compiling the driver into the kernel? Or at the very least, make sure that the modules for the ethernet card get loaded before any RTLinux modules. -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
[rtl] Re: anyone else working on the alpha platform?
On Tue, Oct 24, 2000 at 12:07:59PM -0500, Terry L. Ridder wrote: > hello; > > been there, done that, does not work. > > rtlinux_kernel_2_3.tar.gz is linux-2.2.99-pre10-pre3 > which is not even linux-2.4.0-test1. > there are differences. Hmm, last time i checked, rtlinux_kernel_2_3.tar.gz is 2.4.0-test1, but i didn't put that package together. i'll look at it. > rtlinux_kernel_2_3.tar.gz has the same wrong > patches to the three config.in files. i have > written cort about that before. > make xconfig dies because of those wrong patches. Yes, make xconfig needs to be fixed. i'll see if i can get it fixed before we release pre9. > i am not the only one who has had problems with > those config.in files. > > rtlinux-3.0-pre8.alpha.rpm is not: > 1. a complete linux kernel source tree. Yes, it makes it considerably smaller and allows people to get RTLinux up and running quickly. It should have all header files necessary to compile an RTLinux program. If you want the complete kernel tree, just grab the pre-patched one (which should be fixed soon). > 2. wants to put the files in /usr/rtlinux >which is in my opinion non-standard. What standard? Where do you think it should be and why? > rtlinux-3.0-pre8.alpha.rpm is built using > linux-2.3.99-pre10-pre3. That's funny. i built that RPM, and i know i used 2.4.0-test1. > forgive me, but how can you say that you are sticking > with linux-2.4.0-test1 when nothing indicates that > you even using linux-2.4.0-test1? everything indicates > that you are using linux-2.3.99-pre10-pre3, which as > i stated above is not linux-2.4.0-test1, there are > differences. npsimons@hq:~$ cp ~ftp/pub/rtlinux/v3/rtlinux_kernel_2_3.tar.gz . npsimons@hq:~$ tar -xzf rtlinux_kernel_2_3.tar.gz npsimons@hq:~$ vim rtlinux_kernel_2_3/Makefile VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 0 EXTRAVERSION = -test1 > i do not know what alpha platform fsmlabs.com is developing > on, but i can tell you that on an alpha pc164 is does not > work. what version of gcc are you using to compile > rtlinux-3.0-pre8 on the alpha platform? gcc-2.95.2. Admittedly, we don't test RTLinux on a large number of Alphas, but we do compile kernels and modules with the "generic" machine type so that they should work everywhere. > i have been through rtlinux.org many times. > i have tried nearly everything before attempting > to make linux-2.4.0-test9 work with rtlinux-3.0-pre8.tar.gz > on my own. -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] init_module
On Tue, Oct 24, 2000 at 05:22:16PM +0900, Randolph Lee wrote: > Does rtl have an init_module system call? I noticed in the sample code that > init_module is usually void, but the linux init_module contains input > parameters. Also, is there another way to create threads without using the > init_module call? I am trying to create a function that will create threads > when called. Look at pthread_create(3). -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] anyone else working on the alpha platform?
Try grabbing the prepatched kernel off the ftp site (ftp://ftp.fsmlabs.com/pub/rtlinux/v3/rtlinux_kernel_2_3.tar.gz) or better yet, get the RPM with precompiled kernel and modules (ftp://ftp.fsmlabs.com/pub/rtlinux/v3/rtlinux-3.0-pre8.alpha.rpm). We are sticking with test1 for the 2.4.0 series of kernels because it is the most stable of the testX series (even though they are _supposed_ to be getting more stable with each new test release). On Tue, Oct 24, 2000 at 01:10:27AM -0500, [EMAIL PROTECTED] wrote: > hello; > > i was wondering if anyone else was working > on the alpha platform. > > i have an alpha pc164, 500mhz, etc. > i have redhat-6.2 for alpha installed. > i have downloaded the linux-2.4.0-test1 and > linux-2.4.0-test9 kernels from www.kernel.org. > i have downloaded rtlinux-3.0-pre8.tar.gz > from fsmlabs.com. > > i have patched rtlinux-3.0-pre8 files > rtlinux-3.0/drivers/mbuff/kvmem.h & > rtlinux-3.0/drivers/mbuff/kvmem.c > to work with linux-2.4.0-test9. > > i had to hand patch several of the > linux-2.4.0-test9 source files but > several of the patches were no longer > required. > > there are errors in the patches applied > by both kernel_patch-2.2 & kernel_patch-2.4. > the patched files: > arch/i386/config.in > arch/alpha/config.in > arch/ppc/config.in > > all have the same error. > > instead of a single equal sign '=' there > are two equal signs '=='. > > edit the config.in files and search for the > two equal signs and delete one of them. > > i have tested these patches and mbuff works > rather well. > > i am able to compile rtlinux-3.0-pre8 with > linux-2.4.0-test1 however whenever rtl.o > is insmod the alpha locks right up. > > i am able to compile rtlinux-3.0-pre8 with > linux-2.4.0-test4 however whenever rtl.o > is insmod the alpha locks right up. > > there are still several places in the examples > directory that have warnings about casting a > pointer to an integer of the wrong size. i still > need to look at those. but the examples do not > really matter if i cannot insmod the rtl.o > module without the alpha locking up. > > -- > Terry L. Ridder > Blue Danube Artistic Forge (Blaue Donau Kunstschmiede) > "We do not bend metal, we sculpture it." > > digging deep, i feel my conscience burn > i need to know who and what i am > this hunger jolts me from complacency > rocks me, makes me meet myself > kendall payne---closer to myself--- > > -- [rtl] --- > To unsubscribe: > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > echo "unsubscribe rtl " | mail [EMAIL PROTECTED] > --- > For more information on Real-Time Linux see: > http://www.rtlinux.org/rtlinux/ -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
[rtl] Re: no /lib/modules/2.2.14-RTL2.2/misc and no Symbol.map
On Thu, Oct 19, 2000 at 11:16:41AM -0400, Dingrong Yi wrote: > I only see for my case /lib/modules/2.2.14-RTL2.2/net is installed and no > /lib/modules/2.2.14-RTL2.2/misc. The misc directory is where the RTLinux modules go when you run 'make install' in the RTLinux directory. > Also, I have not a Symbol.map under my > /boot directory instead I have System.map there. Under my > rtlinux-2.2/linux no Symbol.map either, but System.map. System.map is always the standard name i have seen for that file. > Will these two differences cause any problem ? > > My SCSI card is adaptec AHA 2940 the driver is aic7xxx.0. I have the > driver for linux and rtLinux. Hence this is not the problem of my earlier > "unable to mount root file system.". Hmm, i use that driver for my Adaptec 39160. Are you sure it's the right one for your AHA 2940? -- Nathan Paul Simons, Junior Software Engineer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] about Create RT-FIFO
On Sun, Sep 17, 2000 at 09:01:08PM +0800, crzhang wrote: > Hi all, > I have install rtlinux2.2 with linux-2.2.14, but in the /dev I have only rtf0 ~ >rtf7, and how do I create the other RT-FIFOs. Try 'make devices' in the toplevel RTLinux directory, as root. i'm not sure if that rule was in the Makefile as early as 2.2, but it works for the current tree we are developing on. Just in case, here is what the rule does: echo echo -n "Testing for the mbuff device... " mkdir -p /dev if [ ! -e /dev/mbuff ]; then \ mknod /dev/mbuff c 10 254 && echo "mknod /dev/mbuff c 10 254"; \ else \ echo "already exists."; \ fi echo -n "Testing for FIFOs... " if [ ! -e /dev/rtf10 ]; then \ rm -f /dev/rtf*; \ for i in `seq 0 63`; do \ mknod /dev/rtf$i c 150 $i; \ done; \ echo "created /dev/rtf0 - 63 (major 150)"; \ else \ echo "already exist."; \ fi echo -- Nathan Paul Simons, Programmer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] Bootup Speeds...
On Thu, Sep 14, 2000 at 01:53:59PM -0600, Nathan Paul Simons wrote: > i usually make my kernels as modular as possible, and at one point in > time, it took roughly 45 seconds to go from LILO prompt to XDM login prompt. > This, of course, didn't count the time it took to load the RTL or SCSI modules > (for my CD-ROM drive). This is also on a PPro 180 with a slow IDE hard drive. Oh, and i forgot to mention this is a fully loaded devel system that loads up all the fairly standard services at bootup. -- Nathan Paul Simons, Programmer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] Bootup Speeds...
On Thu, Sep 14, 2000 at 05:09:24PM +0100, Derek Cassidy wrote: > Anyone know roughly what the bootup time for RTLinux is or other RTOS's > are. > > is there a list of boot up time comparisons anywhere on the web? > I am developing an embedded system but havent decided on which > RTOS to use and need to compare bootup times... > need a system that will startup quick.. For RTLinux, it shouldn't be (and in my experience isn't) too much different from the bootup time of unpatched Linux. The loading of the modules after bootup is really what takes a humanly noticeable amount of time. Really, it depends a lot on the hardware you use and drivers you select as modules. Making more drivers as modules (or leaving them out altogether) will result in faster bootup speeds, but then they will take noticeable time when you load them later. i usually make my kernels as modular as possible, and at one point in time, it took roughly 45 seconds to go from LILO prompt to XDM login prompt. This, of course, didn't count the time it took to load the RTL or SCSI modules (for my CD-ROM drive). This is also on a PPro 180 with a slow IDE hard drive. -- Nathan Paul Simons, Programmer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] Does RTLinux run on dual-Pentium ?
On Wed, Sep 06, 2000 at 06:16:12PM +0900, washi wrote: > Does someone know whether if RTLinux runs on dual-Pentium or not ? Yes. -- Nathan Paul Simons, Programmer for FSMLabs http://www.fsmlabs.com/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
