bkeys has quit [Remote host closed the connection]
bkeys has joined #fedora-riscv
iooi has joined #fedora-riscv
iooi_ has joined #fedora-riscv
iooi has quit [Ping timeout: 240 seconds]
iooi_ is now known as iooi
iooi has quit [Quit: iooi]
bkircher has joined #fedora-riscv
<davidlt[m]>
Morning
<davidlt[m]>
The patches to support LoadFile2 (IIRC) are not yet merged.
<davidlt[m]>
I don't actually remember what's the current status, but it definitely was blocked on 2.06 being released.
<davidlt[m]>
The last patchset was posted: [PATCH v2 0/7] Add LoadFile2 and riscv Linux loader, Nikita Ermakov, 2021/06/02
<davidlt[m]>
In July it got a reply from Atish.
<davidlt[m]>
From what I understand more changes are needed, but in general things work, it's just we don't yet have the final proper implementation for it.
<davidlt[m]>
@bke
<davidlt[m]>
bkeys: make sure you board is stable at 1.4GHz, run some math benchmarks or something for N hours
jcajka has joined #fedora-riscv
<pierce>
Is there a way to determine what frequency my CPU is running at?
<davidlt[m]>
lmbench can calculate that before benchmarks are run
<pierce>
What work needs to be done for it to appear in cpuinfo or lscpu?
<davidlt[m]>
I think lscpu does show it if opptable is defined
<davidlt[m]>
but FU540 and FU740 doesn't do DVFS
<davidlt[m]>
so there might not be a point to have opptable defined in DT
<pierce>
My D1 nor BeagpeV do not show it either unfortunately
<pierce>
Not sure if qemu even displays it
<davidlt[m]>
Nothing displays it, not really that useful information
<davidlt[m]>
especially if the system is DVFS capable
<davidlt[m]>
MHz/GHz/whatever is not really useful information on which your applications would act
<davidlt[m]>
If you really need to know the freq, calculate it, but I am not sure it will be OK in a more complicated systems with DVFS and power management
<davidlt[m]>
I think lscpu shows min - max range based on opp table (if one is defined in the DT)
<davidlt[m]>
There is default clock in DT too for FU540 and FU740 (that's within U-Boot DT overlay, not what's passed to the kernel)
<davidlt[m]>
that basically tells the default clock to begin with
<davidlt[m]>
if CPUFreq is operational the current clock is available under sysfs knob
<davidlt[m]>
that would be something like: /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
<rwmjones>
morning
<pierce>
* My D1 nor BeagleV do not show it either unfortunately
<jimwilson>
pierce, I use "perf stat /bin/ls" to get frequency, but assumes you have perf, this does work on freedom-u-sdk
<pierce>
Nice, I can see it now. Now I can confirm that the overclock firmware from the SiFive forums is actually in effect. And which one is actually flashed.