[Xenomai-help] serial module problems

[Xenomai-help] serial module problems

[Bachman Kharazmi]

Hi
I'm a new xenomai user and would like to get the serial module working.

I've 'builtin' serial support in my kernel, and tried to add a new
modified kernel line according to the docs which looks like:

kernel          /boot/maikern2 8250.nr_uarts=0
xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro

But when I boot my dmesg sais:
Kernel command line: 8250.nr_uarts=0
xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
Unknown boot option `xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800': ignoring


the serial example gives:
sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
main : can't open rtser0 (write), No such device


I've tried to build the Serial support as a module instead, but it ends up in:
ERROR: "per_cpu__ipipe_percpu_daddr"
[drivers/xenomai/serial/xeno_16550A.ko] undefined!
when doing make bzImage modules.

Any help is welcome
/Bachman

Re: [Xenomai-help] serial module problems

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

Bachman Kharazmi wrote:
> Hi
> I'm a new xenomai user and would like to get the serial module working.
> 
> I've 'builtin' serial support in my kernel, and tried to add a new
> modified kernel line according to the docs which looks like:
> 
> kernel          /boot/maikern2 8250.nr_uarts=0
> xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> 
> But when I boot my dmesg sais:
> Kernel command line: 8250.nr_uarts=0
> xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> Unknown boot option `xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800': ignoring
> 

The Wiki didn't reflect the upcoming version in Xenomai 2.4 yet. I
updated it, please see http://www.xenomai.org/index.php/16550A (the
essence: "ioaddr" is now called "io" for consistency reasons).

> 
> the serial example gives:
> sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
> main : can't open rtser0 (write), No such device
> 
> 
> I've tried to build the Serial support as a module instead, but it ends up in:
> ERROR: "per_cpu__ipipe_percpu_daddr"
> [drivers/xenomai/serial/xeno_16550A.ko] undefined!
> when doing make bzImage modules.

What I-pipe patch are you using? I saw that Philippe uploaded new
revisions (see SVN) that may fix this issue. Please check independently
of the other issue so that we know if that problem was fixed.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] serial module problems

[Philippe Gerum]

On Sat, 2007-09-08 at 20:59 +0200, Bachman Kharazmi wrote:
> Hi
> I'm a new xenomai user and would like to get the serial module working.
> 

Which Xenomai version, which kernel release, which Adeos/I-pipe release?

> I've 'builtin' serial support in my kernel, and tried to add a new
> modified kernel line according to the docs which looks like:
> 

Make sure CONFIG_XENO_DRIVERS_16550A is enabled in your kernel
configuration, and vanilla serial support disabled.

