IRUSER Shared Memory - Revision history

Wwylele: /* ReceiveBufferInfo/SendBufferInfo */

2017-03-01T19:08:34Z

ReceiveBufferInfo/SendBufferInfo

← Older revision		Revision as of 22:08, 1 March 2017
Line 74:		Line 74:

	=ReceiveBufferInfo/SendBufferInfo=		=ReceiveBufferInfo/SendBufferInfo=
	~~(Information below is poorly verified against real hardware. Please help me verify them -- [[User:Wwylele\|Wwylele]] ([[User talk:Wwylele\|talk]]))~~

	The BufferInfo sections store data validity information for the two buffers		The BufferInfo sections store data validity information for the two buffers
Line 98:		Line 97:
	\| 0xC		\| 0xC
	\| 0x4		\| 0x4
	\| Unknown		\| Unknown/Unused?
	\|}		\|}

Wwylele: Undo revision 19719 by Mailwl (talk) First, I don't see how "Read index" is more readable. Second, I did hardware test showing that the last four bytes of buffer info is untouched

2017-02-28T08:02:03Z

Undo revision 19719 by Mailwl (talk) First, I don't see how "Read index" is more readable. Second, I did hardware test showing that the last four bytes of buffer info is untouched

← Older revision		Revision as of 11:02, 28 February 2017
Line 86:		Line 86:
	\| 0x0		\| 0x0
	\| 0x4		\| 0x4
	\| ~~Read~~ index of valid packets		\| Start index of valid packets
	\|-		\|-
	\| 0x4		\| 0x4
Line 93:		Line 93:
	\|-		\|-
	\| 0x8		\| 0x8
	\| ~~0x8~~		\| 0x4
	\| Number of valid packets		\| Number of valid packets
			\|-
			\| 0xC
			\| 0x4
			\| Unknown
	\|}		\|}

Mailwl: /* ReceiveBufferInfo/SendBufferInfo */

2017-02-28T07:54:05Z

ReceiveBufferInfo/SendBufferInfo

← Older revision		Revision as of 10:54, 28 February 2017
Line 86:		Line 86:
	\| 0x0		\| 0x0
	\| 0x4		\| 0x4
	\| ~~Start~~ index of valid packets		\| Read index of valid packets
	\|-		\|-
	\| 0x4		\| 0x4
Line 93:		Line 93:
	\|-		\|-
	\| 0x8		\| 0x8
	\| ~~0x4~~		\| 0x8
	\| Number of valid packets		\| Number of valid packets
	\|-
	~~\| 0xC~~
	~~\| 0x4~~
	~~\| Unknown~~
	\|}		\|}

Wwylele: /* Packet structure */

2017-02-28T07:45:32Z

Packet structure

← Older revision		Revision as of 10:45, 28 February 2017
Line 152:		Line 152:
	\| 0x3 or 0x4 +payload_length		\| 0x3 or 0x4 +payload_length
	\| 0x1		\| 0x1
	\| ~~crc8 (x^~~8 ~~+ x^2 + x + 1)~~ over data above (header + payload)		\| [[CRC-8-CCITT]] over data above (header + payload)
	\|-		\|-
	\|}		\|}

Wwylele: /* Packet structure */

2017-02-23T15:45:09Z

Packet structure

← Older revision		Revision as of 18:45, 23 February 2017
Line 135:		Line 135:
	\| 0x1		\| 0x1
	\| 0x1		\| 0x1
	\| ~~Unknown~~		\| Destination network ID?
	\|-		\|-
	\| 0x2		\| 0x2

Wwylele: /* StatusInfo */

2017-02-23T15:44:47Z

StatusInfo

@@ Line 57: / Line 57: @@
 |-
 | 0xC
-| 0x4
+| 0x1
 | Unknown
 |}

Wwylele at 13:20, 23 February 2017

2017-02-23T12:20:50Z

← Older revision		Revision as of 15:20, 23 February 2017
Line 74:		Line 74:
	\| 0x0		\| 0x0
	\| 0x4		\| 0x4
	\| Start index of valid ~~packages~~		\| Start index of valid packets
	\|-		\|-
	\| 0x4		\| 0x4
	\| 0x4		\| 0x4
	\| End index of valid ~~packages~~		\| End index of valid packets
	\|-		\|-
	\| 0x8		\| 0x8
	\| 0x4		\| 0x4
	\| Number of valid ~~packages~~		\| Number of valid packets
	\|-		\|-
	\| 0xC		\| 0xC
Line 98:		Line 98:
	\|-		\|-
	\| 0x0		\| 0x0
	\| 0x8 * ~~package_count~~ (specified in Init parameter)		\| 0x8 * packet_count (specified in Init parameter)
	\| ~~PackageInfo~~{u32 offset_to_data_buffer, u32 data_length}		\| PacketInfo{u32 offset_to_data_buffer, u32 data_length}
	\|-		\|-
	\| 0x8 * ~~package_count~~		\| 0x8 * packet_count
	\| buffer_size - 0x8 * ~~package_count~~		\| buffer_size - 0x8 * packet_count
	\| Data buffer		\| Data buffer
	\|}		\|}

	The buffers are two circular buffers. A new ~~package~~ is added to the end of previous ~~package~~ in the data buffer, with ~~package~~ info added to ~~PackageInfo~~[end_index++]. Note that if an added ~~package~~ exceeds the end of the buffer, the exceeding data will be wrapped around to the beginning of the data buffer.		The buffers are two circular buffers. A new packet is added to the end of previous packet in the data buffer, with packet info added to PacketInfo[end_index++]. Note that if an added packet exceeds the end of the buffer, the exceeding data will be wrapped around to the beginning of the data buffer.


			==Packet structure==
			A packet in the data buffer consists of a header, payload and a crc8 checksum
			{\| class="wikitable" border="1"
			\|-
			! Relative offset
			! Size
			! Description
			\|-
			\| 0x0
			\| 0x1
			\| Fixed value 0xA5?
			\|-
			\| 0x1
			\| 0x1
			\| Unknown
			\|-
			\| 0x2
			\| 0x1
			\| The highest bit is unknown.
			When second highest bit is clear, the rest bit[0:5] of this byte is the payload length; otherwise bit[0:5] is the higher byte of the payload length
			\|-
			\| 0x3
			\| 0x1
			\| When bit[6] of previous byte is set, this byte is the lower byte of the payload length; other wise this byte doesn't present
			\|-
			\| 0x3 or 0x4
			\| payload length
			\| payload
			\|-
			\| 0x3 or 0x4 +payload_length
			\| 0x1
			\| crc8 (x^8 + x^2 + x + 1) over data above (header + payload)
			\|-
			\|}

Wwylele: /* ReceiveBufferInfo/SendBufferInfo */

2017-02-22T14:20:52Z

ReceiveBufferInfo/SendBufferInfo

← Older revision		Revision as of 17:20, 22 February 2017
Line 82:		Line 82:
	\| 0x8		\| 0x8
	\| 0x4		\| 0x4
	\| Number valid packages		\| Number of valid packages
	\|-		\|-
	\| 0xC		\| 0xC

Wwylele at 15:19, 22 February 2017

2017-02-22T14:19:08Z

← Older revision		Revision as of 17:19, 22 February 2017
Line 60:		Line 60:
	\| Unknown		\| Unknown
	\|}		\|}

			=ReceiveBufferInfo/SendBufferInfo=
			(Information below is poorly verified against real hardware. Please help me verify them -- [[User:Wwylele\|Wwylele]] ([[User talk:Wwylele\|talk]]))

			The BufferInfo sections store data validity information for the two buffers

			{\| class="wikitable" border="1"
			\|-
			! Relative offset
			! Size
			! Description
			\|-
			\| 0x0
			\| 0x4
			\| Start index of valid packages
			\|-
			\| 0x4
			\| 0x4
			\| End index of valid packages
			\|-
			\| 0x8
			\| 0x4
			\| Number valid packages
			\|-
			\| 0xC
			\| 0x4
			\| Unknown
			\|}

			=ReceiveBuffer/SendBuffer=

			{\| class="wikitable" border="1"
			\|-
			! Relative offset
			! Size
			! Description
			\|-
			\| 0x0
			\| 0x8 * package_count (specified in Init parameter)
			\| PackageInfo{u32 offset_to_data_buffer, u32 data_length}
			\|-
			\| 0x8 * package_count
			\| buffer_size - 0x8 * package_count
			\| Data buffer
			\|}

			The buffers are two circular buffers. A new package is added to the end of previous package in the data buffer, with package info added to PackageInfo[end_index++]. Note that if an added package exceeds the end of the buffer, the exceeding data will be wrapped around to the beginning of the data buffer.

Wwylele at 13:13, 22 February 2017

2017-02-22T12:13:28Z

← Older revision		Revision as of 15:13, 22 February 2017
Line 3:		Line 3:
	=Overall Structure=		=Overall Structure=

	The shared memory consists of 2 or 5 components, depending on which Init function is called. For InitializeIrnopShared, ir service puts more information to the shared memory and applications can read it directly; for InitializeIrnop, ir service puts less information and store the rest in its local storage. All these components are adjacent to each other.		The shared memory consists of 2 or 5 components, depending on which Init function is called. For InitializeIrnopShared, ir service puts more information to the shared memory and applications can read it directly; for InitializeIrnop, ir service puts less information and store the rest in its local storage. All these components are adjacent to each other, without any padding, which means the data can be unaligned if the size specified in Init is unaligned.
	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
	\|-		\|-