It's been awhile since I looked at this, but IIRC I had to insert
a 'release_region()' somewhere in init_module() in rt_com.c to get
past this problem.
Rich
> -----Original Message-----
> From: Michael C. Riedl [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 20, 2001 1:50 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [rtl] rt_com problem
>
>
> Hi there!
>
> I'm having a similar problem:
>
> First I made sure the Kernel (2.2.18) is compiled with serial.o as a
> module and not belonging to the kernel image.
> Next I checked serial.o is not loaded (lsmod).
> Then loading of rt_com.o works fine.
> But here's the problem:
> When I load testcom.o from the examples belonging to rt_com
> and it calls
> t_com_setup then the setup fails returning -EBUSY.
>
> I also tried "setserial /dev/ttyS0 uart none", but that didn't help
> either.
>
> Might there be a problem with modules being loaded automatically?
>
> What else could be wrong?
>
> Thank you very much for your hints to my first question, but
> unfortunately I couldn't fix my problem using them, so please help
> again.
>
> Michael C. Riedl
>
> -- [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/
>
-- [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/
