Files
rtems/c
Joel Sherrill 120adc209f Patch cd2401fix.diff from Charles-Antoine Gauthier <charles.gauthier@nrc.ca>
to address problems triggered when switching modes.  His ChangeLog:


  * c/src/lib/libbsp/m68k/mvme167/console/console-recording:
    New file. Console debug info recording functions.
  * c/src/lib/libbsp/m68k/mvme167/console/console.c:
    Try to eliminate garbled characters when the line characteristics are
    changed. Added debug info logging calls
  * c/src/tests/libtests/termios/init.c: Remove sleep calls.

His longer description :)

  This one was hard. I tried a number of approaches, and eventually came
  to the conclusion that one cannot tell when the output FIFO have drained
  completely. Consequently, the driver now includes delay loops that get
  executed when the line discipline is changed. Yuk. I had a look at the
  Linux and FreeBSD drivers; the FreeBSD driver uses delay loops while the
  Linux driver contain warnings about characters getting garbled when the
  line discipline is changed.

  The new driver only re-initializes the cd2401 if some registers need to
  change, otherwise, the chip is left alone. This is equivalent to caching
  the previous setting and only changing things if they need to be. The
  code is kind of ugly, but what can you do. The delay loops are only used
  if the chip must be re-initialized.

  Optional instrumentation that records what the driver is doing is
  provided. It should be obvious how to enable it and how to use it. It's
  not the best, but it got the job done.

  I ran the termios test. The delay loops I had introduced are no longer
  necessary, so I took them out. The patch includes that change. The test
  re-initializes the chip whenever the canonical input test (test 4) is
  run THE FIRST TIME OR AFTER THE LINE WAS RESET (test 1). The test did
  not garble any characters when the chip was re-initialized (or when it
  was not) while running at 9600 bsp. I therefore think that I have a
  solution.
2000-05-08 17:27:46 +00:00
..
1999-10-28 14:07:54 +00:00
2000-01-10 20:38:04 +00:00

#
#  $Id$
#

This is the top level of the RTEMS directory structure.  The following
is a description of the files and directories in this directory:

  Makefile.in
    The top-level Make command file used to build the C implementation
    of RTEMS.  [RTEMS assumes the use of GNU make.]

  README
    This file.

  REQUIRES
    A list of the other tools which are assumed to be installed
    before RTEMS is built.

  SUPPORT
    Information on third-party support for RTEMS.

  build-tools
    This directory contains the source for various utilities
    needed to build RTEMS.

  make
    Make command files "included" from those in the source distribution.
    [RTEMS assumes the use of GNU make.]

  patches
    This directory contains patches for this release of RTEMS.

  src
    This directory contains the source code for the C
    implementation of RTEMS as well as the test suites, sample
    applications, Board Support Packages, Device Drivers, and
    support libraries.