On Tue, 1 Mar 2016, Felipe Balbi wrote:
> Hi,
>
> Robert Baldyga writes:
> >> Olivier Schonken writes:
> >>> Hope I'm not raising an issue which actually is my own stupidity.
> >>>
> >>> I recently upstreamed my embedded Linux kernel to version 4.4, after which
> >>> I started experiencing issu
Hi Felipe
As far as I could see in Systemd, getty PID changes, so the SIGHUP
should be received to close getty. The re-opening of the
port with getty is when the issues begin.
Regards
Olivier Schonken
On 1 March 2016 at 09:27, Felipe Balbi wrote:
>
> Hi,
>
> Robert Baldyga writes:
>>> Oliv
Hi,
Robert Baldyga writes:
>> Olivier Schonken writes:
>>> Hope I'm not raising an issue which actually is my own stupidity.
>>>
>>> I recently upstreamed my embedded Linux kernel to version 4.4, after which
>>> I started experiencing issues with my serial gadget - acm and obex. I used
>>> to
Hi Robert
I may have used very bad language to describe the problem "hang up". A
better description would be to say that when connecting to the ttyACM
gadget via a terminal, it works at startup, but if the usb device is
plugged out, and back in again, comms with it is unresponsive, regardless
of
Hi Oliver,
On 02/29/2016 08:34 AM, Felipe Balbi wrote:
>
> Hi,
>
> Olivier Schonken writes:
>> Hope I'm not raising an issue which actually is my own stupidity.
>>
>> I recently upstreamed my embedded Linux kernel to version 4.4, after which
>> I started experiencing issues with my serial gadge
Hi,
Olivier Schonken writes:
> Hope I'm not raising an issue which actually is my own stupidity.
>
> I recently upstreamed my embedded Linux kernel to version 4.4, after which
> I started experiencing issues with my serial gadget - acm and obex. I used
> to be able to run a getty console on it
