[Freemint-list] XHDOSLimits

[Miro Kropáček]

On 4 October 2016 at 18:38, Miro Kropáček <miro.kropacek at gmail.com> wrote:

> Just to correct this statement -- it seems that I've discovered the
> culprit: HD Driver actually expect *explicit call* to XHDOSLimits() so it
> can adjust it to the new limits (instead of reading them). Uwe claims this
> is the way the XHDI protocol works, I have no clue. I asked him to join
> this thread as he might get better answers here.
>

Hmm, found some time to look into this further. It seems that FreeMiNT
violates XHDI at least starting with with version 1.30:

*As a required functionality starting with XHDI release 1.30 a driver shall
retrieve limit values from previously started XHDI drivers, if these exist.
When a limit is changed, this information then shall be passed through to
other XHDI drivers. *

So this basically means that FreeMiNT should query the old value, compare
with its own (like # of possible drives changing from 16 to 32) and call
the other drivers' function.

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20161005/8ab42e16/attachment.html