> kernel          /boot/maikern2 8250.nr_uarts=0
> xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> 
> But when I boot my dmesg sais:
> Kernel command line: 8250.nr_uarts=0
> xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> Unknown boot option `xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800': ignoring
> 
> 
> the serial example gives:
> sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
> main : can't open rtser0 (write), No such device
> 
> 
> I've tried to build the Serial support as a module instead, but it ends up in:
> ERROR: "per_cpu__ipipe_percpu_daddr"
> [drivers/xenomai/serial/xeno_16550A.ko] undefined!
> when doing make bzImage modules.
> 

I guess you might be using the latest Xenomai trunk/ with the latest
Adeos/x86 patches from the 2.6.22/1.10 series then. Some new symbols
have not been exported as they should in the latest Adeos release. The
patch below fixes that.

index 4d5bf61..08f4c33 100644
--- a/kernel/ipipe/core.c
+++ b/kernel/ipipe/core.c
@@ -1577,6 +1577,7 @@ EXPORT_SYMBOL(ipipe_control_irq);
 EXPORT_SYMBOL(ipipe_suspend_domain);
 EXPORT_SYMBOL(ipipe_alloc_virq);
 EXPORT_PER_CPU_SYMBOL(ipipe_percpu_domain);
+EXPORT_PER_CPU_SYMBOL(ipipe_percpu_darray);
 EXPORT_SYMBOL(ipipe_root);
 EXPORT_SYMBOL(ipipe_stall_pipeline_from);
 EXPORT_SYMBOL(ipipe_test_and_stall_pipeline_from);
@@ -1597,6 +1598,7 @@ EXPORT_SYMBOL(__ipipe_lock_irq);
 EXPORT_SYMBOL(__ipipe_unlock_irq);
 #ifndef CONFIG_SMP
 EXPORT_SYMBOL(__ipipe_root_status);
+EXPORT_PER_CPU_SYMBOL(ipipe_percpu_daddr);
 #endif
 EXPORT_SYMBOL(ipipe_register_domain);
 EXPORT_SYMBOL(ipipe_unregister_domain);

This fix is now part of the next Adeos/x86 release:

http://download.gna.org/adeos/patches/v2.6/i386/adeos-ipipe-2.6.22-i386-1.10-03.patch


> Any help is welcome
> /Bachman
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
-- 
Philippe.

Re: [Xenomai-help] serial module problems

[Bachman Kharazmi]

Hi, after doing some modifications as mentioned in your patch I did
compile serial as module without problems.

My problem is now that I don't have any /dev/rtserX devices :(
Do I need that?

My goal is to get serial communication working with xenomai for
controlling devices.

Linux default serial support ain't builtin to kernel anymore.
I'm running
Linux sandbox 2.6.22 #14 Sun Sep 9 15:01:50 CEST 2007 i686 GNU/Linux

I've checked out xenomai using svn according to:
svn co http://svn.gna.org/svn/xenomai/trunk xenomai
Adeos:
adeos-ipipe-2.6.22-i386-1.10-03.patch

sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# insmod
./xeno_16550A.ko io=0x3f8,0xbc00 irq=4,3 tx_fifo=10,20 start_index=0
sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# ls /dev/rtser*
ls: /dev/rtser*: No such file or directory

But I do have:
sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# find /proc/
| grep rtser
/proc/xenomai/rtdm/rtser1
/proc/xenomai/rtdm/rtser1/information
/proc/xenomai/rtdm/rtser0
/proc/xenomai/rtdm/rtser0/information

There's a serial example coming with xenomai, I'm unsure about
exactlly what it's supposed to do, or how I should use it. Would be
glad if somebody could explain more about how to use the serial ports
with xenomai driver.

with a crossed cable between serialport1 at mobo and serialport1 at
sunix4066 8port controllercard I get:

sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
main : write-file opened
main : write-config written
main : read-file opened
main : read-config written
main : write-task created
main : read-task created
main : starting write-task
main : starting read-task
 Nr |   write->irq    |    irq->read    |   write->read   |
-----------------------------------------------------------
read_task: error on rt_dev_read, code Success
main : rtser1 (read) -> closed
read_task: exit

dmesg: http://pastebin.ca/688553
.config: http://pastebin.ca/688558


Any hints are welcome.
/Bachman


On 08/09/07, Philippe Gerum <rpm@xenomai.org> wrote:
> On Sat, 2007-09-08 at 20:59 +0200, Bachman Kharazmi wrote:
> > Hi
> > I'm a new xenomai user and would like to get the serial module working.
> >
>
> Which Xenomai version, which kernel release, which Adeos/I-pipe release?
>
> > I've 'builtin' serial support in my kernel, and tried to add a new
> > modified kernel line according to the docs which looks like:
> >
>
> Make sure CONFIG_XENO_DRIVERS_16550A is enabled in your kernel
> configuration, and vanilla serial support disabled.
>
> > kernel          /boot/maikern2 8250.nr_uarts=0
> > xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> > xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> >
> > But when I boot my dmesg sais:
> > Kernel command line: 8250.nr_uarts=0
> > xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800 xeno_16550A.irq=4,3,3,3
> > xeno_16550A.baud_base=115200,115200,115200,115200 root=/dev/hda3 ro
> > Unknown boot option `xeno_16550A.ioaddr=0x03f8,0xbc00,0xbc08,0xb800': ignoring
> >
> >
> > the serial example gives:
> > sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
> > main : can't open rtser0 (write), No such device
> >
> >
> > I've tried to build the Serial support as a module instead, but it ends up in:
> > ERROR: "per_cpu__ipipe_percpu_daddr"
> > [drivers/xenomai/serial/xeno_16550A.ko] undefined!
> > when doing make bzImage modules.
> >
>
> I guess you might be using the latest Xenomai trunk/ with the latest
> Adeos/x86 patches from the 2.6.22/1.10 series then. Some new symbols
> have not been exported as they should in the latest Adeos release. The
> patch below fixes that.
>
> index 4d5bf61..08f4c33 100644
> --- a/kernel/ipipe/core.c
> +++ b/kernel/ipipe/core.c
> @@ -1577,6 +1577,7 @@ EXPORT_SYMBOL(ipipe_control_irq);
>  EXPORT_SYMBOL(ipipe_suspend_domain);
>  EXPORT_SYMBOL(ipipe_alloc_virq);
>  EXPORT_PER_CPU_SYMBOL(ipipe_percpu_domain);
> +EXPORT_PER_CPU_SYMBOL(ipipe_percpu_darray);
>  EXPORT_SYMBOL(ipipe_root);
>  EXPORT_SYMBOL(ipipe_stall_pipeline_from);
>  EXPORT_SYMBOL(ipipe_test_and_stall_pipeline_from);
> @@ -1597,6 +1598,7 @@ EXPORT_SYMBOL(__ipipe_lock_irq);
>  EXPORT_SYMBOL(__ipipe_unlock_irq);
>  #ifndef CONFIG_SMP
>  EXPORT_SYMBOL(__ipipe_root_status);
> +EXPORT_PER_CPU_SYMBOL(ipipe_percpu_daddr);
>  #endif
>  EXPORT_SYMBOL(ipipe_register_domain);
>  EXPORT_SYMBOL(ipipe_unregister_domain);
>
> This fix is now part of the next Adeos/x86 release:
>
> http://download.gna.org/adeos/patches/v2.6/i386/adeos-ipipe-2.6.22-i386-1.10-03.patch
>
>
> > Any help is welcome
> > /Bachman
> >
> > _______________________________________________
> > Xenomai-help mailing list
> > Xenomai-help@domain.hid
> > https://mail.gna.org/listinfo/xenomai-help
> --
> Philippe.
>
>
>

