Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1908 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1908.

Report 1908 Actions

    Problem Report Number 1908
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0227
    Raised 2000-02-03 08:00
    Updated 2003-03-13 08:00
    Published 2000-02-18 08:00
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.4.4
    Test Identification POSIX.os/devclass/tcgetattr 3
    Specification System Interfaces and Headers Issue 5
    Location in Spec See Problem Text
    Linked Problem Reports PIN4.058, (in, old, system)
    Problem Summary PIN5.007 POSIX.os/devclass/tcgetattr/T.tcgetattr 3 Failed POSIX-Part 1: System Application Program Interface (API) IEEE std 1003.1, 1996, Section 7.2.1.1 page 151 states: "If differing baud rates are not suppo...
    Problem Text
    POSIX.os/devclass/tcgetattr/T.tcgetattr 3 Failed

    **************************************************

    POSIX-Part 1: System Application Program Interface (API)
    IEEE std 1003.1, 1996, Section 7.2.1.1 page 151 states:

    "If differing baud rates are not supported, the rate returned as
    the output baud rate shall be the actual baud rate. The rate
    returned as the input baud rate shall be either the number zero
    or the output rate (as one of the symbolic values). Permitting
    either behavior is obsolescent. 3)."

    Our implementation does not support split baud rates, and
    returns the output baud rate, which is permited by POSIX.
    Here the tests expect a return value of only zero, which we think
    is not correct.
    is not correct.



    Test Output

    /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 3 Failed

    Test Description:
    If general terminal interface supported:
    If the implementation supports input and output baud rates that
    differ:
    The baud rates stored in the termios structure returned by the
    tcgetattr() reflect the actual baud rates even when they are
    equal
    Otherwise
    The output baud rate stored in the termios structure returned by
    the tcgetattr() reflect the actual baud rate. The input baud
    rate stored in this termios structure is equal to zero. In
    POSIX mode the input baud rate may also equal the actual baud
    rate.
    This test is not executed in XPG3 mode.
    Posix Ref: Component TCGETATTR Assertion 7.2.1.2-05(C)

    Test Strategy:
    OPEN and initialise terminal file and loop back file
    SET the output speed to VSX_TERMIOS_SPEED using cfsetospeed().
    FIND a supported input speed not equal to VSX_TERMIOS_SPEED, by
    calling cfsetispeed() and tcsetattr() with different input speeds
    until an EINVAL error is not generated.
    IF one is found:
    VERIFY that tcgetattr() returns the actual baud rates.
    SET the input speed to the output speed using tcsetattr() with
    input speed 0.
    VERIFY that tcgetattr() returns the actual baud rates.
    ELSE
    SET the input speed to the output speed using tcsetattr() with
    input speed 0.
    VERIFY that tcgetattr() returns the actual output baud rate and an
    input baud rate of zero, or (for POSIX mode only) the actual input
    baud rate.

    Test Information:
    tcgetattr() did not return correct input baud rate when input = output
    expected 0, observed 9600



    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The POSIX.1-1996 specification allowed the input baud rate to be set either to
    zero or to the input baud rate in the case that split baud rates are not
    supported. The current XSH specifications require, as an extension to the
    POSIX definition, that the input baud rate is set to zero in these
    circumstances. However, the proposed revisions to POSIX.1 to which a future
    revision of XSH is expected to align, requires that the input baud rate is set
    to the output baud rate. Since the behavior of this system matches an expected
    future direction, a permanent interpretation is granted.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority