Thanks a lot.
That cleared up a lot of thinking. I have sended another mail this morning. Dont
reply it. I have undestood the message.
Anders Gnistrup
Jens Michaelsen wrote:
> [EMAIL PROTECTED] schrieb am 21.04.01:
> > if you do not need the standard serial port driver from linux kernel just
> > compile a new kernel witout serial.o.
> > I think that the problem is that that both driveres wont to reqeue the
> > addres 0x3F8 etc. (comport 0)
> >
> > A question for the serial driver. ->
> > what is the variable "loop" good for in isr_com() interrupt routine?
>
> If it still has the funtion I used it for, it should:
> - prevent lock up by exeting even when there are pending irqs.
> - improove cpu-time sharing with multiple serial ports by
> leaving the isr even with pending irqs.
> - reduce latency for our multiport serial-port machine control board.
> - allow better shared irq behavior with our hardware.
> - on the other hand it allows to make the driver a polling driver
> with known maximum process time.
> - ... its my way to design such tasks ...
>
> oops, guess the shared irq scheduler never made it into
> the open source ...
>
> Jens Michaelsen
>
> >
> > Anders Gnistrup
> >
> > Theo ten Brummelaar wrote:
> >
> > > Gentlepersons,
> > >
> > > As part of our development of an RT driver for the Cyclades-Y
> > > multi-serial port card I have finally upgraded to RTL3.0, and after a
> > > bit of trouble have recompiled my code, for one of our CPUs anyway, and
> > > it all seems to work. I am using the API V1 still but will one day
> > > upgrade in my copious free time.
> > >
> > > Some of our CPUs use the rt_com module and that also seems to be OK
> > > except for one thing. You need to do the following to load the rt_com
> > > module:
> > >
> > > setserial /dev/ttyS0 uart none
> > > insmod rt_com
> > >
> > > Now, I want these machines to boot up and load whatever they need to
> > > make them run, including all the RT modules. With the older version of
> > > rt_com I could put
> > >
> > > insmod rt_com
> > >
> > > into the rc.local file. This no longer works, mostly I think due to the
> > > setserial stuff. If I put both the setserial command and the insmod
> > > rt_com command into rc.local it doesn't work.
> > >
> > > Any suggestions?
> > >
> > > Theo
> > > --
> > > Dr. Theo ten Brummelaar
> > > The CHARA Array-Georgia State University-Mount Wilson Observatory
> > > http://www.chara.gsu.edu/~theo Ph: 626-796-5405 Fax: 626-796-6717
> > > -- [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/
> >
> > -- [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/
> >
>
> ______________________________________________________________________________
> Die Fachpresse ist sich einig: WEB.DE 20mal Testsieger! Kostenlos E-Mail,
> Fax, SMS, Verschlusselung, POP3, WAP....testen Sie uns! http://freemail.web.de
> -- [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/
-- [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/
