All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
       [not found] <mailman.439.1426601187.27969.xenomai@xenomai.org>
@ 2015-03-17 14:23 ` Narasimhaprasad Yedatore Achutha
  0 siblings, 0 replies; 7+ messages in thread
From: Narasimhaprasad Yedatore Achutha @ 2015-03-17 14:23 UTC (permalink / raw)
  To: 'xenomai-owner@xenomai.org'; +Cc: 'xenomai@xenomai.org'

Pls find my query below.

----- Original Message -----
From: xenomai-owner@xenomai.org [mailto:xenomai-owner@xenomai.org]
Sent: Tuesday, March 17, 2015 07:36 PM
To: Narasimhaprasad Yedatore Achutha
Subject: CAN tx successfullness at Xenomai RT SocketCAN

xenomai mailing list is reserved to subscribers.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
  2015-04-01 12:04       ` Narasimhaprasad Yedatore Achutha
@ 2015-04-01 12:37         ` Wolfgang Grandegger
  0 siblings, 0 replies; 7+ messages in thread
From: Wolfgang Grandegger @ 2015-04-01 12:37 UTC (permalink / raw)
  To: Narasimhaprasad Yedatore Achutha; +Cc: xenomai

On Wed, 1 Apr 2015 12:04:16 +0000, Narasimhaprasad Yedatore Achutha
<Narasimhaprasad_A@infosys.com> wrote:
> Actually it will be definitely helpful if we can recognize through
> MSG_CONFIRM flag with CAN_RAW_RECV_OWN_MSGS options.
> Even with  loopback option  we can receive our own messages, but needs
> additional task time to separate it from external messages and its own
> transmitted messages as there will be mix of both,  additionally with
lot
> of backtracking. Here we just want to confirm whether the tx messages
has
> gone out successfully.

OK, I see.
 
> Incidentally socketcan also has a patch(refer net\can\raw.c   @
raw_rcv() )
> http://patchwork.ozlabs.org/patch/67893/
> 
> So a patch on this line,  will enable us to handle this in a better way.
> Please let me know the feasibility.

Yes, this approach is also feasible with RTCAN. Should not be a big deal
to implement it.

Wolfgang.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
  2015-04-01 11:06     ` Wolfgang Grandegger
@ 2015-04-01 12:04       ` Narasimhaprasad Yedatore Achutha
  2015-04-01 12:37         ` Wolfgang Grandegger
  0 siblings, 1 reply; 7+ messages in thread
From: Narasimhaprasad Yedatore Achutha @ 2015-04-01 12:04 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: xenomai

Actually it will be definitely helpful if we can recognize through MSG_CONFIRM flag with CAN_RAW_RECV_OWN_MSGS options.
Even with  loopback option  we can receive our own messages, but needs additional task time to separate it from external messages and its own transmitted messages as there will be mix of both,  additionally with lot of backtracking. Here we just want to confirm whether the tx messages has gone out successfully.

Incidentally socketcan also has a patch(refer net\can\raw.c   @ raw_rcv() )
http://patchwork.ozlabs.org/patch/67893/

So a patch on this line,  will enable us to handle this in a better way. Please let me know the feasibility.

Thanks and Regards
Prasad


-----Original Message-----
From: Wolfgang Grandegger [mailto:wg@grandegger.com] 
Sent: Wednesday, April 01, 2015 4:37 PM
To: Narasimhaprasad Yedatore Achutha
Cc: gilles.chanteperdrix@xenomai.org; xenomai@xenomai.org
Subject: Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
Importance: High

On Wed, 1 Apr 2015 10:19:31 +0000, Narasimhaprasad Yedatore Achutha <Narasimhaprasad_A@infosys.com> wrote:
> Hi All
> Could anybody share details on this query?

See below.

