qemu5 and zynq console input

[Joel Sherrill]

On Tue, Dec 1, 2020 at 3:06 PM Chris Johns <chrisj at rtems.org> wrote:

> On 2/12/20 3:29 am, Gedare Bloom wrote:
>  On Mon, Nov 30, 2020 at 4:59 PM Chris Johns <chrisj at rtems.org
> > <mailto:chrisj at rtems.org>> wrote:
> >
> >     On 1/12/20 10:25 am, Joel Sherrill wrote:
> >     > Does this combination work for anyone? I am suspicious that this
> broke
> >     with the
> >     > qemu version bump in the RSB.
> >
> >     I did not test input. The tester does not have the ability to test
> input.
> >
> > Would something like https://pexpect.readthedocs.io/en/stable/
> > <https://pexpect.readthedocs.io/en/stable/> work?
>
> Yes it would and it is small enough to be included.
>
> > It could be an interesting
> > project to get even one input-related test running under automation.
>
> It would be and this failure highlights a weakness in the rtems-test
> command.
>
> I would need to see where in the runtime I would place input processing
> and if
> the input side would need an extra thread.
>

FWIW I retrieved the qemu4 bset files (two) and think I built a qemu4 again.
I am not sure input worked on it either.  Confirmation appreciated.

>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20201201/600c52a4/attachment.html>