rtnet-users — support, discussion, and announcement list

Re: [RTnet-users] RTNet compilation failed

[Mnatsakanyan, M. <m.m...@tu...>]

Hello,

Thank you for response.

My non-RT driver module is r8169 and I used rt_r8169 available in RTNet.
So I guess the problem is with NIC.

I would like to give a try to maintain the driver to support the NIC I have.

Could you guide me through what has to be done?

This is the controller I have:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)

Best regards,
Mari  
________________________________________
From: Mariusz Janiak [mar...@wp...]
Sent: Tuesday, May 06, 2014 6:43 PM
To: Mnatsakanyan, M.
Cc: rtn...@li...
Subject: RE: [RTnet-users] RTNet compilation failed

Hi,

I think, that you have chosen wrong driver or your NIC is not supported by selected rt driver. Unfortunately rt drivers haven't been updated recently, so there can be a problem with newer NICs.

Best regards,
Maruisz


Dnia Wtorek, 6 Maja 2014 16:23 Mnatsakanyan, M. <m.m...@tu...> napisał(a)
> Thank you, that solved the problem with compilation, but now I am having a different problem.
>
> Now I get errors on "rtnet start". Again, I follow the installation & test instructions.
>
> The errors are as follows:
>
> rteth0: ERROR while getting interface flags: No such device
> rteth0-mac: ERROR while getting interface flags: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl (add): No such device
> vnic0: ERROR while getting interface flags: No such device
> SIOCSIFADDR: No such device
> vnic0: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> Waiting for all slaves...ioctl: No such device
> ioctl: No such device
>
> Regards,
> Mari
> ________________________________________
> From: Mariusz Janiak [mar...@wp...]
> Sent: Tuesday, May 06, 2014 1:45 PM
> To: Mnatsakanyan, M.
> Cc: rtn...@li...
> Subject: Re: [RTnet-users] RTNet compilation failed
>
> Hi,
>
> Try RTnet git version, this issue has been resolved already. The problem is with __devinit and __devexit that are not supported by newer kernels. You can remove them by your own.
>
> Best regards,
> Mariusz
>
> Dnia Wtorek, 6 Maja 2014 13:29 Mnatsakanyan, M. <m.m...@tu...> napisał(a)
> > Hi,
> >
> >
> > I am having a problem with compilation.
> > I used instructions in the page http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing
> >
> >
> > Here are versions I use:
> >
> >
> > RTNet:                0.9.13
> > Xenomai:              2.6.3
> > Linux kernel: 3.8.13
> >
> > In config, I selected only Realtek 8169 (Gigabit) driver, which corresponds to my network card.
> >
> > I get the following errors:
> >
> >
> > /usr/src/rtnet/drivers/rt_r8169.c:218:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’
> >  static struct pci_device_id rtl8169_pci_tbl[] __devinitdata = {
> >                                                ^
> > /usr/src/rtnet/drivers/rt_r8169.c:656:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_board’
> >  static int __devinit rtl8169_init_board ( struct pci_dev *pdev, struct rtnet_device **dev_out, unsigned long *ioaddr_out)
> >                       ^
> > /usr/src/rtnet/drivers/rt_r8169.c:821:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_one’
> >  static int __devinit rtl8169_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
> >                       ^
> > /usr/src/rtnet/drivers/rt_r8169.c:1066:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_remove_one’
> >  static void __devexit rtl8169_remove_one (struct pci_dev *pdev)
> >                        ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2071:12: error: ‘rtl8169_pci_tbl’ undeclared here (not in a function)
> >   id_table: rtl8169_pci_tbl,
> >             ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2072:10: error: ‘rtl8169_init_one’ undeclared here (not in a function)
> >   probe:  rtl8169_init_one,
> >           ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2073:11: error: ‘rtl8169_remove_one’ undeclared here (not in a function)
> >   remove:  rtl8169_remove_one,
> >
> >
> > Regards,
> > Mari
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> > &#149; 3 signs your SCM is hindering your productivity
> > &#149; Requirements for releasing software faster
> > &#149; Expert tips and advice for migrating your SCM now
> > http://p.sf.net/sfu/perforce
> > _______________________________________________
> > RTnet-users mailing list
> > RTn...@li...
> > https://lists.sourceforge.net/lists/listinfo/rtnet-users

Re: [RTnet-users] RTNet compilation failed

[Mariusz J. <mar...@wp...>]

Hi,

I think, that you have chosen wrong driver or your NIC is not supported by selected rt driver. Unfortunately rt drivers haven't been updated recently, so there can be a problem with newer NICs. 

Best regards,
Maruisz


Dnia Wtorek, 6 Maja 2014 16:23 Mnatsakanyan, M. <m.m...@tu...> napisał(a) 
> Thank you, that solved the problem with compilation, but now I am having a different problem.
> 
> Now I get errors on "rtnet start". Again, I follow the installation & test instructions.
> 
> The errors are as follows:
> 
> rteth0: ERROR while getting interface flags: No such device
> rteth0-mac: ERROR while getting interface flags: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl: No such device
> ioctl (add): No such device
> vnic0: ERROR while getting interface flags: No such device
> SIOCSIFADDR: No such device
> vnic0: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> Waiting for all slaves...ioctl: No such device
> ioctl: No such device
> 
> Regards,
> Mari
> ________________________________________
> From: Mariusz Janiak [mar...@wp...]
> Sent: Tuesday, May 06, 2014 1:45 PM
> To: Mnatsakanyan, M.
> Cc: rtn...@li...
> Subject: Re: [RTnet-users] RTNet compilation failed
> 
> Hi,
> 
> Try RTnet git version, this issue has been resolved already. The problem is with __devinit and __devexit that are not supported by newer kernels. You can remove them by your own.
> 
> Best regards,
> Mariusz
> 
> Dnia Wtorek, 6 Maja 2014 13:29 Mnatsakanyan, M. <m.m...@tu...> napisał(a)
> > Hi,
> >
> >
> > I am having a problem with compilation.
> > I used instructions in the page http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing
> >
> >
> > Here are versions I use:
> >
> >
> > RTNet:                0.9.13
> > Xenomai:              2.6.3
> > Linux kernel: 3.8.13
> >
> > In config, I selected only Realtek 8169 (Gigabit) driver, which corresponds to my network card.
> >
> > I get the following errors:
> >
> >
> > /usr/src/rtnet/drivers/rt_r8169.c:218:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’
> >  static struct pci_device_id rtl8169_pci_tbl[] __devinitdata = {
> >                                                ^
> > /usr/src/rtnet/drivers/rt_r8169.c:656:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_board’
> >  static int __devinit rtl8169_init_board ( struct pci_dev *pdev, struct rtnet_device **dev_out, unsigned long *ioaddr_out)
> >                       ^
> > /usr/src/rtnet/drivers/rt_r8169.c:821:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_one’
> >  static int __devinit rtl8169_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
> >                       ^
> > /usr/src/rtnet/drivers/rt_r8169.c:1066:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_remove_one’
> >  static void __devexit rtl8169_remove_one (struct pci_dev *pdev)
> >                        ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2071:12: error: ‘rtl8169_pci_tbl’ undeclared here (not in a function)
> >   id_table: rtl8169_pci_tbl,
> >             ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2072:10: error: ‘rtl8169_init_one’ undeclared here (not in a function)
> >   probe:  rtl8169_init_one,
> >           ^
> > /usr/src/rtnet/drivers/rt_r8169.c:2073:11: error: ‘rtl8169_remove_one’ undeclared here (not in a function)
> >   remove:  rtl8169_remove_one,
> >
> >
> > Regards,
> > Mari
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> > &#149; 3 signs your SCM is hindering your productivity
> > &#149; Requirements for releasing software faster
> > &#149; Expert tips and advice for migrating your SCM now
> > http://p.sf.net/sfu/perforce
> > _______________________________________________
> > RTnet-users mailing list
> > RTn...@li...
> > https://lists.sourceforge.net/lists/listinfo/rtnet-users

Re: [RTnet-users] RTNet compilation failed

[Mnatsakanyan, M. <m.m...@tu...>]

Thank you, that solved the problem with compilation, but now I am having a different problem.

Now I get errors on "rtnet start". Again, I follow the installation & test instructions.

The errors are as follows:

rteth0: ERROR while getting interface flags: No such device
rteth0-mac: ERROR while getting interface flags: No such device
ioctl: No such device
ioctl: No such device
ioctl: No such device
ioctl: No such device
ioctl (add): No such device
vnic0: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
vnic0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
Waiting for all slaves...ioctl: No such device
ioctl: No such device

Regards,
Mari
________________________________________
From: Mariusz Janiak [mar...@wp...]
Sent: Tuesday, May 06, 2014 1:45 PM
To: Mnatsakanyan, M.
Cc: rtn...@li...
Subject: Re: [RTnet-users] RTNet compilation failed

Hi,

Try RTnet git version, this issue has been resolved already. The problem is with __devinit and __devexit that are not supported by newer kernels. You can remove them by your own.

Best regards,
Mariusz

Dnia Wtorek, 6 Maja 2014 13:29 Mnatsakanyan, M. <m.m...@tu...> napisał(a)
> Hi,
>
>
> I am having a problem with compilation.
> I used instructions in the page http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing
>
>
> Here are versions I use:
>
>
> RTNet:                0.9.13
> Xenomai:              2.6.3
> Linux kernel: 3.8.13
>
> In config, I selected only Realtek 8169 (Gigabit) driver, which corresponds to my network card.
>
> I get the following errors:
>
>
> /usr/src/rtnet/drivers/rt_r8169.c:218:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’
>  static struct pci_device_id rtl8169_pci_tbl[] __devinitdata = {
>                                                ^
> /usr/src/rtnet/drivers/rt_r8169.c:656:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_board’
>  static int __devinit rtl8169_init_board ( struct pci_dev *pdev, struct rtnet_device **dev_out, unsigned long *ioaddr_out)
>                       ^
> /usr/src/rtnet/drivers/rt_r8169.c:821:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_one’
>  static int __devinit rtl8169_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
>                       ^
> /usr/src/rtnet/drivers/rt_r8169.c:1066:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_remove_one’
>  static void __devexit rtl8169_remove_one (struct pci_dev *pdev)
>                        ^
> /usr/src/rtnet/drivers/rt_r8169.c:2071:12: error: ‘rtl8169_pci_tbl’ undeclared here (not in a function)
>   id_table: rtl8169_pci_tbl,
>             ^
> /usr/src/rtnet/drivers/rt_r8169.c:2072:10: error: ‘rtl8169_init_one’ undeclared here (not in a function)
>   probe:  rtl8169_init_one,
>           ^
> /usr/src/rtnet/drivers/rt_r8169.c:2073:11: error: ‘rtl8169_remove_one’ undeclared here (not in a function)
>   remove:  rtl8169_remove_one,
>
>
> Regards,
> Mari
>
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> RTnet-users mailing list
> RTn...@li...
> https://lists.sourceforge.net/lists/listinfo/rtnet-users

Re: [RTnet-users] RTNet compilation failed

[Mariusz J. <mar...@wp...>]

Hi,

Try RTnet git version, this issue has been resolved already. The problem is with __devinit and __devexit that are not supported by newer kernels. You can remove them by your own. 

Best regards,
Mariusz

Dnia Wtorek, 6 Maja 2014 13:29 Mnatsakanyan, M. <m.m...@tu...> napisał(a) 
> Hi,
> 
> 
> I am having a problem with compilation.
> I used instructions in the page http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing
> 
> 
> Here are versions I use:
> 
> 
> RTNet:		0.9.13
> Xenomai:		2.6.3
> Linux kernel:	3.8.13
> 
> In config, I selected only Realtek 8169 (Gigabit) driver, which corresponds to my network card. 
> 
> I get the following errors:
> 
> 
> /usr/src/rtnet/drivers/rt_r8169.c:218:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’
>  static struct pci_device_id rtl8169_pci_tbl[] __devinitdata = {
>                                                ^
> /usr/src/rtnet/drivers/rt_r8169.c:656:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_board’
>  static int __devinit rtl8169_init_board ( struct pci_dev *pdev, struct rtnet_device **dev_out, unsigned long *ioaddr_out)
>                       ^
> /usr/src/rtnet/drivers/rt_r8169.c:821:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_one’
>  static int __devinit rtl8169_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
>                       ^
> /usr/src/rtnet/drivers/rt_r8169.c:1066:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_remove_one’
>  static void __devexit rtl8169_remove_one (struct pci_dev *pdev)
>                        ^
> /usr/src/rtnet/drivers/rt_r8169.c:2071:12: error: ‘rtl8169_pci_tbl’ undeclared here (not in a function)
>   id_table: rtl8169_pci_tbl,
>             ^
> /usr/src/rtnet/drivers/rt_r8169.c:2072:10: error: ‘rtl8169_init_one’ undeclared here (not in a function)
>   probe:  rtl8169_init_one,
>           ^
> /usr/src/rtnet/drivers/rt_r8169.c:2073:11: error: ‘rtl8169_remove_one’ undeclared here (not in a function)
>   remove:  rtl8169_remove_one,
> 
> 
> Regards,
> Mari
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> RTnet-users mailing list
> RTn...@li...
> https://lists.sourceforge.net/lists/listinfo/rtnet-users

[RTnet-users] RTNet compilation failed

[Mnatsakanyan, M. <m.m...@tu...>]

Hi,


I am having a problem with compilation.
I used instructions in the page http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing


Here are versions I use:


RTNet:		0.9.13
Xenomai:		2.6.3
Linux kernel:	3.8.13

In config, I selected only Realtek 8169 (Gigabit) driver, which corresponds to my network card. 

I get the following errors:


/usr/src/rtnet/drivers/rt_r8169.c:218:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’
 static struct pci_device_id rtl8169_pci_tbl[] __devinitdata = {
                                               ^
/usr/src/rtnet/drivers/rt_r8169.c:656:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_board’
 static int __devinit rtl8169_init_board ( struct pci_dev *pdev, struct rtnet_device **dev_out, unsigned long *ioaddr_out)
                      ^
/usr/src/rtnet/drivers/rt_r8169.c:821:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_init_one’
 static int __devinit rtl8169_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
                      ^
/usr/src/rtnet/drivers/rt_r8169.c:1066:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8169_remove_one’
 static void __devexit rtl8169_remove_one (struct pci_dev *pdev)
                       ^
/usr/src/rtnet/drivers/rt_r8169.c:2071:12: error: ‘rtl8169_pci_tbl’ undeclared here (not in a function)
  id_table: rtl8169_pci_tbl,
            ^
/usr/src/rtnet/drivers/rt_r8169.c:2072:10: error: ‘rtl8169_init_one’ undeclared here (not in a function)
  probe:  rtl8169_init_one,
          ^
/usr/src/rtnet/drivers/rt_r8169.c:2073:11: error: ‘rtl8169_remove_one’ undeclared here (not in a function)
  remove:  rtl8169_remove_one,


Regards,
Mari

Re: [RTnet-users] rtnet TDMA + user space app

[Klemen D. <kle...@ya...>]

Hello everybody,

Now i noticed one thing - I configured the master and slave as described in my previous e-mail:

master# tdmacfg rteth0 master 1000000 
master# tdmacfg rteth0 slot 0 100000

slave# tdmacfg rteth0 slave
slave# tdmacfg
 rteth0 slot 0 500000

Then i tried to rtping the slave with master and monitor the trafic with wireshark. I can see that the master pings the slave 0.1 s after the sync_frame. The slave then replies, but not 0.5 s after the sync_frame (as i was expecting), but just right after the next sync frame.
If i try to rtping the master with slave, i can see that the slave again sends the ping request right after the sync_frame and the master replies 0.1 s after the sync frame. 


Any idea why is that, why the slave does not obeys its tdmacfg slot offset? BTW, on the other hand the slave sends its Synchronization_Request_Frame 0.5 second after the sync_frame as expected.

Best Regards
Klemen



On Sunday, April 20, 2014 5:59 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
I would like to test a simple example of user space app with rtnet tdma. I successfully tested the RTAI example of simpleserver and simpleclient and it works fine. Then i configured the two machines to run as tdma master and tdma slave:

master:
# tdmacfg rteth0 master 1000000 
# tdmacfg rteth0 slot 0 100000

slave:
tdmacfg rteth0 slave
tdmacfg
 rteth0 slot 1 500000

I noticed the master started to transmit the synchronization_frame and the slave started to transmit the calibration_request_frames, and the masted then replied to them with calibration_reply_frames. Everything worked fine.

The i ran the  simpleserver and simpleclient once again and hoped the example will run over the tdma, but it doesn’t. No data is transmitted over the net. Any idea why not - I thought the axample will work with tdma with no change. Can yomeone please give me an example of user space app that runs on rtnet tdma or give me a hint what am i doing wrong.

Best Regards
Klemen

[RTnet-users] rtnet TDMA + user space app

[Klemen D. <kle...@ya...>]

I would like to test a simple example of user space app with rtnet tdma. I successfully tested the RTAI example of simpleserver and simpleclient and it works fine. Then i configured the two machines to run as tdma master and tdma slave:

master:
# tdmacfg rteth0 master 1000000 
# tdmacfg rteth0 slot 0 100000

slave:
tdmacfg rteth0 slave
tdmacfg rteth0 slot 1 500000

I noticed the master started to transmit the synchronization_frame and the slave started to transmit the calibration_request_frames, and the masted then replied to them with calibration_reply_frames. Everything worked fine.

The i ran the  simpleserver and simpleclient once again and hoped the example will run over the tdma, but it doesn’t. No data is transmitted over the net. Any idea why not - I thought the axample will work with tdma with no change. Can yomeone please give me an example of user space app that runs on rtnet tdma or give me a hint what am i doing wrong.

Best Regards
Klemen

[RTnet-users] Problem with e1000e driver

[Wojciech D. <woj...@gm...>]

Dear all,

I am experiencing some problems using the rt_e1000e driver for RTnet.

What I am doing is pretty simple, however not everything is working as
it supposed to. After I start the rtnet service I'm keep getting such
communicates from syslog:

TDMA: Failed to transmit sync frame!

and occasionally:

rt_e1000e: Reset adapter

After quite long time (at least few minutes)
the driver manages to establish the connection
and then everything is working as it should.

As my set-up I'm using mother board with those ethernet devices:

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection
a 8-port switch
a dedicated device bases on a microcontroller running RTnet.

As I described before I was able to establish the transmission and
then everything is working as it should. The time needed for
establishing the connection is however unacceptable.

Also I have tried repeating the same scenario but this time
only using the switch and everything is as previous.
Moreover, I tested this on different machines and I'm experiencing
the same problem.

I've found this on mailing list:

https://www.mail-archive.com/rtn...@li.../msg01326.html 


encouraged I've tried it by editing rtnet script by adding a substantial 
delay
of few seconds after all the drivers were loaded. Unfortunately,
that didn't solved the problem.

Different approach was to try the patch for the newest version
for e1000e driver and this one also didn't solve the problem.

Best regards,

-- 
Wojciech Domski

Domski.pl

Wojciech.Domski.pl

Re: [RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Just one more thing i noticed and could also cause problems:


If Cycle_Number overflow number would be changed by the master, then this should be somehow reported to a slave, because during the Calibration Phase, the slave has to set/define the Reply_Cycle_Number in the Request_Calibration_Frame. The slave should not define the Reply_Cycle_Number which is higher than the Cycle_Number overflow number.

Regards
Klemen




On Friday, January 3, 2014 4:26 PM, Jan Kiszka <jan...@we...> wrote:
 
On 2014-01-03 16:10, Klemen Dovrtel wrote:
> Can you change the number used by the master to overflow the Cycle Number. The number 4.151.347.200 is very close to 2^32 (which is the maximum Cycle Number) and suits to all phasing/period defined by 4 bits (16 in decimal).

Then we also need to restrict period to <= 16, rejecting other values.
Some automatic calculation of the overflow number + a rejection of
configurations where this becomes >= 2^32 would be nicer.

Jan


> On Friday, January 3, 2014 12:22 PM, Jan Kiszka <jan...@we...> wrote:
>  
> On 2013-12-12 21:13, Klemen Dovrtel wrote:
> 
>> Hello everybody,
>>
>> I am studding rtnet documentation and i am not sure of Rtnet slave <phasing> and <period> setup. 
>>
>> How does the slave knows it is his turn to send data? I assume all the informations should be in the Synchronisation Frame ->  Cycle Number field which is incremented by one in every new cycle, and it is reset to zero on overflow. What i am not sure is when does it overflow? I would suspect that the overflow number is set in a way that the (overflow_number+1) can be divided by all period numbers in the tdma.conf file without a reminder. Otherwise the slave slots can not be evenly distributed. I could not find any information about this. 
>>
> 
> Good point! This is not taken into account by the implementation. So if
> the configuration contains non-power-of-two periods, it will face
> skipped slots on wrap-around of the 32-bit cycle counter.
> 
> Jan
> 

Re: [RTnet-users] stage 2 configuration

[Klemen D. <kle...@ya...>]

Yust one correction 


>One option is the use of  Acknowledge_Configuration frame and Acknowledge_Length filed, which is sent by slave after it process one >stage_2 configuration fragment. But this means that the stage2_file in length of 100 frames need 100 factorial (100*99*98*....*1) frames to >be sent by master, which is a huge number.

The stage2_file in length of 100 frames data transfer controlled by Acknowledge_Configuration frame would need 100+99+98+....+1 frames to be sent by master.

Regards
Klemen

[RTnet-users] stage 2 configuration

[Klemen D. <kle...@ya...>]

Hello everybody,

I am studying the rtcfg - stage2 configuration. When the stage2_file is larger than MTU (1500) the file is cat to fragments which are sent to slave one after another without any control of the file data transfer. I am having a problem with that because the my rtnet slave can not process the data so fast. This is why i am looking for some kind of flow control.

One option is the use of  Acknowledge_Configuration frame and Acknowledge_Length filed, which is sent by slave after it process one stage_2 configuration fragment. But this means that the stage2_file in length of 100 frames need 100 factorial (100*99*98*....*1) frames to be sent by master, which is a huge number.

That is why i would like to add/change this part in the rtcfg source so that it would enable fragment by fragment transmit of stage2 configuration file. What i am not sure is what part of the code cuts the stage2_file and transmit it. I went through the rtcfg.c and rtcfg_ioctl.c and i could not find where this happens.

Can someone please give me some hint what files should i check/change or point to workaround.

Best Regards
Klemen

[RTnet-users] RTnet + Xenomai

[Sylvain <syl...@mi...>]

Hello,

I am testing the example code using RTnet with Xenomai given on Xenomai
website : http://www.xenomai.org/index.php/RTnet:Programming Nevertheless, I
do not exacty know which librairies and options are to
be used with gcc . And I do not succeed in compiling it...

 Here is what the compiler says : gcc -I/usr/xenomai/include
 -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -lrtdm -L/usr/xenomai/lib
 -lxenomai -lpthread -lrt -L /usr/xenomai/lib -o main main.c -lrtdm
 -lxenomai /tmp/ccLHOd3t.o: In function `main':
     main.c:(.text+0x1fd): undefined reference to `rt_inet_aton'
     collect2: ld returned 1 exit status
     make: *** [main] Error 1


Any idea ?

Thanks a lot,
Best regards,
Sylvain

Re: [RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Let me answer to myself :)

If the client does not include the -f option in "rtcfg announce command", then the requests_available_stage_2_configuration_data_from_the_server flag in New_Announcement_Frame is cleared and the master does not transmit the stage2 configuration data.

Regards
Klemen





On Monday, February 10, 2014 1:45 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
Hello everybody,
I am still studying the rtcfg. I managed to send the rtcfg_stage1 frame, 
but i still can not send the  rtcfg_stage2 frame. The stage_2_burst_rate filed in stage1 frame is always set to 4 (which is a default value). 
After that, only one stage2 frame is sent by the server and the 
stage_2_config_length is set to zero. After that the client replies with acknowledge frame, nothing else happens. I tried different stage2_cfg files but the result is always the same. 

Any idea why is 
stage_2_burst_rate set to four and after that no data is sent - i would 
expect four frames. Is there a certain way how the 
stage2_cfg data should be written. Can someone please share a 
rtcfg_stage2 communication example/file.

rtnet server sommands i used:
$ sudo
 /usr/local/rtnet/sbin/rtcfg rteth0 server -h 0
$ sudo /usr/local/rtnet/sbin/rtcfg rteth0 add 142.168.0.5 -hw 00:01:02:03:04:05 -stage1 stage1_cfg -stage2 stage2_cfg

Best Regards
Klemen




On Sunday, February 9, 2014 9:47 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
Hello everybody,

I am still studying the rtcfg. I managed to send the rtcfg_stage1 frame, but i still can not send the  rtcfg_stage2 frame. The stage_2_burst_rate filed in stage1 frame is always set to 4 (which is a default value). After that, only one stage2 frame is sent by the server and the stage_2_config_length is set to zero. After that the client replies with Acknolwedge frame, nothing else happens (I attached the print screen of frames captured with wireshark). I tried different stage2_cfg files but the result is always the same. 
Any idea why is stage_2_burst_rate set to 4 and after that no data is sent i would expect for frames. That
 makes no sense. Is there a certain way how the stage2_cfg data should be written. Can someone please share a rtcfg_stage2 communication example/file.

rtnet server sommands:
$ sudo
 /usr/local/rtnet/sbin/rtcfg rteth0 server -h 0
$ sudo /usr/local/rtnet/sbin/rtcfg rteth0 add 142.168.0.5 -hw 00:01:02:03:04:05 -stage1 stage1_cfg -stage2 stage2_cfg

Best Regards
Klemen





On Wednesday, February 5, 2014 5:13 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
Hello everybody,
I will just continue
 this thread...

I noticed the Stage_1_configuration_frame data file has to end with EOL (x0A), otherwise the Configuration_length parameter is set to 0 and no Stage_1 configuration_data are sent. But when the data file ends with the EOL, the EOL character is also included in the configuration data. I am not sure what would happen if EOL character is also included in configuration data itself?

What i am also not sure is how should i write the Stage_2_configuration_frame data filewhen Stage_2_Burst_Rate is more than 1. How should i mark the data that are transfered with first frame, and the data that are sent with the second frame, etc. 
What is the delay between Stage_2_configuration_frames. I would like to make sure the rtnet client has enough time to process the data in one frame and than wait for new frame and process that one.

Is there a way to somehow cut this command:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>] [-stage2 <stage2_file>] [-t <timeout>]
and send stage1 frame first and after that stage2 frames by parts. I tried to send the stage1 frame only with:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>]
but the empty stage2
 frame is
 added automatically.

Any idea how to solve this,
Best Regards

Klemen





------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the
 Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
RTnet-users mailing list
RTn...@li...
https://lists.sourceforge.net/lists/listinfo/rtnet-users






------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk

_______________________________________________
RTnet-users mailing list
RTn...@li...
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Re: [RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Hello everybody,
I am still studying the rtcfg. I managed to send the rtcfg_stage1 frame, 
but i still can not send the  rtcfg_stage2 frame. The stage_2_burst_rate filed in stage1 frame is always set to 4 (which is a default value). 
After that, only one stage2 frame is sent by the server and the 
stage_2_config_length is set to zero. After that the client replies with acknowledge frame, nothing else happens. I tried different stage2_cfg files but the result is always the same. 

Any idea why is 
stage_2_burst_rate set to four and after that no data is sent - i would 
expect four frames. Is there a certain way how the 
stage2_cfg data should be written. Can someone please share a 
rtcfg_stage2 communication example/file.

rtnet server sommands i used:
$ sudo
 /usr/local/rtnet/sbin/rtcfg rteth0 server -h 0
$ sudo /usr/local/rtnet/sbin/rtcfg rteth0 add 142.168.0.5 -hw 00:01:02:03:04:05 -stage1 stage1_cfg -stage2 stage2_cfg

Best Regards
Klemen




On Sunday, February 9, 2014 9:47 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
Hello everybody,

I am still studying the rtcfg. I managed to send the rtcfg_stage1 frame, but i still can not send the  rtcfg_stage2 frame. The stage_2_burst_rate filed in stage1 frame is always set to 4 (which is a default value). After that, only one stage2 frame is sent by the server and the stage_2_config_length is set to zero. After that the client replies with Acknolwedge frame, nothing else happens (I attached the print screen of frames captured with wireshark). I tried different stage2_cfg files but the result is always the same. 
Any idea why is stage_2_burst_rate set to 4 and after that no data is sent i would expect for frames. That
 makes no sense. Is there a certain way how the stage2_cfg data should be written. Can someone please share a rtcfg_stage2 communication example/file.

rtnet server sommands:
$ sudo
 /usr/local/rtnet/sbin/rtcfg rteth0 server -h 0
$ sudo /usr/local/rtnet/sbin/rtcfg rteth0 add 142.168.0.5 -hw 00:01:02:03:04:05 -stage1 stage1_cfg -stage2 stage2_cfg

Best Regards
Klemen





On Wednesday, February 5, 2014 5:13 PM, Klemen Dovrtel <kle...@ya...> wrote:
 
Hello everybody,
I will just continue
 this thread...

I noticed the Stage_1_configuration_frame data file has to end with EOL (x0A), otherwise the Configuration_length parameter is set to 0 and no Stage_1 configuration_data are sent. But when the data file ends with the EOL, the EOL character is also included in the configuration data. I am not sure what would happen if EOL character is also included in configuration data itself?

What i am also not sure is how should i write the Stage_2_configuration_frame data filewhen Stage_2_Burst_Rate is more than 1. How should i mark the data that are transfered with first frame, and the data that are sent with the second frame, etc. 
What is the delay between Stage_2_configuration_frames. I would like to make sure the rtnet client has enough time to process the data in one frame and than wait for new frame and process that one.

Is there a way to somehow cut this command:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>] [-stage2 <stage2_file>] [-t <timeout>]
and send stage1 frame first and after that stage2 frames by parts. I tried to send the stage1 frame only with:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>]
but the empty stage2
 frame is
 added automatically.

Any idea how to solve this,
Best Regards

Klemen





------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the
 Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
RTnet-users mailing list
RTn...@li...
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Re: [RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Hello everybody,
I will just continue this thread...

I noticed the Stage_1_configuration_frame data file has to end with EOL (x0A), otherwise the Configuration_length parameter is set to 0 and no Stage_1 configuration_data are sent. But when the data file ends with the EOL, the EOL character is also included in the configuration data. I am not sure what would happen if EOL character is also included in configuration data itself?

What i am also not sure is how should i write the Stage_2_configuration_frame data filewhen Stage_2_Burst_Rate is more than 1. How should i mark the data that are transfered with first frame, and the data that are sent with the second frame, etc. 
What is the delay between Stage_2_configuration_frames. I would like to make sure the rtnet client has enough time to process the data in one frame and than wait for new frame and process that one.

Is there a way to somehow cut this command:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>] [-stage2 <stage2_file>] [-t <timeout>]
and send stage1 frame first and after that stage2 frames by parts. I tried to send the stage1 frame only with:
rtcfg <dev> add <address> [-hw <hw_address>] [-stage1 <stage1_file>]
but the empty stage2 frame is added automatically.

Any idea how to solve this,
Best Regards
Klemen

[RTnet-users] Updating Driver e1000e to support I218V

[Niklaus W. <sim...@ho...>]

Hello,

I'm trying to see if it is possible to update the e1000e driver to support
the latest chip of Intel, I218V. I found the patch to go from support of
I217V to I218V which are simple adds of identifiers.
(http://ubuntu.5.x6.nabble.com/3-5-yuz-extended-stable-Patch-quot-e1000e-add-device-IDs-for-i218-quot-has-been-added-to-staging-quee-td5002425.html)
But the support of the I217V implies the support of a new Platform
Controller Hub, the Lynx Point Low Power (PCH_LPTLP). I found the patch
which is not too big to implement
(http://article.gmane.org/gmane.linux.network/229772/match=i217) but the
base of this patch seems to be a bit newer that the base of the current
rt_e100e. Could you tell me the version of the e1000e driver you use in the
last git source code ?

Niklaus

[RTnet-users] Basic questionsa about RTNet , TCP and real time comunications

[Pablo I. B. <pi...@gm...>]

Hello. In the RTNet wiki I read:

*RTnet implements UDP/IP, TCP/IP (basic features), ICMP and ARP in a
deterministic way. It provides a POSIX socket API to real-time user space
processes and kernel modules.*

*To avoid unpredictable collisions and congestions on Ethernet, an
additional protocol layer called RTmac controls the media access. A
dedicated Ethernet segment is required to guarantee bounded transmission
delays, but RTnet also includes a mechanism to tunnel non real-time traffic
like TCP/IP over RTmac, thus allowing a "single-cable" solution for
connecting control systems.*

I am not understanding well both paragraphs. Here I show a naive user case:
Let a closed loop control task performed by two hard realtime processes
located in different machines (for instance using Xenomai and RTNet):

-  Can I communicate two real-time processes in different machines writing
a code based on the POSIX socket API?

- Can I consider hard real time the task performed by both processes
together?

- Or instead the only I can say is that each process is real time, but the
whole task is not hard real-time because TCP is not a hard real-time
protocol. Is this right?


Thanks in advance.
Regards.

Re: [RTnet-users] rtnet fundamentals

[Jan K. <jan...@we...>]

On 2014-01-03 16:10, Klemen Dovrtel wrote:
> Can you change the number used by the master to overflow the Cycle Number. The number 4.151.347.200 is very close to 2^32 (which is the maximum Cycle Number) and suits to all phasing/period defined by 4 bits (16 in decimal).

Then we also need to restrict period to <= 16, rejecting other values.
Some automatic calculation of the overflow number + a rejection of
configurations where this becomes >= 2^32 would be nicer.

Jan

> On Friday, January 3, 2014 12:22 PM, Jan Kiszka <jan...@we...> wrote:
>  
> On 2013-12-12 21:13, Klemen Dovrtel wrote:
> 
>> Hello everybody,
>>
>> I am studding rtnet documentation and i am not sure of Rtnet slave <phasing> and <period> setup. 
>>
>> How does the slave knows it is his turn to send data? I assume all the informations should be in the Synchronisation Frame ->  Cycle Number field which is incremented by one in every new cycle, and it is reset to zero on overflow. What i am not sure is when does it overflow? I would suspect that the overflow number is set in a way that the (overflow_number+1) can be divided by all period numbers in the tdma.conf file without a reminder. Otherwise the slave slots can not be evenly distributed. I could not find any information about this. 
>>
> 
> Good point! This is not taken into account by the implementation. So if
> the configuration contains non-power-of-two periods, it will face
> skipped slots on wrap-around of the 32-bit cycle counter.
> 
> Jan
> 

Re: [RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Can you change the number used by the master to overflow the Cycle Number. The number 4.151.347.200 is very close to 2^32 (which is the maximum Cycle Number) and suits to all phasing/period defined by 4 bits (16 in decimal).

Regards
Klemen




On Friday, January 3, 2014 12:22 PM, Jan Kiszka <jan...@we...> wrote:
 
On 2013-12-12 21:13, Klemen Dovrtel wrote:

> Hello everybody,
> 
> I am studding rtnet documentation and i am not sure of Rtnet slave <phasing> and <period> setup. 
> 
> How does the slave knows it is his turn to send data? I assume all the informations should be in the Synchronisation Frame ->  Cycle Number field which is incremented by one in every new cycle, and it is reset to zero on overflow. What i am not sure is when does it overflow? I would suspect that the overflow number is set in a way that the (overflow_number+1) can be divided by all period numbers in the tdma.conf file without a reminder. Otherwise the slave slots can not be evenly distributed. I could not find any information about this. 
> 

Good point! This is not taken into account by the implementation. So if
the configuration contains non-power-of-two periods, it will face
skipped slots on wrap-around of the 32-bit cycle counter.

Jan

Re: [RTnet-users] rtnet fundamentals

[Jan K. <jan...@we...>]

On 2013-12-12 21:13, Klemen Dovrtel wrote:
> Hello everybody,
> 
> I am studding rtnet documentation and i am not sure of Rtnet slave <phasing> and <period> setup. 
> 
> How does the slave knows it is his turn to send data? I assume all the informations should be in the Synchronisation Frame ->  Cycle Number field which is incremented by one in every new cycle, and it is reset to zero on overflow. What i am not sure is when does it overflow? I would suspect that the overflow number is set in a way that the (overflow_number+1) can be divided by all period numbers in the tdma.conf file without a reminder. Otherwise the slave slots can not be evenly distributed. I could not find any information about this. 
> 

Good point! This is not taken into account by the implementation. So if
the configuration contains non-power-of-two periods, it will face
skipped slots on wrap-around of the 32-bit cycle counter.

Jan

[RTnet-users] rtnet fundamentals

[Klemen D. <kle...@ya...>]

Hello everybody,

I am studding rtnet documentation and i am not sure of Rtnet slave <phasing> and <period> setup. 

How does the slave knows it is his turn to send data? I assume all the informations should be in the Synchronisation Frame ->  Cycle Number field which is incremented by one in every new cycle, and it is reset to zero on overflow. What i am not sure is when does it overflow? I would suspect that the overflow number is set in a way that the (overflow_number+1) can be divided by all period numbers in the tdma.conf file without a reminder. Otherwise the slave slots can not be evenly distributed. I could not find any information about this. 


Best Regards
Klemen

Re: [RTnet-users] Patch to solve __devinit problem

[Jan K. <jan...@we...>]

On 2013-12-03 09:45, Leopold Palomo-Avellaneda wrote:
> A Dimarts, 3 de desembre de 2013, Jan Kiszka va escriure:
>> On 2013-12-02 16:07, Leopold Palomo-Avellaneda wrote:
>>> A Diumenge, 1 de desembre de 2013, Jan Kiszka va escriure:
>>>> On 2013-11-19 11:07, Leopold Palomo-Avellaneda wrote:
>>>>> Hi,
>>>>>
>>>>> work done. Now it compiles. Still there's a driver that doesn't compile 
>>>>> (natsemi), but it's another problem:
>>>>>
>>>>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>>>> code/drivers/rt_natsemi.c:2018:6: error: conflicting types for 
>>> ‘set_bit_le’
>>>>> In file included from /usr/src/linux-headers-3.8.13-
>>>>> xenomai-2.6.3/arch/x86/include/asm/bitops.h:516:0,
>>>>>                  from include/linux/bitops.h:22,
>>>>>                  from include/linux/kernel.h:10,
>>>>>                  from include/linux/cache.h:4,
>>>>>                  from include/linux/time.h:4,
>>>>>                  from include/linux/stat.h:18,
>>>>>                  from include/linux/module.h:10,
>>>>>                  from 
>>>>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>>>> code/drivers/rt_natsemi.c:150:
>>>>> include/asm-generic/bitops/le.h:57:20: note: previous definition of 
>>>>> ‘set_bit_le’ was here
>>>>> make[4]: *** 
> [/home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>>>> code/drivers/rt_natsemi.o] Error 1
>>>>>
>>>>>
>>>>> Patch attached, please apply it.
>>>>
>>>> Thanks for the fixes, and sorry for my late reply. The patch looks good
>>>> except for some small formal issues:
>>>>
>>>> - The patch should be accommodated with a proper commit message:
>>>>
>>>> <subject line>
>>>>
>>>> <brief description (you can follow my argumentation for Xenomai here)>
>>>>
>>>> Signed-off-by: ...
>>>>
>>>> The latter is a formal statement that you are the copyright holder and
>>>> contribute it to this project under the corresponding license.
>>>>
>>>> - The .gitignore change is unrelated, requires a separate path
>>>>
>>>> I'm looking into the natsemi build issue.
>>>>
>>>
>>> It's ok now?
>>>
>>
>> Thanks, almost perfect. I've massaged it while applying.
>>
> :-D
> 
> I understand that it's not perfect, I should have sent you the patch and some 
> Mediterranean wine and iberic jam for after the massage ;-)

Haha, will remind you of this next time! ;)

Jan

Re: [RTnet-users] Patch to solve __devinit problem

[Leopold Palomo-A. <le...@al...>]

A Dimarts, 3 de desembre de 2013, Jan Kiszka va escriure:
> On 2013-12-02 16:07, Leopold Palomo-Avellaneda wrote:
> > A Diumenge, 1 de desembre de 2013, Jan Kiszka va escriure:
> >> On 2013-11-19 11:07, Leopold Palomo-Avellaneda wrote:
> >>> Hi,
> >>>
> >>> work done. Now it compiles. Still there's a driver that doesn't compile 
> >>> (natsemi), but it's another problem:
> >>>
> >>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
> >>> code/drivers/rt_natsemi.c:2018:6: error: conflicting types for 
> > ‘set_bit_le’
> >>> In file included from /usr/src/linux-headers-3.8.13-
> >>> xenomai-2.6.3/arch/x86/include/asm/bitops.h:516:0,
> >>>                  from include/linux/bitops.h:22,
> >>>                  from include/linux/kernel.h:10,
> >>>                  from include/linux/cache.h:4,
> >>>                  from include/linux/time.h:4,
> >>>                  from include/linux/stat.h:18,
> >>>                  from include/linux/module.h:10,
> >>>                  from 
> >>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
> >>> code/drivers/rt_natsemi.c:150:
> >>> include/asm-generic/bitops/le.h:57:20: note: previous definition of 
> >>> ‘set_bit_le’ was here
> >>> make[4]: *** 
[/home/users/leopold.palomo/robotica/projects/platform/rtnet-
> >>> code/drivers/rt_natsemi.o] Error 1
> >>>
> >>>
> >>> Patch attached, please apply it.
> >>
> >> Thanks for the fixes, and sorry for my late reply. The patch looks good
> >> except for some small formal issues:
> >>
> >> - The patch should be accommodated with a proper commit message:
> >>
> >> <subject line>
> >>
> >> <brief description (you can follow my argumentation for Xenomai here)>
> >>
> >> Signed-off-by: ...
> >>
> >> The latter is a formal statement that you are the copyright holder and
> >> contribute it to this project under the corresponding license.
> >>
> >> - The .gitignore change is unrelated, requires a separate path
> >>
> >> I'm looking into the natsemi build issue.
> >>
> > 
> > It's ok now?
> > 
> 
> Thanks, almost perfect. I've massaged it while applying.
> 
:-D

I understand that it's not perfect, I should have sent you the patch and some 
Mediterranean wine and iberic jam for after the massage ;-)


-- 
--
Linux User 152692
Catalonia

Re: [RTnet-users] Patch to solve __devinit problem

[Jan K. <jan...@we...>]

On 2013-12-02 16:07, Leopold Palomo-Avellaneda wrote:
> A Diumenge, 1 de desembre de 2013, Jan Kiszka va escriure:
>> On 2013-11-19 11:07, Leopold Palomo-Avellaneda wrote:
>>> Hi,
>>>
>>> work done. Now it compiles. Still there's a driver that doesn't compile 
>>> (natsemi), but it's another problem:
>>>
>>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>> code/drivers/rt_natsemi.c:2018:6: error: conflicting types for 
> ‘set_bit_le’
>>> In file included from /usr/src/linux-headers-3.8.13-
>>> xenomai-2.6.3/arch/x86/include/asm/bitops.h:516:0,
>>>                  from include/linux/bitops.h:22,
>>>                  from include/linux/kernel.h:10,
>>>                  from include/linux/cache.h:4,
>>>                  from include/linux/time.h:4,
>>>                  from include/linux/stat.h:18,
>>>                  from include/linux/module.h:10,
>>>                  from 
>>> /home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>> code/drivers/rt_natsemi.c:150:
>>> include/asm-generic/bitops/le.h:57:20: note: previous definition of 
>>> ‘set_bit_le’ was here
>>> make[4]: *** [/home/users/leopold.palomo/robotica/projects/platform/rtnet-
>>> code/drivers/rt_natsemi.o] Error 1
>>>
>>>
>>> Patch attached, please apply it.
>>
>> Thanks for the fixes, and sorry for my late reply. The patch looks good
>> except for some small formal issues:
>>
>> - The patch should be accommodated with a proper commit message:
>>
>> <subject line>
>>
>> <brief description (you can follow my argumentation for Xenomai here)>
>>
>> Signed-off-by: ...
>>
>> The latter is a formal statement that you are the copyright holder and
>> contribute it to this project under the corresponding license.
>>
>> - The .gitignore change is unrelated, requires a separate path
>>
>> I'm looking into the natsemi build issue.
>>
> 
> It's ok now?
> 

Thanks, almost perfect. I've massaged it while applying.

Jan

Re: [RTnet-users] Patch to solve __devinit problem

[Leopold Palomo-A. <le...@al...>]

A Diumenge, 1 de desembre de 2013, Jan Kiszka va escriure:
> On 2013-11-19 11:07, Leopold Palomo-Avellaneda wrote:
> > Hi,
> > 
> > work done. Now it compiles. Still there's a driver that doesn't compile 
> > (natsemi), but it's another problem:
> > 
> > /home/users/leopold.palomo/robotica/projects/platform/rtnet-
> > code/drivers/rt_natsemi.c:2018:6: error: conflicting types for 
‘set_bit_le’
> > In file included from /usr/src/linux-headers-3.8.13-
> > xenomai-2.6.3/arch/x86/include/asm/bitops.h:516:0,
> >                  from include/linux/bitops.h:22,
> >                  from include/linux/kernel.h:10,
> >                  from include/linux/cache.h:4,
> >                  from include/linux/time.h:4,
> >                  from include/linux/stat.h:18,
> >                  from include/linux/module.h:10,
> >                  from 
> > /home/users/leopold.palomo/robotica/projects/platform/rtnet-
> > code/drivers/rt_natsemi.c:150:
> > include/asm-generic/bitops/le.h:57:20: note: previous definition of 
> > ‘set_bit_le’ was here
> > make[4]: *** [/home/users/leopold.palomo/robotica/projects/platform/rtnet-
> > code/drivers/rt_natsemi.o] Error 1
> > 
> > 
> > Patch attached, please apply it.
> 
> Thanks for the fixes, and sorry for my late reply. The patch looks good
> except for some small formal issues:
> 
> - The patch should be accommodated with a proper commit message:
> 
> <subject line>
> 
> <brief description (you can follow my argumentation for Xenomai here)>
> 
> Signed-off-by: ...
> 
> The latter is a formal statement that you are the copyright holder and
> contribute it to this project under the corresponding license.
> 
> - The .gitignore change is unrelated, requires a separate path
> 
> I'm looking into the natsemi build issue.
> 

It's ok now?

Regards,

Leopold

-- 
--
Linux User 152692
Catalonia