I'm dying to know too, but did not want harass davebaol.@[member='davebaol']
Hey man, how are you? much to do nowadays?
I'm just a little curious as to what is happening and what is in focus with the d2x cIOS development nowadays.
Maybe you could tease us a bit with some information about the progress.
.
Awesome!
This is what the end user can enjoyAwesome!
I read the changelog, but don't know what everything means.
What do you consider are the biggest changes in this release, in layman terms?
I see. Thanks.
Wait, so that means no more random freezing? =Dok finally I managed to make it work without any random crash.
I'm talking about the new ehci module with interrupts that I developed with rodries in june/july.
It has been abandoned since games crashed after playing for some minutes and we were not able to fix it at that time.
But I recently found out that the ehci module works properly after removing some non essential modules picked at random.
OMFG how many nights wasted in vain in hunting a bug that does not exist.
In fact this likely means that there are too many threads and problems arise when extending the execution time of the interrupt procedure.
So I removed the fat module by embedding fat support directly into the fs plugin, i.e. one less thread.
Also, I replaced the thread which makes the drive led blink on fat write access with a synchronous procedure which turns the led on and off respectively before and after writing sectors.
And now without those 2 threads the issue has disappeared.
Good news!!ok finally I managed to make it work without any random crash.
I'm talking about the new ehci module with interrupts that I developed with rodries in june/july.
It has been abandoned since games crashed after playing for some minutes and we were not able to fix it at that time.
But I recently found out that the ehci module works properly after removing some non essential modules picked at random.
OMFG how many nights wasted in vain in hunting a bug that does not exist.
In fact this likely means that there are too many threads and problems arise when extending the execution time of the interrupt procedure.
So I removed the fat module by embedding fat support directly into the fs plugin, i.e. one less thread.
Also, I replaced the thread which makes the drive led blink on fat write access with a synchronous procedure which turns the led on and off respectively before and after writing sectors.
And now without those 2 threads the issue has disappeared.
Niiiiiceok finally I managed to make it work without any random crash.
I'm talking about the new ehci module with interrupts that I developed with rodries in june/july.
It has been abandoned since games crashed after playing for some minutes and we were not able to fix it at that time.
But I recently found out that the ehci module works properly after removing some non essential modules picked at random.
OMFG how many nights wasted in vain in hunting a bug that does not exist.
In fact this likely means that there are too many threads and problems arise when extending the execution time of the interrupt procedure.
So I removed the fat module by embedding fat support directly into the fs plugin, i.e. one less thread.
Also, I replaced the thread which makes the drive led blink on fat write access with a synchronous procedure which turns the led on and off respectively before and after writing sectors.
And now without those 2 threads the issue has disappeared.
so what I understand we all can enjoy this in the next new beta, and probably very soon.
Yep. That's exactly how I would have done it.ok finally I managed to make it work without any random crash.
I'm talking about the new ehci module with interrupts that I developed with rodries in june/july.
It has been abandoned since games crashed after playing for some minutes and we were not able to fix it at that time.
But I recently found out that the ehci module works properly after removing some non essential modules picked at random.
OMFG how many nights wasted in vain in hunting a bug that does not exist.
In fact this likely means that there are too many threads and problems arise when extending the execution time of the interrupt procedure.
So I removed the fat module by embedding fat support directly into the fs plugin, i.e. one less thread.
Also, I replaced the thread which makes the drive led blink on fat write access with a synchronous procedure which turns the led on and off respectively before and after writing sectors.
And now without those 2 threads the issue has disappeared.
Then you could have told me before.Yep. That's exactly how I would have done it.ok finally I managed to make it work without any random crash.
I'm talking about the new ehci module with interrupts that I developed with rodries in june/july.
It has been abandoned since games crashed after playing for some minutes and we were not able to fix it at that time.
But I recently found out that the ehci module works properly after removing some non essential modules picked at random.
OMFG how many nights wasted in vain in hunting a bug that does not exist.
In fact this likely means that there are too many threads and problems arise when extending the execution time of the interrupt procedure.
So I removed the fat module by embedding fat support directly into the fs plugin, i.e. one less thread.
Also, I replaced the thread which makes the drive led blink on fat write access with a synchronous procedure which turns the led on and off respectively before and after writing sectors.
And now without those 2 threads the issue has disappeared.
I did not want to steal the spotlight.Then you could have told me before.
Xdqwerty
@
CameronCataclysm:
@
Xdqwerty:
@
Xdqwerty:
