USB services: Difference between revisions

Line 678:

==== PostBufferAsync ====

Takes an input u32 '''size''', an input u64 '''buffer''', and an input u64 '''id''', returns an output u32 '''xferId'''.

Takes an input u32 '''size''', an input u64 '''buffer''', and an input u64 '''Id''', returns an output u32 '''xferId'''.

Starts a data transfer with a single urb.

The official sw func which uses this cmd and handles waiting on the Event passes value 0 for the '''id'''. The async version which exposes this cmd directly uses '''id''' from user input - the user funcs pass a value starting at 0 then increment it each time (for sending multiple requests at once, with 0 for the first request in this set of requests).

The official sw func which uses this cmd and handles waiting on the Event passes value 0 for the '''Id'''. The async version which exposes this cmd directly uses '''Id''' from user input - the user funcs pass a value starting at 0 then increment it each time (for sending multiple requests at once, with 0 for the first request in this set of requests). Note that '''Id''' can be arbitrary, the sysmodule doesn't require a certain range for this.

On newer sysvers the state fields setup by [[#CreateSmmuSpace]] are compared with '''buffer'''. If it's within bounds of the SmmuSpace (which won't be the case when [[#CreateSmmuSpace]] wasn't used), it will then verify that buffer+buffer_size is within bounds throwing an error otherwise. Note that a buffer from [[#CreateSmmuSpace]] can't be reused by another endpoint with PostBufferAsync.

Line 697:

==== BatchBufferAsync ====

Takes 3 input u32s ('''urbCount''', '''unk1''', and '''unk2'''), an input u64 '''buffer''' and u64 '''id''', and a type-0x5 ([3.0.0+] type-0x21) input buffer, returns an output u32 '''xferId'''.

Takes 3 input u32s ('''urbCount''', '''unk1''', and '''unk2'''), an input u64 '''buffer''' and u64 '''Id''', and a type-0x5 ([3.0.0+] type-0x21) input buffer, returns an output u32 '''xferId'''.

Where '''id''' is the same as [[#PostBufferAsync_2|#PostBufferAsync]].

Where '''Id''' is the same as [[#PostBufferAsync_2|#PostBufferAsync]].

This uses the same func internally as [[#PostBufferAsync_2|#PostBufferAsync]] except multiple urbs are specified by the user: the input buffer contains an array of u32s for the size of each urb, where '''urbCount''' is the total number of entries in this array. With [[#PostBufferAsync_2|#PostBufferAsync]] the last 2 params passed to the internal func are hard-coded to 0, while with this command it's '''unk1''' and '''unk2'''.

Line 1,061:

| 0xC || 0x4 || transferredSize

|-

| 0x10 || 0x8? || ?

| 0x10 || 0x8 || [[#PostBufferAsync_2|Id]]

|}

@@ Line 678: / Line 678: @@
 ==== PostBufferAsync ====
-Takes an input u32 '''size''', an input u64 '''buffer''', and an input u64 '''id''', returns an output u32 '''xferId'''.
+Takes an input u32 '''size''', an input u64 '''buffer''', and an input u64 '''Id''', returns an output u32 '''xferId'''.
 Starts a data transfer with a single urb.
-The official sw func which uses this cmd and handles waiting on the Event passes value 0 for the '''id'''. The async version which exposes this cmd directly uses '''id''' from user input - the user funcs pass a value starting at 0 then increment it each time (for sending multiple requests at once, with 0 for the first request in this set of requests).
+The official sw func which uses this cmd and handles waiting on the Event passes value 0 for the '''Id'''. The async version which exposes this cmd directly uses '''Id''' from user input - the user funcs pass a value starting at 0 then increment it each time (for sending multiple requests at once, with 0 for the first request in this set of requests). Note that '''Id''' can be arbitrary, the sysmodule doesn't require a certain range for this.
 On newer sysvers the state fields setup by [[#CreateSmmuSpace]] are compared with '''buffer'''. If it's within bounds of the SmmuSpace (which won't be the case when [[#CreateSmmuSpace]] wasn't used), it will then verify that buffer+buffer_size is within bounds throwing an error otherwise. Note that a buffer from [[#CreateSmmuSpace]] can't be reused by another endpoint with PostBufferAsync.
@@ Line 697: / Line 697: @@
 ==== BatchBufferAsync ====
-Takes 3 input u32s ('''urbCount''', '''unk1''', and '''unk2'''), an input u64 '''buffer''' and u64 '''id''', and a type-0x5 ([3.0.0+] type-0x21) input buffer, returns an output u32 '''xferId'''.
+Takes 3 input u32s ('''urbCount''', '''unk1''', and '''unk2'''), an input u64 '''buffer''' and u64 '''Id''', and a type-0x5 ([3.0.0+] type-0x21) input buffer, returns an output u32 '''xferId'''.
-Where '''id''' is the same as [[#PostBufferAsync_2|#PostBufferAsync]].
+Where '''Id''' is the same as [[#PostBufferAsync_2|#PostBufferAsync]].
 This uses the same func internally as [[#PostBufferAsync_2|#PostBufferAsync]] except multiple urbs are specified by the user: the input buffer contains an array of u32s for the size of each urb, where '''urbCount''' is the total number of entries in this array. With [[#PostBufferAsync_2|#PostBufferAsync]] the last 2 params passed to the internal func are hard-coded to 0, while with this command it's '''unk1''' and '''unk2'''.
@@ Line 1,061: / Line 1,061: @@
 | 0xC || 0x4 || transferredSize
 |-
-| 0x10 || 0x8? || ?
+| 0x10 || 0x8 || [[#PostBufferAsync_2|Id]]
 |}