linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: janusz.uzycki@elproma.com.pl
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Krzysztof Borgulski <k.borgulski@elproma.com.pl>
Subject: Re: [PATCH 2/2] slcanpty: /dev/tty support for tests
Date: Mon, 10 Jun 2013 20:29:11 +0200	[thread overview]
Message-ID: <51B61AF7.901@hartkopp.net> (raw)
In-Reply-To: <3bdf2623dd49f435018b29b60d720a3b@beep.pl>

On 10.06.2013 11:53, janusz.uzycki@elproma.com.pl wrote:
> Primarily I wanted to use stdin/stdout (defined as "-") but it required
> splitted p descriptor to pin and pout... For the "-" socat can be used so I
> stopped here.

:-)

Ok, which of your three patches do you suggest to be applied now?

Is the terminal flags update patch enough?

Best regards,
Oliver

> 
> best regards
> Janusz
> 
> W dniu 2013-06-10 11:44, janusz.uzycki@elproma.com.pl napisał(a):
>> From 4c6115b210b64cf93493c93b05f82c83a085fb73 Mon Sep 17 00:00:00 2001
>> From: Janusz Uzycki <j.uzycki@elproma.com.pl>
>> Date: Fri, 7 Jun 2013 23:02:13 +0200
>> Subject: [PATCH 2/2] slcanpty: /dev/tty support for tests
>>
>>
>> Signed-off-by: Janusz Uzycki <j.uzycki@elproma.com.pl>
>> ---
>>  slcanpty.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/slcanpty.c b/slcanpty.c
>> index f312362..b7e8ed7 100644
>> --- a/slcanpty.c
>> +++ b/slcanpty.c
>> @@ -44,6 +44,7 @@
>>  /* maximum rx buffer len: extended CAN frame with timestamp */
>>  #define SLC_MTU (sizeof("T1111222281122334455667788EA5F\r")+1)
>>  #define DEVICE_NAME_PTMX "/dev/ptmx"
>> +#define DEVICE_NAME_TTY "/dev/tty"
>>
>>  #define DEBUG
>>
>> @@ -407,10 +408,13 @@ int main(int argc, char **argv)
>>                         " /dev/ttyc0 for the slcan application\n", argv[0]);
>>                 fprintf(stderr, "e.g. for pseudo-terminal '%s %s can0' creates"
>>                         " /dev/pts/N\n", argv[0], DEVICE_NAME_PTMX);
>> +               fprintf(stderr, "e.g. for pseudo-terminal '%s %s can0' uses"
>> +                       " console terminal (for testing purposes)\n",
>> argv[0], DEVICE_NAME_TTY);
>>                 fprintf(stderr, "\n");
>>                 return 1;
>>         }
>>
>> +       if (strcmp(argv[1], DEVICE_NAME_TTY) != 0)
>>         select_stdin = check_select_stdin();
>>
>>         /* open pty */
>> -- 
>> 1.7.11.3


  reply	other threads:[~2013-06-10 18:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2DAB3DC2841347E7AF7833620339B427@laptop2>
2013-06-05 19:44 ` slcanpty Oliver Hartkopp
2013-06-06 12:03   ` slcanpty Janusz Uzycki
2013-06-06 18:31     ` slcanpty Oliver Hartkopp
2013-06-06 20:43       ` slcanpty janusz.uzycki
2013-06-07 13:40       ` [PATCH] slcanpty janusz.uzycki
2013-06-08 11:09         ` Oliver Hartkopp
2013-06-10  9:06           ` janusz.uzycki
2013-06-10  9:16             ` janusz.uzycki
2013-06-10  9:36               ` janusz.uzycki
2013-06-10  9:42                 ` [PATCH 1/2] slcanpty: "slcanpty < /dev/null" issue fix janusz.uzycki
2013-06-10  9:44                   ` [PATCH 2/2] slcanpty: /dev/tty support for tests janusz.uzycki
2013-06-10  9:53                     ` janusz.uzycki
2013-06-10 18:29                       ` Oliver Hartkopp [this message]
2013-06-10 18:38                         ` janusz.uzycki
2013-06-11 20:28                           ` Oliver Hartkopp
2013-06-11 16:29       ` slcanpty janusz.uzycki
2013-06-11 20:32         ` slcanpty Oliver Hartkopp
2013-06-11 21:19           ` slcanpty janusz.uzycki
2013-06-12 15:25             ` slcanpty Oliver Hartkopp
2013-06-14  8:42               ` slcanpty Janusz Uzycki
2013-06-18  8:24               ` slcanpty j.uzycki
2013-06-19 17:15                 ` slcanpty Oliver Hartkopp
2013-06-19 22:39                   ` slcanpty j.uzycki

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=51B61AF7.901@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=janusz.uzycki@elproma.com.pl \
    --cc=k.borgulski@elproma.com.pl \
    --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;
as well as URLs for NNTP newsgroup(s).