Re: [Xenomai-help] serial module problems

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]

Bachman Kharazmi wrote:
> Hi, after doing some modifications as mentioned in your patch I did
> compile serial as module without problems.
> 
> My problem is now that I don't have any /dev/rtserX devices :(
> Do I need that?

Nope. RTDM devices don't show up as Linux devices.

> 
> My goal is to get serial communication working with xenomai for
> controlling devices.
> 
> Linux default serial support ain't builtin to kernel anymore.
> I'm running
> Linux sandbox 2.6.22 #14 Sun Sep 9 15:01:50 CEST 2007 i686 GNU/Linux
> 
> I've checked out xenomai using svn according to:
> svn co http://svn.gna.org/svn/xenomai/trunk xenomai
> Adeos:
> adeos-ipipe-2.6.22-i386-1.10-03.patch
> 
> sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# insmod
> ./xeno_16550A.ko io=0x3f8,0xbc00 irq=4,3 tx_fifo=10,20 start_index=0

I bet the IRQ of your external serial adapter is NOT 3. Please check the
hardware manual.

> sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# ls /dev/rtser*
> ls: /dev/rtser*: No such file or directory
> 
> But I do have:
> sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# find /proc/
> | grep rtser
> /proc/xenomai/rtdm/rtser1
> /proc/xenomai/rtdm/rtser1/information
> /proc/xenomai/rtdm/rtser0
> /proc/xenomai/rtdm/rtser0/information
> 
> There's a serial example coming with xenomai, I'm unsure about
> exactlly what it's supposed to do, or how I should use it. Would be
> glad if somebody could explain more about how to use the serial ports
> with xenomai driver.
> 
> with a crossed cable between serialport1 at mobo and serialport1 at
> sunix4066 8port controllercard I get:

