Re: USb 3/4+ Future USB 8,000Hz -to- 24,000Hz polling rate
Posted: 25 Oct 2020, 22:04
dir€ctx
Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
ROTFL about Dye-Euro-Ex but fortunately, only 6 mentions on Google, so this hasn't established a derogatory meaning, so I put this squarely in the "Humor" department. You can use your original account instead. No, Icognito & VPNs won't hide you.
All good stuff, but don't bother. It's not even that far yet, not even unlockable in a build you can download to the computer.schizobeyondpills wrote: ↑25 Oct 2020, 21:59http://www.mrtweaks.com/reg10.htm
this is both on topic and relevant to secret NDA stuff, i hope there's more documented and actually without any hidden things (like this reg i posted being multiplied by 100 inside the driver) tweaks possible for new unlocked 1000Hz build, hope you request this with NDA guys at Microsoft.
Dude, kudos to your efforts man. Can't be easy "convincing" the establishment.Chief Blur Buster wrote: ↑25 Oct 2020, 22:12However, the discussions started when Microsoft emailed me from my public feedback report, also linked from Windows 512Hz limitation, and took more than a year of patient back and fourth discussions/negotations/buyins/etc.
Thanks. Sometimes I have to ELI5 some Blur Busters stuff at simple language, but that's intentional at Blur Busters Media. Some big corporate departments can't handle Blur Busters Laboratoryspeak, so I switch to ELI5 mode. It's totally different from how I naturally write in forums.
Wow, even updating & improving RTT. Nice!Chief Blur Buster wrote: ↑26 Oct 2020, 03:58XEP-0301 specification work for XMPP extension).
Then the right engineers become interested, and start to realize how complex the Pandora Box is, and some department purchases an esports monitor as part of QA testing, and so on. Many dominoes involved.
Someday I need to create 1-minute YouTube easy explainer clips (but my being born deaf is somewhat of a barrier to that). I'm working around some solutions for that, but it's on Valve Time.
What does that have to do with 8K polling rate?schizobeyondpills wrote: ↑17 Oct 2020, 08:32Windows kernel timer has a limit of 0.5 ms interrupt intervals.
Percentage is going to be lower than that I think but just like you generally wouldn't pair a top end graphics card with a low end CPU, 8K isn't for everyone and some programs may choke.schizobeyondpills wrote: ↑17 Oct 2020, 08:32why do you believe you can plug anything of 8000hz or more in 99.99999% of systems and expect no perf degradation? and think it will work properly.
No, 40C is maximum recommended ambient temperature, the temperature of the air near the sensor while absolute ambient temperature is likely 15C higher than that. USB polling will be taken care of by the MCU which might be a LPC11U3... which has an ambient specification of -40C to 85C and a maximum junction temperature of 150C.schizobeyondpills wrote: ↑17 Oct 2020, 08:32pixart sensors per their specsheets have a temperature operating temp of 40deg c, thats junction inside not on top where its cooler.
Temperature is a result of power dissipation and dynamic power is proportional as voltage is constant.
This is the system timer and operates from around 0.5ms to 15.6ms, it is not windows time.schizobeyondpills wrote: ↑25 Oct 2020, 14:51windows time (not timer) source occurs at 0.5ms intervals.
Would imagine just parse the PCI BAR similar to Intel XHCI
The IMOD register/mechanism is specific to Intel's implementation AFAIK.
The sensor rate is only slightly higher than earlier mice, 16 KHz raised to 20 KHz. That won’t do the heat increase of the 1000Hz:8000Hz differential, so this is not a weak link.O_O wrote: ↑27 Oct 2020, 07:51No, 40C is maximum recommended ambient temperature, the temperature of the air near the sensor while absolute ambient temperature is likely 15C higher than that.schizobeyondpills wrote: ↑17 Oct 2020, 08:32pixart sensors per their specsheets have a temperature operating temp of 40deg c, thats junction inside not on top where its cooler.
That’s definitely true. USB poll rate processing in a separate chip, and there’s been more than 15 years of Moore’s Law on USB processing.
its an indicator that windows is not engineered for such high performance devices, its not hard to see or figure out, where do you have problems with? do you need further help? RTC and HPET allow far lower interrupt intervals than 0.5ms but Windows does not implement them intentionally due to being very badly engineered outdated kernel which is not optimized to handle such high freq interrupts.O_O wrote: ↑27 Oct 2020, 07:51What does that have to do with 8K polling rate?schizobeyondpills wrote: ↑17 Oct 2020, 08:32Windows kernel timer has a limit of 0.5 ms interrupt intervals.
Code: Select all
Periodic Interrupt
==================
The frequency of this interrupt is programmable from 2 to 8192 per
second. To use this type of interrupt first set RS (Rate Select)
bits in Status Register A to the required value:
RS Int/sec Period
3210 - -
0000 none none
0001 256 3.90625 ms
0010 128 7.8125 ms
0011 8192 122.070 Micros
0100 4096 244.141 Micros
0101 2048 488.281 Micros
0110 1024 976.562 Micros
0111 512 1.93125 ms
1000 256 3.90625 ms
1001 128 7.8125 ms
1010 64 15.625 ms
1011 32 31.25 ms
1100 16 62.50 ms
1101 8 125.0 ms
1110 4 250.0 ms
1111 2 500.0 ms
>Percentage is going to be lower than that I think but just like you generally wouldn't pair a top end graphics card with a low end CPU, 8K isn't for everyone and some programs may choke."Rate" is the divider setting. If you select a rate of 1 or 2, the RTC will have problems and "roll over" so that it generates interrupts of .81 mS and 3.91 mS, rather than the expected interrupts of 61.0 uS or 30.5 uS. So, the fastest rate you can select is 3. This will generate interrupts of 8 kHz or 122 uS.
^ from Windows Internals. try again pleaseThe system’s clock interval timer is probably the most important device on a Windows machine, as evidenced by its high IRQL value (CLOCK_LEVEL) and due to the critical nature of the work it is responsible for. Without this interrupt, Windows would lose track of time, causing erroneous results in calculations of uptime and clock time—and worse, causing timers not to expire anymore and threads never to lose their quantum anymore. Windows would also not be a preemptive operating system, and unless the current running thread yielded the CPU, critical background tasks and scheduling could never occur on a given processor.
No problem finding IMOD registers for my Asmedia USB3.1. Has one type C and one type A port and no problem running low speed USB mouse directly on Type A connector however I usually have the device disabled via BIOS setup.