From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH] cangen: Support RTR frames with random or increment CAN IDs
Date: Wed, 07 Nov 2012 10:07:08 +0100 [thread overview]
Message-ID: <509A24BC.5070505@volkswagen.de> (raw)
In-Reply-To: <1352276048-21299-1-git-send-email-alexander.stein@systec-electronic.com>
Hello Alexander,
just yesterday evening i was pondering about making the canfd branch of the
can-utils the master branch ...
Due to added the CAN FD possibilities is also cleaned up the RTR sending
which can be done randomly now too.
See the commit log at
https://gitorious.org/linux-can/can-utils/commit/51c57c8445d5a0faef73f32fc9f5b772d4fde939
Please check out the canfd branch and see if cangen meets your requirements.
The same with 'candump' ...
There's a new '-x' option which prints extra message infos: RX/TX BRS ESI
Best regards,
Oliver
On 07.11.2012 09:14, Alexander Stein wrote:
> Signed-off-by: Alexander Stein<alexander.stein@systec-electronic.com>
> ---
> cangen.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/cangen.c b/cangen.c
> index efb8251..0037605 100644
> --- a/cangen.c
> +++ b/cangen.c
> @@ -339,6 +339,9 @@ int main(int argc, char **argv)
> frame.can_id |= CAN_EFF_FLAG;
> } else
> frame.can_id&= CAN_SFF_MASK;
> +
> + if (rtr_frame)
> + frame.can_id |= CAN_RTR_FLAG;
> }
>
> if (dlc_mode == MODE_RANDOM) {
> @@ -412,6 +415,9 @@ resend:
> frame.can_id |= CAN_EFF_FLAG;
> } else
> frame.can_id&= CAN_SFF_MASK;
> +
> + if (rtr_frame)
> + frame.can_id |= CAN_RTR_FLAG;
> }
>
> if (dlc_mode == MODE_INCREMENT) {
next prev parent reply other threads:[~2012-11-07 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 8:14 [PATCH] cangen: Support RTR frames with random or increment CAN IDs Alexander Stein
2012-11-07 9:07 ` Oliver Hartkopp [this message]
2012-11-07 9:26 ` Alexander Stein
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=509A24BC.5070505@volkswagen.de \
--to=oliver.hartkopp@volkswagen.de \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
/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