Basically, you already got its usage. It is a local cross link test,
running between two serial ports on the same box, that are connected via
a null modem cable. If the test is successful, you will see some round
trip statistics (yeah, needs to be documented more explicitly...).

> 
> sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
> main : write-file opened
> main : write-config written
> main : read-file opened
> main : read-config written
> main : write-task created
> main : read-task created
> main : starting write-task
> main : starting read-task
>  Nr |   write->irq    |    irq->read    |   write->read   |
> -----------------------------------------------------------
> read_task: error on rt_dev_read, code Success
> main : rtser1 (read) -> closed
> read_task: exit

There is no output likely due to one adapter being unable to get any
IRQ. You can check the IRQ activity under /proc/xenomai/irq.

> 
> dmesg: http://pastebin.ca/688553
> .config: http://pastebin.ca/688558

Also note that Xenomai warns you about potential SMI-related latencies.
Please see the Xenomai TROUBLESHOOTING doc on this.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] serial module problems

[Bachman Kharazmi]

sandbox:~/golden_2.6# ls
Makefile  README  driver  snxdump  snxlink  snxmknod  snxterm
sandbox:~/golden_2.6# modprobe snx_golden
sandbox:~/golden_2.6# setserial -g /dev/ttySNX0
/dev/ttySNX0, UART: 16650, Port: 0xbc00, IRQ: 3
sandbox:~/golden_2.6# setserial -g /dev/ttySNX1
/dev/ttySNX1, UART: 16650, Port: 0xbc08, IRQ: 3
sandbox:~/golden_2.6# setserial -g /dev/ttySNX2
/dev/ttySNX2, UART: 16650, Port: 0xb800, IRQ: 3
sandbox:~/golden_2.6# setserial -g /dev/ttySNX3
/dev/ttySNX3, UART: 16650, Port: 0xb808, IRQ: 3
sandbox:~/golden_2.6# setserial -g /dev/ttySNX4
/dev/ttySNX4, UART: 16650, Port: 0xb400, IRQ: 3
etc..

It's a sunix 4066 8port pci serial controller.

The irq file shows:
sandbox:~/golden_2.6# cat /proc/xenomai/irq
IRQ         CPU0
  0:         221         [timer]
 34:       10767         [virtual]

If this is a irq releated problem, how can I solve it? :/

thanks
Bachman

On 09/09/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
> Bachman Kharazmi wrote:
> > Hi, after doing some modifications as mentioned in your patch I did
> > compile serial as module without problems.
> >
> > My problem is now that I don't have any /dev/rtserX devices :(
> > Do I need that?
>
> Nope. RTDM devices don't show up as Linux devices.
>
> >
> > My goal is to get serial communication working with xenomai for
> > controlling devices.
> >
> > Linux default serial support ain't builtin to kernel anymore.
> > I'm running
> > Linux sandbox 2.6.22 #14 Sun Sep 9 15:01:50 CEST 2007 i686 GNU/Linux
> >
> > I've checked out xenomai using svn according to:
> > svn co http://svn.gna.org/svn/xenomai/trunk xenomai
> > Adeos:
> > adeos-ipipe-2.6.22-i386-1.10-03.patch
> >
> > sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# insmod
> > ./xeno_16550A.ko io=0x3f8,0xbc00 irq=4,3 tx_fifo=10,20 start_index=0
>
> I bet the IRQ of your external serial adapter is NOT 3. Please check the
> hardware manual.
>
> > sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# ls /dev/rtser*
> > ls: /dev/rtser*: No such file or directory
> >
> > But I do have:
> > sandbox:/lib/modules/2.6.22/kernel/drivers/xenomai/serial# find /proc/
> > | grep rtser
> > /proc/xenomai/rtdm/rtser1
> > /proc/xenomai/rtdm/rtser1/information
> > /proc/xenomai/rtdm/rtser0
> > /proc/xenomai/rtdm/rtser0/information
> >
> > There's a serial example coming with xenomai, I'm unsure about
> > exactlly what it's supposed to do, or how I should use it. Would be
> > glad if somebody could explain more about how to use the serial ports
> > with xenomai driver.
> >
> > with a crossed cable between serialport1 at mobo and serialport1 at
> > sunix4066 8port controllercard I get:
>
> Basically, you already got its usage. It is a local cross link test,
> running between two serial ports on the same box, that are connected via
> a null modem cable. If the test is successful, you will see some round
> trip statistics (yeah, needs to be documented more explicitly...).
>
> >
> > sandbox:/usr/src/xenomai/examples/rtdm/profiles/serial# ./cross-link
> > main : write-file opened
> > main : write-config written
> > main : read-file opened
> > main : read-config written
> > main : write-task created
> > main : read-task created
> > main : starting write-task
> > main : starting read-task
> >  Nr |   write->irq    |    irq->read    |   write->read   |
> > -----------------------------------------------------------
> > read_task: error on rt_dev_read, code Success
> > main : rtser1 (read) -> closed
> > read_task: exit
>
> There is no output likely due to one adapter being unable to get any
> IRQ. You can check the IRQ activity under /proc/xenomai/irq.
>
> >
> > dmesg: http://pastebin.ca/688553
> > .config: http://pastebin.ca/688558
>
> Also note that Xenomai warns you about potential SMI-related latencies.
> Please see the Xenomai TROUBLESHOOTING doc on this.
>
> Jan
>
>
>

Re: [Xenomai-help] serial module problems

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Bachman Kharazmi wrote:
> sandbox:~/golden_2.6# ls
> Makefile  README  driver  snxdump  snxlink  snxmknod  snxterm
> sandbox:~/golden_2.6# modprobe snx_golden

See, you already need some out-of-tree driver to make this adapter work
with standard Linux - and you expect the driver that comes with Xenomai
to work with it out of the box?

The question is now *what* is special about this adapter and its driver.
Where do you have the code from? What's its license?

> sandbox:~/golden_2.6# setserial -g /dev/ttySNX0
> /dev/ttySNX0, UART: 16650, Port: 0xbc00, IRQ: 3
> sandbox:~/golden_2.6# setserial -g /dev/ttySNX1
> /dev/ttySNX1, UART: 16650, Port: 0xbc08, IRQ: 3
> sandbox:~/golden_2.6# setserial -g /dev/ttySNX2
> /dev/ttySNX2, UART: 16650, Port: 0xb800, IRQ: 3
> sandbox:~/golden_2.6# setserial -g /dev/ttySNX3
> /dev/ttySNX3, UART: 16650, Port: 0xb808, IRQ: 3
> sandbox:~/golden_2.6# setserial -g /dev/ttySNX4
> /dev/ttySNX4, UART: 16650, Port: 0xb400, IRQ: 3
> etc..
> 
> It's a sunix 4066 8port pci serial controller.
> 
> The irq file shows:
> sandbox:~/golden_2.6# cat /proc/xenomai/irq
> IRQ         CPU0
>   0:         221         [timer]
>  34:       10767         [virtual]
> 
> If this is a irq releated problem, how can I solve it? :/

IRQs only show up there when they are in use, and that is the case when
the port is opened (ie. the test program is running).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] serial module problems

[Bachman Kharazmi]

I'm trying to implement a rt java motioncontrol-platform releated to
smerobot.org
I need to control three drives(rs232) connected to brushless dc motors.

The current PC I'm working on has one builtin serial port, and I found
a SUNIX 8port controller. So that's the reason why I'm using the pci
controller.

Anyhow the drivers are fetched from:
http://sunix.com.tw/it/en/DRIVER.php?SID&classnumber=3&usid1=303&usid2=304&Psid=472

I counldn't find any license releated information :/
But source comes with the driver is copied temporarily here:
http://bachman.tor.lindesign.se/tmp/driver/

Are there any chance that modifications in the source will get it going?

Other suggestions about how to solve this are also welcome

thanks
Bachman
On 09/09/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
> Bachman Kharazmi wrote:
> > sandbox:~/golden_2.6# ls
> > Makefile  README  driver  snxdump  snxlink  snxmknod  snxterm
> > sandbox:~/golden_2.6# modprobe snx_golden
>
> See, you already need some out-of-tree driver to make this adapter work
> with standard Linux - and you expect the driver that comes with Xenomai
> to work with it out of the box?
>
> The question is now *what* is special about this adapter and its driver.
> Where do you have the code from? What's its license?
>
> > sandbox:~/golden_2.6# setserial -g /dev/ttySNX0
> > /dev/ttySNX0, UART: 16650, Port: 0xbc00, IRQ: 3
> > sandbox:~/golden_2.6# setserial -g /dev/ttySNX1
> > /dev/ttySNX1, UART: 16650, Port: 0xbc08, IRQ: 3
> > sandbox:~/golden_2.6# setserial -g /dev/ttySNX2
> > /dev/ttySNX2, UART: 16650, Port: 0xb800, IRQ: 3
> > sandbox:~/golden_2.6# setserial -g /dev/ttySNX3
> > /dev/ttySNX3, UART: 16650, Port: 0xb808, IRQ: 3
> > sandbox:~/golden_2.6# setserial -g /dev/ttySNX4
> > /dev/ttySNX4, UART: 16650, Port: 0xb400, IRQ: 3
> > etc..
> >
> > It's a sunix 4066 8port pci serial controller.
> >
> > The irq file shows:
> > sandbox:~/golden_2.6# cat /proc/xenomai/irq
> > IRQ         CPU0
> >   0:         221         [timer]
> >  34:       10767         [virtual]
> >
> > If this is a irq releated problem, how can I solve it? :/
>
> IRQs only show up there when they are in use, and that is the case when
> the port is opened (ie. the test program is running).
>
> Jan
>
>
>

Re: [Xenomai-help] serial module problems

[Bachman Kharazmi]

> I counldn't find any license releated information :/
> But source comes with the driver is copied temporarily here:
> http://bachman.tor.lindesign.se/tmp/driver/

Sorry, I did miss:
 * 	This program is free software; you can redistribute it and/or modify		
 * 	it under the terms of the GNU General Public License as published by		
 * 	the Free Software Foundation; either version 2 of the License, or		
 * 	(at your option) any later version.

/B  ;)

Re: [Xenomai-help] serial module problems

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Bachman Kharazmi wrote:
> I'm trying to implement a rt java motioncontrol-platform releated to
> smerobot.org
> I need to control three drives(rs232) connected to brushless dc motors.
> 
> The current PC I'm working on has one builtin serial port, and I found
> a SUNIX 8port controller. So that's the reason why I'm using the pci
> controller.
> 
> Anyhow the drivers are fetched from:
> http://sunix.com.tw/it/en/DRIVER.php?SID&classnumber=3&usid1=303&usid2=304&Psid=472
> 
> I counldn't find any license releated information :/
> But source comes with the driver is copied temporarily here:
> http://bachman.tor.lindesign.se/tmp/driver/
> 
> Are there any chance that modifications in the source will get it going?

Maybe we are just lacking some pci_enable_device() on the right pci_dev.
That would mean extending xeno_16550A to deal with PCI devices. Surely
feasible, but it takes time and hardware to test - I'm lacking both.

Are you willing to play a bit with it? Then, as a prototype, you could
pick up the lookup and enabling code from the snx driver and hack it
into xeno_16550A. If that works, we could discuss how to establish
something generic for PCI-based adapters.

Note that I haven't read through that driver in details. There is a
slight risk that some more bits are different. On the other hand, the
16650 UART that seems to be on that card is advertised as
16550-compatible, thus it /should/ work...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]