Any users of the Termios receive/send callbacks?
sebastian.huber at embedded-brains.de
Tue Mar 21 06:32:29 UTC 2017
On 21/03/17 00:57, Chris Johns wrote:
> On 20/03/2017 20:47, Sebastian Huber wrote:
>> On 20/03/17 10:38, Pavel Pisa wrote:
>>> Hello Sebastian,
>>> On Thursday 23 of February 2017 07:51:13 Sebastian Huber wrote:
>>>> >the RTEMS Termios implementation provides receive and send callbacks:
>>>> >There is no API to install these callbacks. They are not used in the
>>>> >RTEMS code base. Is there someone how uses this stuff? I would
>>>> like to
>>>> >change the invocation conditions to use them for the poll(), select()
>>>> >and kqueue() support.
>>> it would be great. Would it work with bare RTEMS or libbsd
>>> would be required? If it can be used without libbsd
>>> on memory constrained systems then it would be great.
>> I already checked in the poll() and select() support for Termios in
>> libbsd. The poll() and select() functions are a part of libbsd. They use
>> the sleep/wakeup support of BSD which in turn uses a hash table of sleep
>> queues. This is indeed a problem for memory constrained systems. I think
>> with some work it might be possible to provide a low memory footprint
>> configuration of libbsd, however, I don't have time/budget for this.
>> There are some fundamental problems with the RTEMS Termios
>> implementation to fully support POSIX Termios, e.g. input processing is
>> mostly done by the reading task (e.g. echo). One option is to use the
>> Termios support of FreeBSD with the low level drivers of RTEMS to fix
> I am a little confused by this and what we are attempting to do here.
I don't attempt anything to do. I just wanted to share some issues we
found while porting the Erlang virtual machine to RTEMS.
> Why would someone want 'select' or 'poll' on a memory constrained
> system? I understand in the context of libbsd it allows us to bring
> existing code onto a board. Is this also a requirement for memory
> constrained systems?
What is memory constrained? It would be nice to use libbsd with lets say
1-2MiB of RAM.
> The other aspect is how we document and explain "Termios for RTEMS" if
> we have two differing implementations where code may not be portable
> between a libbsd build and a non-libbsd build, ie legacy networking?
> For example I have a large project that can can be built with the
> legacy and libbsd networking stacks. If the libbsd termios is a better
> implementation then I see no problem but it is not clear to me if this
> is the case.
I don't want to think of Termios at the moment since this causes nightmares.
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users