> 
> Thanks and Regards
> Prasad
> 
> -----Original Message-----
> From: Narasimhaprasad Yedatore Achutha
> Sent: Wednesday, March 18, 2015 1:57 PM
> To: 'gilles.chanteperdrix@xenomai.org'; 'xenomai-owner@xenomai.org'; 
> 'xenomai@xenomai.org'
> Subject: Re: CAN tx successfullness at Xenomai RT SocketCAN
> 
> Hello All
> I'm using RTSocket CAN in my application. Trying figure out how to
ensure
> the CAN message tranmission succesfulness in my function Previuosly I
was
> able to assess the echoed (recv own msg) message with MSG_CONFIRM flag 
> returned by recvmsg() while using just socket CAN functionalities.
> However with RT SOcket CAN, the CAN_RAW_RECV_OWN_MSGS is not supported
at
> rt_dev_setsockopt, and because of this the MSG_CONFIRM isnot being set
at
> msg flags in the received messages.
> Could please elaborate how do we make sure the tx message 
> successfulness are assesed at RT socket CAN.

As a workaround you could open another socket to receive the looped back message. Also implementing CAN_RAW_RECV_OWN_MSGS should not be a big deal.
The delivery skipping the own socket is done here:

http://git.xenomai.org/xenomai-2.6.git/tree/ksrc/drivers/can/rtcan_raw.c#n194

Wolfgang.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
  2015-04-01 10:19   ` Narasimhaprasad Yedatore Achutha
@ 2015-04-01 11:06     ` Wolfgang Grandegger
  2015-04-01 12:04       ` Narasimhaprasad Yedatore Achutha
  0 siblings, 1 reply; 7+ messages in thread
From: Wolfgang Grandegger @ 2015-04-01 11:06 UTC (permalink / raw)
  To: Narasimhaprasad Yedatore Achutha; +Cc: xenomai

On Wed, 1 Apr 2015 10:19:31 +0000, Narasimhaprasad Yedatore Achutha
<Narasimhaprasad_A@infosys.com> wrote:
> Hi All
> Could anybody share details on this query?

See below.

> 
> Thanks and Regards
> Prasad
> 
> -----Original Message-----
> From: Narasimhaprasad Yedatore Achutha 
> Sent: Wednesday, March 18, 2015 1:57 PM
> To: 'gilles.chanteperdrix@xenomai.org'; 'xenomai-owner@xenomai.org';
> 'xenomai@xenomai.org'
> Subject: Re: CAN tx successfullness at Xenomai RT SocketCAN
> 
> Hello All
> I'm using RTSocket CAN in my application. Trying figure out how to
ensure
> the CAN message tranmission succesfulness in my function Previuosly I
was
> able to assess the echoed (recv own msg) message with MSG_CONFIRM flag
> returned by recvmsg() while using just socket CAN functionalities.
> However with RT SOcket CAN, the CAN_RAW_RECV_OWN_MSGS is not supported
at
> rt_dev_setsockopt, and because of this the MSG_CONFIRM isnot being set
at
> msg flags in the received messages.
> Could please elaborate how do we make sure the tx message successfulness
> are assesed at RT socket CAN.

As a workaround you could open another socket to receive the looped back
message. Also implementing CAN_RAW_RECV_OWN_MSGS should not be a big deal.
The delivery skipping the own socket is done here:

http://git.xenomai.org/xenomai-2.6.git/tree/ksrc/drivers/can/rtcan_raw.c#n194

Wolfgang.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
  2015-03-18  8:27 ` Narasimhaprasad Yedatore Achutha
  2015-03-18  8:42   ` Gilles Chanteperdrix
@ 2015-04-01 10:19   ` Narasimhaprasad Yedatore Achutha
  2015-04-01 11:06     ` Wolfgang Grandegger
  1 sibling, 1 reply; 7+ messages in thread
From: Narasimhaprasad Yedatore Achutha @ 2015-04-01 10:19 UTC (permalink / raw)
  To: 'gilles.chanteperdrix@xenomai.org',
	'xenomai@xenomai.org'

Hi All
Could anybody share details on this query?

Thanks and Regards
Prasad

-----Original Message-----
From: Narasimhaprasad Yedatore Achutha
Sent: Wednesday, March 18, 2015 1:57 PM
To: 'gilles.chanteperdrix@xenomai.org'; 'xenomai-owner@xenomai.org'; 'xenomai@xenomai.org'
Subject: Re: CAN tx successfullness at Xenomai RT SocketCAN

Hello All
I'm using RTSocket CAN in my application. Trying figure out how to ensure the CAN message tranmission succesfulness in my function Previuosly I was able to assess the echoed (recv own msg) message with MSG_CONFIRM flag returned by recvmsg() while using just socket CAN functionalities.
However with RT SOcket CAN, the CAN_RAW_RECV_OWN_MSGS is not supported at rt_dev_setsockopt, and because of this the MSG_CONFIRM isnot being set at msg flags in the received messages.
Could please elaborate how do we make sure the tx message successfulness are assesed at RT socket CAN.
Thanks
YA

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
  2015-03-18  8:27 ` Narasimhaprasad Yedatore Achutha
