Bug 86388 - MAX_INPUT should be defined correctly
MAX_INPUT should be defined correctly
Status: CLOSED WONTFIX
Product: eCos
Classification: Retired
Component: Serial device driver (Show other bugs)
CVS
All Linux
low Severity low
: ---
: ---
Assigned To: Jonathan Larmour
Jonathan Larmour
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-20 22:06 EST by Jonathan Larmour
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-20 12:21:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jonathan Larmour 2003-03-20 22:06:50 EST
Description of problem:

POSIX's <limits.h> requires MAX_INPUT to be defined correctly and be at least
_POSIX_MAX_INPUT i.e. 255 chars. For the termios drivers, this means the serial
input buffer needs to be at least 255 chars - a CDL option for strict
conformance should exist which sets this.

However for the value of MAX_INPUT, it requires a call to serial_get_config with
CYG_IO_GET_CONFIG_SERIAL_BUFFER_INFO to get the buffer size and thus the value
of MAX_INPUT, so MAX_INPUT will have to be a sysconf()'d value... which means
implementing sysconf()!
Comment 1 Alex Schuilenburg 2003-06-20 12:21:14 EDT
This bug has moved to http://bugs.ecos.sourceware.org/show_bug.cgi?id=86388

Note You need to log in before you can comment on or make changes to this bug.