On 12/05/2012 02:36 PM, Michael Morscher wrote:
> Hi Jan,
>
> My stupid comments will never end :)
>
> So, since using the 3.5.3 ipipe kernel for powerpc from DENX, I'm getting the
> following error during the first rtnet startup phase:
>
> *** RTnet 0.9.13 - built on Nov 29 2012 23:23:23 ***
>
On 2012-12-05 14:36, Michael Morscher wrote:
> Hi Jan,
>
> My stupid comments will never end :)
>
> So, since using the 3.5.3 ipipe kernel for powerpc from DENX, I'm getting the
> following error during the first rtnet startup phase:
>
> *** RTnet 0.9.13 - built on Nov 29 2012 23:23:23 ***
>
>
Hi Jan,
My stupid comments will never end :)
So, since using the 3.5.3 ipipe kernel for powerpc from DENX, I'm getting the
following error during the first rtnet startup phase:
*** RTnet 0.9.13 - built on Nov 29 2012 23:23:23 ***
RTnet: initialising real-time networking
rt_e1000e: Intel(R) PRO
Hi Jan,
I ran into another or the same problem again. I switched platform to two
Freescale P2020RDB and two Intel e1000e PCI-Express Adapters (Desktop CT). I
think the TDMA problem occurs because the buffer of the card explodes. Il
receive those messages when I connect both systems with a 1:1
On 2012-12-03 17:18, Michael Morscher wrote:
> Hi Jan,
>
> I ran into another or the same problem again. I switched platform to two
> Freescale P2020RDB and two Intel e1000e PCI-Express Adapters (Desktop CT). I
> think the TDMA problem occurs because the buffer of the card explodes. Il
> recei
Hi Jan,
When doing a correct start i get:
root@nfs1-webcam:~# /usr/local/rtnet/sbin/rtnet stop
RTmac/TDMA: unloaded
RTmac: unloaded
RTcfg: unloaded
removing loopback...
RTnet: unregistered rtlo
RTnet: unregistered rteth0
RTnet: unloaded
root@nfs1-webcam:~# /usr/local/rtnet/sbin/rtnet start
*** R
On 2012-10-26 17:01, Michael Morscher wrote:
> Hi,
>
> Am Freitag, 26. Oktober 2012 16:34 CEST, Jan Kiszka
> schrieb:
>> The purpose is to tell Linux to unbind the active driver (e1000) from
>> the card and bind the rt_e1000 instead. As long as there is only one
>> adapter of the same kind, it'
Hi,
Am Freitag, 26. Oktober 2012 16:34 CEST, Jan Kiszka
schrieb:
> The purpose is to tell Linux to unbind the active driver (e1000) from
> the card and bind the rt_e1000 instead. As long as there is only one
> adapter of the same kind, it's basically "rmmod e1000; modprobe
> rt_e1000" (and "rmm
On 2012-10-26 16:09, Michael Morscher wrote:
> Hi Jan,
>
> Thank for the answer.
>
> Am Freitag, 26. Oktober 2012 15:38 CEST, Jan Kiszka
> schrieb:
>
>> On 2012-10-25 10:58, Michael Morscher wrote:
>>> Hey guys,
>>>
>>> Just ran into some strange behaviour on my test rig. (2x MPC8313E-RDB
Hi Jan,
Thank for the answer.
Am Freitag, 26. Oktober 2012 15:38 CEST, Jan Kiszka
schrieb:
> On 2012-10-25 10:58, Michael Morscher wrote:
> > Hey guys,
> >
> > Just ran into some strange behaviour on my test rig. (2x MPC8313E-RDB +2x
> > Intel E1000 PCI)
> >
> > 1. After starting the ma
On 2012-10-25 10:58, Michael Morscher wrote:
> Hey guys,
>
> Just ran into some strange behaviour on my test rig. (2x MPC8313E-RDB +2x
> Intel E1000 PCI)
>
> 1. After starting the master server, I'm getting loads of those messages:
>>>>TDMA: Failed to transmit sync frame!
> instead of the no
Hey guys,
Just ran into some strange behaviour on my test rig. (2x MPC8313E-RDB +2x Intel
E1000 PCI)
1. After starting the master server, I'm getting loads of those messages:
>>>TDMA: Failed to transmit sync frame!
instead of the normal "waiting for slaves...". I need to start the slave first
12 matches
Mail list logo