@ 2015-03-18  8:42   ` Gilles Chanteperdrix
  2015-04-01 10:19   ` Narasimhaprasad Yedatore Achutha
  1 sibling, 0 replies; 7+ messages in thread
From: Gilles Chanteperdrix @ 2015-03-18  8:42 UTC (permalink / raw)
  To: Narasimhaprasad Yedatore Achutha
  Cc: 'xenomai-owner@xenomai.org', 'xenomai@xenomai.org'

On Wed, Mar 18, 2015 at 08:27:06AM +0000, Narasimhaprasad Yedatore Achutha wrote:
> Hello All
> I'm using RTSocket CAN in my application. Trying figure out how to ensure the CAN message tranmission succesfulness in my function
> Previuosly I was able to assess the echoed (recv own msg) message with MSG_CONFIRM flag returned by recvmsg() while using just socket CAN functionalities.
> However with RT SOcket CAN, the CAN_RAW_RECV_OWN_MSGS is not supported at rt_dev_setsockopt, and because of this the MSG_CONFIRM isnot being set at msg flags in the received messages.
> Could please elaborate how do we make sure the tx message successfulness are assesed at RT socket CAN.
> Thanks

Apparently you did not get it the first time, so I am going to try
again:

PLEASE DO NOT SEND MAILING LIST QUESTIONS TO THE XENOMAI-OWNER ADDRESS.

-- 
					    Gilles.


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN
       [not found] <20150317181631.GC16113@hermes.click-hack.org>
@ 2015-03-18  8:27 ` Narasimhaprasad Yedatore Achutha
  2015-03-18  8:42   ` Gilles Chanteperdrix
  2015-04-01 10:19   ` Narasimhaprasad Yedatore Achutha
  0 siblings, 2 replies; 7+ messages in thread
From: Narasimhaprasad Yedatore Achutha @ 2015-03-18  8:27 UTC (permalink / raw)
  To: 'gilles.chanteperdrix@xenomai.org',
	'xenomai-owner@xenomai.org',
	'xenomai@xenomai.org'

Hello All
I'm using RTSocket CAN in my application. Trying figure out how to ensure the CAN message tranmission succesfulness in my function
Previuosly I was able to assess the echoed (recv own msg) message with MSG_CONFIRM flag returned by recvmsg() while using just socket CAN functionalities.
However with RT SOcket CAN, the CAN_RAW_RECV_OWN_MSGS is not supported at rt_dev_setsockopt, and because of this the MSG_CONFIRM isnot being set at msg flags in the received messages.
Could please elaborate how do we make sure the tx message successfulness are assesed at RT socket CAN.
Thanks
YA
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2015-04-01 12:37 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.439.1426601187.27969.xenomai@xenomai.org>
2015-03-17 14:23 ` [Xenomai] CAN tx successfullness at Xenomai RT SocketCAN Narasimhaprasad Yedatore Achutha
     [not found] <20150317181631.GC16113@hermes.click-hack.org>
2015-03-18  8:27 ` Narasimhaprasad Yedatore Achutha
2015-03-18  8:42   ` Gilles Chanteperdrix
2015-04-01 10:19   ` Narasimhaprasad Yedatore Achutha
2015-04-01 11:06     ` Wolfgang Grandegger
2015-04-01 12:04       ` Narasimhaprasad Yedatore Achutha
2015-04-01 12:37         ` Wolfgang Grandegger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.