linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: kime@ixxat.de
Cc: socketcan-core@lists.berlios.de, linux-can@vger.kernel.org
Subject: Re: CAN State Information
Date: Fri, 09 Dec 2011 15:49:50 +0100	[thread overview]
Message-ID: <4EE2200E.4060403@grandegger.com> (raw)
In-Reply-To: <166589D0B9DD2547A1319599B9BADA1FC19A38@vsv-exchange.ixxat.intranet.priv>

On 12/09/2011 02:41 PM, kime@ixxat.de wrote:
> I noticed that when libsocketcan calls send_dump_request() it returns a message for me that has a length of 3424 with recvmsg().  This is not the full message, if I add a loop into the routine to again receive, I receive a second message this time with a length of 1424.  I added some prints into the routine to output strings and sizes:
> 
> First read:
> nl_msg:-1073753668  u_msglen:3424
> lo
> nl_msg:-1073752676  u_msglen:2432
> eth0
> nl_msg:-1073751668  u_msglen:1424
> can0
> nl_msg:-1073750956  u_msglen:712
> can1
> 
> Second read:
> nl_msg:-1073753668  u_msglen:1424
> can2
> nl_msg:-1073752956  u_msglen:712
> can3
> 
> With this loop, it seems to work.  Does this make sense?

Yes, could you send a patch (showing your modifications)?

Wolfgang.

  reply	other threads:[~2011-12-09 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166589D0B9DD2547A1319599B9BADA1FC1960C@vsv-exchange.ixxat.intranet.priv>
     [not found] ` <166589D0B9DD2547A1319599B9BADA1FC1960C-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-06 15:26   ` CAN State Information Wolfgang Grandegger
     [not found]     ` <4EDE342E.8030102-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-06 18:54       ` Wolfram Sang
2011-12-08  8:43       ` kime-Z4QKGCRq86k
     [not found]         ` <166589D0B9DD2547A1319599B9BADA1FC1981F-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-08 19:15           ` Wolfgang Grandegger
2011-12-09  8:03             ` kime
     [not found]               ` <166589D0B9DD2547A1319599B9BADA1FC19968-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09  8:15                 ` Wolfgang Grandegger
     [not found]                   ` <4EE1C3BF.70104-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09  8:19                     ` Wolfgang Grandegger
     [not found]                       ` <4EE1C47A.7080507-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09  8:45                         ` kime-Z4QKGCRq86k
     [not found]                           ` <166589D0B9DD2547A1319599B9BADA1FC1998A-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09  9:00                             ` Wolfgang Grandegger
2011-12-09 13:41                               ` kime
2011-12-09 14:49                                 ` Wolfgang Grandegger [this message]
     [not found]                                   ` <4EE2200E.4060403-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-12 10:21                                     ` kime-Z4QKGCRq86k

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE2200E.4060403@grandegger.com \
    --to=wg@grandegger.com \
    --cc=kime@ixxat.de \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan-core@lists.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).