csx_Parse_CISTPL_BYTEORDER(9f)

1csx_Parse_CISTPL_BYTEORDERK(e9rFn)el Functions for Dricvsexr_sParse_CISTPL_BYTEORDER(9F)
2
3
4

NAME

6       csx_Parse_CISTPL_BYTEORDER - parse the Byte Order tuple
7

SYNOPSIS

9       #include <sys/pccard.h>
10
11
12
13       int32_t csx_Parse_CISTPL_BYTEORDER(client_handle_t ch, tuple_t *tu,
14            cistpl_byteorder_t *cbo);
15
16

INTERFACE LEVEL

18       Solaris DDI Specific (Solaris DDI)
19

PARAMETERS

21       ch      Client handle returned from csx_RegisterClient(9F).
22
23
24       tu      Pointer  to  a  tuple_t structure (see tuple(9S)) returned by a
25               call to csx_GetFirstTuple(9F) or csx_GetNextTuple(9F).
26
27
28       cbo     Pointer to a cistpl_byteorder_t structure  which  contains  the
29               parsed CISTPL_BYTEORDER tuple information upon return from this
30               function.
31
32

DESCRIPTION

34       This function parses the Byte Order  tuple,  CISTPL_BYTEORDER,  into  a
35       form usable by PC Card drivers.
36
37
38       The  CISTPL_BYTEORDER  tuple shall only appear in a partition tuple set
39       for a memory-like partition. It specifies two parameters: the order for
40       multi-byte data, and the order in which bytes map into words for 16-bit
41       cards.
42

STRUCTURE MEMBERS

44       The structure members of cistpl_byteorder_t are:
45
46         uint32_t     order;     /* byte order code */
47         uint32_t     map;       /* byte mapping code */
48
49
50
51       The fields are defined as follows:
52
53       order     This field specifies the byte order  for  multi-byte  numeric
54                 data.
55
56                 TPLBYTEORD_LOW    Little endian order
57
58
59                 TPLBYTEORD_VS     Vendor specific
60
61
62
63       map       This  field  specifies  the  byte mapping for 16-bit or wider
64                 cards.
65
66                 TPLBYTEMAP_LOW     Byte zero is least significant byte
67
68
69                 TPLBYTEMAP_HIGH    Byte zero is most significant byte
70
71
72                 TPLBYTEMAP_VS      Vendor specific mapping
73
74
75

RETURN VALUES

77       CS_SUCCESS                  Successful operation.
78
79
80       CS_BAD_HANDLE               Client handle is invalid.
81
82
83       CS_UNKNOWN_TUPLE            Parser does not know how to parse tuple.
84
85
86       CS_NO_CARD                  No PC Card in socket.
87
88
89       CS_NO_CIS                   No  Card  Information  Structure  (CIS)  PC
90                                   Card.
91
92
93       CS_UNSUPPORTED_FUNCTION     No PCMCIA hardware installed.
94
95

CONTEXT

97       This function may be called from user or kernel context.
98