oracular (5) sergensio.5.gz

Provided by: libgensio-dev_2.8.2-6.1build1_amd64 bug

NAME

       sergensio - How to use a serial gensio

DESCRIPTION

       NOTE:  sergensio  is  deprecated,  the functionality for it is not done with the acontrol() and control()
       functions in the main gensio type.

       A sergensio object is a type of gensio that provides  serial  port  functions.   It  cannot  be  directly
       created,  instead  you  create  a  gensio  that  has  serial  port  capabilities  and  cast  it using the
       gensio_to_sergensio() function.

       A sergensio object may be a client, meaning that you can set serial  port  parameters  for  that  gensio.
       This is what you would normally expect, and works for all serial port types.

       A  sergensio object may also be a server, meaning that it can receive requests from the remote end to set
       serial port parameters.  Currently only the telnet gensio has server capability,  so  a  remote  end  may
       request that serial port parameters be set.

USING A CLIENT SERGENSIO

   ASYNCHRONOUS EVENTS

USING A SERVER SERGENSIO

   ASYNCHRONOUS EVENTS

SEE ALSO

       gensio(5),        sergensio_to_gensio(3),       gensio_to_sergensio(3),       sergensio_get_user_data(3),
       sergensio_is_client(3),       sergensio_baud(3),       sergensio_datasize(3),        sergensio_parity(3),
       sergensio_stopbits(3),    sergensio_flowcontrol(3),    sergensio_iflowonctrol(3),    sergensio_sbreak(3),
       sergensio_dtr(3),        sergensio_rts(3),        sergensio_signature(3),         sergensio_linestate(3),
       sergensio_modemstate(3),   sergensio_flowcontrol_state(3),  sergensio_flush(3),  sergensio_send_break(3),
       sergensio_b_alloc(3),       sergensio_b_free(3),       sergensio_baud_b(3),       sergensio_datasize_b(3)
       sergensio_parity_b(3),  sergensio_stopbits_b(3), sergensio_flowcontrol_b(3), sergensio_iflowonctrol_b(3),
       sergensio_sbreak_b(3), sergensio_dtr_b(3), sergensio_rts_b(3), gensio_event(3), sergensio_event(3)

KNOWN PROBLEMS

       None.

AUTHOR

       Corey Minyard <minyard@acm.org>