Davebaol, do you know much different or what was changed between your mod and Xabby's mod? Just wondering.davebaol said:Xabby's mod works for me.
Tested with wiiflow, gx, and cfg

That's correct!XFlak said:xabby666's EHCI mod is superior to davebaol's, correct?
And this is the only module that needs to replace any of wanin's official rev 21 modules to fix the controller lag AND the wiiflow sync issue, correct?

Viva la google translate, yeah better post the source code..davebaol said:That's correct!XFlak said:xabby666's EHCI mod is superior to davebaol's, correct?
And this is the only module that needs to replace any of wanin's official rev 21 modules to fix the controller lag AND the wiiflow sync issue, correct?
EDIT:
xabby, mi hai battuto sul tempo.
PS: Siamo troppo forti!!!![]()
EDIT 2:
Posta i sorgenti prima che inizino a rompere.![]()

if you are able to share a better EHCI module, I think I speak for everyone when I say we'd be more than happy to use that instead. I bet it would only take all of 10 minutes for you to do... so why not?tueidj said:So you're just going to ignore me and call os_restart_timer with 2 arguments, which could potentially crash IOS?

I'm confused now, if i read back, i see that davebaol looked at the rev 19 EHCI and corrected the REV21 EHCI.tueidj said:So you're just going to ignore me and call os_restart_timer with 2 arguments, which could potentially crash IOS?

I agree too, and i read that part too, but i thought rev 19 EHCI was not used anymore, so really my question is: does rev 21 EHCI has the same amount of os_restart_timer arguments as rev 19?xfcrowman said:I believe that tuedj is saying that os_restart_timer needs to be called with 3 arguments, rather than 2 arguments which is what the source code is currently doing. I think that someone else in this thread (can't remember who, sorry) tried doing this earlier, but it failed because they didn't use the correct values.
I agree with Xflak that this correction to the source code is probably a simple thing to fix for someone as experienced as tuedj, and that if he can help in any way that would be great.
EDIT: sorry for the double post.

And I agree too.xfcrowman said:I believe that tuedj is saying that os_restart_timer needs to be called with 3 arguments, rather than 2 arguments which is what the source code is currently doing. I think that someone else in this thread (can't remember who, sorry) tried doing this earlier, but it failed because they didn't use the correct values.
Yeah I confirm. It was me.
Anyway all hermes cios and waninkoko cios till rev20 excluded call os_restart_timer with just 2 arguments and nobody cares so far since it seems to be harmless.
But I believe that if waninkoko added the 3rd argument (actually the 2nd in positional order) there must be a reason.
QUOTE(xfcrowman @ Jan 28 2011, 08:00 PM) I agree with Xflak that this correction to the source code is probably a simple thing to fix for someone as experienced as tuedj, and that if he can help in any way that would be great.
No XFlak, in rev20 and rev21 os_restart_timer is called with 3 arguments.XFlak said:@Etheboss, I haven't actually looked at the source personally, but from what I gather from this thread, both rev21 and rev19's EHCI module's os_restart_timer is called with 2 arguments, when instead it should be called using 3 arguments.

So if xabby666 modded the rev21 EHCI module (which seems very logical to me), os_restart_timer is called with 3 arguments and all is good.davebaol said:No XFlak, in rev20 and rev21 os_restart_timer is called with 3 arguments.XFlak said:@Etheboss, I haven't actually looked at the source personally, but from what I gather from this thread, both rev21 and rev19's EHCI module's os_restart_timer is called with 2 arguments, when instead it should be called using 3 arguments.
All other revs use just 2 args.