Sergey Didenko wrote:
Hello
This is a patch which includes the changes for xenomai-2.4.10 release,
required to support the ARM based targets controlled by plat-orion timer,
irq and gpio.
Ok. In __ipipe_mach_demux_irq, you must call ipipe_handle_irq, not
desc_handle_irq.
On one of our platforms (PPC 5200B Kernel 2.4, Xenomai 2.4.8, PCI-bus) we face
rare network stalls (once a day).
In this situation network communication seems to be completly dead, but
obviously only the receive direction is affected as receive-interrupts in
/proc/interrupts aren´t incremented
roderik.wildenb...@manroland.com wrote:
On one of our platforms (PPC 5200B Kernel 2.4, Xenomai 2.4.8,
PCI-bus) we face rare network stalls (once a day). In this situation
network communication seems to be completly dead, but obviously only
the receive direction is affected as
Gilles Chanteperdrix wrote:
roderik.wildenb...@manroland.com wrote:
On one of our platforms (PPC 5200B Kernel 2.4, Xenomai 2.4.8,
PCI-bus) we face rare network stalls (once a day). In this situation
network communication seems to be completly dead, but obviously only
the receive direction is
How do I get the wifistix to work on a kernel 2.6.24?
I maneged to compile wifistix-module but I get this error:
r...@gumstix-custom-verdex:/lib/modules/2.6.24/extra$ modprobe wlan0
FATAL: Error inserting cfio (/lib/modules/2.6.24/extra/cfio.ko): Unknown
symbol in module, or unknown parameter
Ups I didn't have pxa2xx and pxa2xx_cs module.
Now I have this error:
r...@gumstix-custom-verdex:~$ modprobe wlan0
Segmentation fault
r...@gumstix-custom-verdex:~$ dmesg
5pccard: card ejected from slot 0
4cfio: module license 'unspecified' taints kernel.
5pccard: PCMCIA card inserted into slot
Linus Casassa wrote:
Ups I didn't have pxa2xx and pxa2xx_cs module.
Now I have this error:
r...@gumstix-custom-verdex:~$ modprobe wlan0
Segmentation fault
Ok. I did not answer to your first mail because I thought your post to
the Xenomai mailing list was a mistake. But apparently it was
Are there any FEC related kernel messages? Maybe (likely) the
problem is
We will check this.
caused by Ethernet packet bombardments (I suspect bursts of ARP
request). You could try to simulate such bombardments by
using pktgen. I
can send you a script in case you are interested.
Sure
