I see multiple OSes request 0x10 bytes for volume range.
This sounds like something that has to be tested in detail on all relevant
operating systems. What is so special that you can’t use one range and work
it out in firmware?
Børge
On Wednesday, December 5, 2018, Tim Roberts <timr@xxxxxxxxx> wrote:
Kevin Ng wrote:
Hi, I am new here. Tried searching through the list and unable to find
some similar to the above.
So I am trying to specify a multiple volume range control with different
volume resolution for each volume range.
...
I understand what is required to send back the feature unit volume range
request command from the host PC (Windows 10/MacOS). But the problem is the
host PC only allow 8 bytes of data length to be sent back for the volume
range command. Anyone have any idea how to implement this?
Interesting. I would expect it to make one request of 8 bytes, then make
another request based on the wNumSubRanges you returned. That's the usual
protocol for variable-length layouts. Do you not see the second request?
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
