All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bird, Timothy" <Tim.Bird@sony.com>
To: Rafael Gago Castano <RGC@hms.se>,
	"fuego@lists.linuxfoundation.org"
	<fuego@lists.linuxfoundation.org>,
	"dhinakar.k@samsung.com" <dhinakar.k@samsung.com>
Cc: Frank Rowand <frowand.list@gmail.com>
Subject: Re: [Fuego] Problems with the serial transport.
Date: Tue, 30 May 2017 08:29:16 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF1FA9DCB1@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <HE1PR06MB303670058FACEA860855EFA4C2F00@HE1PR06MB3036.eurprd06.prod.outlook.com>



> -----Original Message-----
> From: Rafael Gago Castano on Tuesday, May 30, 2017 4:29 PM
> 
> Well, what seemed to fix the issue was turning off the line wrapping (using a
> VT100 control sequence), not the column length:
> 
> > printf "printf '\033[?7l'\r" > $SERIAL_DEV

OK - sorry.  I misread the thread.
> 
> But it doesn't seem to work consistently, e.g. it did work with our images
> flashed on NAND but not with our image booted for RAM booting. Yesterday
> it stopped working (it may be my mistake).
>  
OK - please let me know if you get more information about the
inconsistent behavior.

> 
> It would be nice to document these issues for the serial transport:
> 
> -Login must be handled separately (it's documented on the serio sources).
I have added a separate 'serlogin' program in the 'next' branch which is intended
to deal with this issue.  It works for me, but is a bit finicky.  But the goal is to
have it completely handle this particular issue.

See https://github.com/tbird20d/serlogin
and
https://bitbucket.org/tbird20d/fuego-core/src/805adb067afc492382ee23bc9178c059b90c043e/engine/overlays/base/base-board.fuegoclass?at=next

> -serio has issues with Busybox adding newlines (it's documented on the serio
> sources).

I'd like to see if this can be fixed in serio.  serio used to turn off
echoing, and we experimented with using a different mechanism
to detect end of program output.

I'm not sure if either of these would affect this issue, but 
I'll try to find some time to look at this before the 1.2 release.

> 
> I'm still blocked on the Busybox serial issues. I'll post here if I find something.
OK - thanks.
 -- Tim

> ________________________________
> 
> From: Bird, Timothy <Tim.Bird@sony.com>
> Sent: Tuesday, May 30, 2017 9:08:31 AM
> To: Rafael Gago Castano; fuego@lists.linuxfoundation.org;
> dhinakar.k@samsung.com
> Subject: RE: [Fuego] Problems with the serial transport.
> 
> > -----Original Message-----
> > From: Rafael Gago Castano on Friday, May 26, 2017 8:42 PM
> >
> > It looks like sercp --basic (using echo and cat) works, so it was just a matter
> of
> > disabling line wrapping on the terminal and everything works on the
> BusyBox
> > shell too. I guess that sercp failed because our device has no uuencode.
> 
> That's good to hear.  I didn't have time to figure out the problem using the
> busybox
> shell, but it's nice to hear there's an easy workaround (to make the column
> length long
> using stty).
> 
> It's too bad you had to figure out the missing 'uuencode' issue yourself.
> 
> IMHO it would be good to detect these automatically and adjust serio (or
> Fuego's use of serio) to automatically compensate.  I have a test in the 'next'
> branch that checks various features (presence of programs and other items),
> and reports if there are any problems.  I'll look at adding something to this
> test
> so that at least people will get a warning if there might be issues with the
> serial
> transport.  Also I'll think about doing some extra steps in Fuego, or about
> enhancing serio so that it will automatically deal with these issues.
> 
> Thanks for the report!
>  - - Tim
> 


  reply	other threads:[~2017-05-30  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  8:26 [Fuego] Problems with the serial transport Rafael Gago Castano
     [not found] ` <CGME20170526082622epcas2p3f251d5c044e5fdc2dba12312d1ec2f36@epcms5p7>
2017-05-26  8:46   ` Dhinakar Kalyanasundaram
2017-05-26  9:43     ` Rafael Gago Castano
2017-05-26 10:41       ` Rafael Gago Castano
2017-05-26 11:41         ` Rafael Gago Castano
2017-05-30  7:08           ` Bird, Timothy
2017-05-30  7:29             ` Rafael Gago Castano
2017-05-30  8:29               ` Bird, Timothy [this message]
2017-05-30 12:49                 ` Rafael Gago Castano

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=ECADFF3FD767C149AD96A924E7EA6EAF1FA9DCB1@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=RGC@hms.se \
    --cc=dhinakar.k@samsung.com \
    --cc=frowand.list@gmail.com \
    --cc=fuego@lists.linuxfoundation.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 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.