From: Yegor Yefremov <yegorslists@googlemail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: barebox remote control
Date: Mon, 22 Aug 2016 15:10:14 +0200 [thread overview]
Message-ID: <CAGm1_kuH3Z=Tev7Ra129C9QFMCM9ryhhTy_KS5Sji2ykabYXiw@mail.gmail.com> (raw)
In-Reply-To: <CAGm1_ks9wTMiP2EBoO9BKGkckuTRqkinaazxWXTkNrJKSc7b=w@mail.gmail.com>
Hi Sascha,
On Mon, Aug 22, 2016 at 11:05 AM, Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> On Mon, Aug 22, 2016 at 7:28 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>> Hi Yegor,
>>
>> On Fri, Aug 19, 2016 at 03:45:22PM +0200, Yegor Yefremov wrote:
>>> Hi Sascha,
>>>
>>> On Thu, Aug 18, 2016 at 9:48 AM, Yegor Yefremov
>>> <yegorslists@googlemail.com> wrote:
>>> > Are you planning to create a standalone PyPI package for bbremote? It
>>> > would be very handy.
>>>
>>> I'll try to create such a package on my GitHub account and then we
>>> will see how to proceed. Porting to Python 3 is really funny :-) str
>>> vs. bytearrays ....
>>>
>>> > Have you already contacted pyserial maintainers, so that they could
>>> > provide a configurable option for RFC2217 related timeout
>>> > (https://github.com/pyserial/pyserial)?
>>>
>>> I'll drop own pyserial and rely on upstream.
>>
>> Thanks. We haven't done anything in that direction yet.
>
> Take a look at this repo: https://github.com/yegorich/bbremote
>
> Following commands are already working in both Py2/3:
>
> bbremote ping
> bbremote run "devinfo"
> bbremote getenv "global.version"
>
> So far there was only one place, where I explicitly make distinction
> between Py2 and 3. Everything else seems to work well with bytearray
> (http://www.devdungeon.com/content/working-binary-data-python).
>
> TODO:
>
> 1. bbremote console works only in Py3, in Py2 it seems to freeze
> 2. add proper dependencies for setup.py (enum, enum34 for Py2 and
> crcmod and pyserial for all versions). What minial Py3 version should
> be supported? Perhaps choose 3.4 as is available on current Debian 8
> 3. licence: should we keep Barebox licence or move to MIT?
> 4. more tests
What is "bbremote listen" for?
Yegor
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-08-22 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 7:48 Yegor Yefremov
2016-08-19 13:45 ` Yegor Yefremov
2016-08-22 5:28 ` Sascha Hauer
2016-08-22 9:05 ` Yegor Yefremov
2016-08-22 13:10 ` Yegor Yefremov [this message]
2016-08-23 9:01 ` Yegor Yefremov
2016-08-23 9:05 ` Jan Lübbe
2016-08-23 9:24 ` Yegor Yefremov
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='CAGm1_kuH3Z=Tev7Ra129C9QFMCM9ryhhTy_KS5Sji2ykabYXiw@mail.gmail.com' \
--to=yegorslists@googlemail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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