-
Notifications
You must be signed in to change notification settings - Fork 134
Core(TM) i7-7567U #400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Most data appear accurate but I'm not sure about IMC timings. Googleing But CoreFreq has decoded a Can you please check and post the configured timings from BIOS or |
BIOS reports CL 15 ( |
Got it from "7th Generation Intel® Processor Families for U/Y Platforms and 8th Generation Intel® Processor Family for U Quad Core Datasheet, Volume 2 of 2" Order Number: 334662-005
Whenever I have clearly detected this architecture, I just have to add |
I have checked and down to Skylake I'm supposed to also add |
I have Coffee Lake-U (i3-8109U). Other CPUs I have belong to other architectures such as i5-5200U and i5-7600. |
Yes please, could you post the output of |
For my current Tiger Lake Mobile timings are the same with datasheet, |
Using latest commit, you can edit and change function Line 4393 in 0116ad7
void SKL_IMC(RO(SHM_STRUCT) *RO(Shm), RO(PROC) *RO(Proc))
{
TIMING(mc, cha).tCL = 5
+ RO(Proc)->Uncore.MC[mc].Channel[cha].SKL.ODT.tCL;
TIMING(mc, cha).tRCD = 5
+ RO(Proc)->Uncore.MC[mc].Channel[cha].SKL.Timing.tRP;
TIMING(mc, cha).tRP = 5
+ RO(Proc)->Uncore.MC[mc].Channel[cha].SKL.Timing.tRP;
TIMING(mc, cha).tRAS = 7
+ RO(Proc)->Uncore.MC[mc].Channel[cha].SKL.Timing.tRAS;
} |
@svmlegacy Hello, |
Thanks, now it shows:
|
Thank you. I'm OK to change But Line 3688 in 0116ad7
To go further with source code:
|
@JohnAZoidberg Hello, Based on latest develop branch, could you please post the output of your ... and check if the DDR timings are the same with BIOS (preferably screenshots of it) ? |
Unsolved: regression risk on all Skylake decoders : Need large hardware scale testings : Postponed |
On 1.93.1:
The text was updated successfully, but these errors were encountered: