X hits on this document

PDF document

February 10, 2006 - page 49 / 238

1023 views

0 shares

0 downloads

0 comments

49 / 238

3.4. BRIDGING

37

8-9

Auxiliary channel info. For channel Fh, this is byte 8 is the interrupt for the system interface, byte 9 is the interrupt for the event message buffer interface. Valid values are: 00h-0Fh - IRQ 0-15 10h-13h - PCI A-D, respectively 14h - SMI 15h - SCI 20h-5Fh - System interrupt 0-62, respecitively 60h - Assigned by ACPI, SMBIOS, or a plug and play mechanism. FFh - No interrupt or unspecified All other values are reserved. For Original Equipment Manufacturer (OEM) channel types, this value is OEM defined. These bytes are reserved for all other channel types. Table 3.3: Get Channel Info Command, NetFN App (06h), Cmd 42h

3.4.2

Sending

Bridged

Message

Table 3.4 shows the format of a Send Message command. Note that the spec says the response can have response data for non-system interface channels. However, this is not actually the case, response data for LAN and serial channels is carried in a different manner.

Request

Channel information, bits are: 0-4 - Channel number 4-5 - reserved 6-7 - tracking type. See section 3.4.3 for more information. Values are:

0

00b - No tracking 01b - Track request 10b - Send raw. This is a test mechanism or a mechanism used for transmitting proprietary protocols. It is optional.

1-n Response

11b - reserved Message data. The format depends on the channel type. See the section on the specific

channel type for more information.

Completion code. If transmitting on an IPMB, SMBus, or PCI management bus, the following return codes are used to inform the sender of sending problems:

  • 0

    81h - lost arbitration

82h - Bus Error

83h - NAK on Write Table 3.4: Send Message Command, NetFN App (06h), Cmd 34h

Document info
Document views1023
Page views1023
Page last viewedThu Jan 19 03:17:17 UTC 2017
Pages238
Paragraphs8090
Words85809

Comments