Jones42 has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
Jones42 has joined #u-boot
Jones42 has quit [Ping timeout: 248 seconds]
zibolo has quit [Ping timeout: 265 seconds]
zibolo has joined #u-boot
mckoan|away has quit [Read error: Connection reset by peer]
mckoan|away has joined #u-boot
mmu_man has quit [Ping timeout: 272 seconds]
Daanct12 has joined #u-boot
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #u-boot
rockosov has quit [Ping timeout: 272 seconds]
rockosov has joined #u-boot
goliath has quit [Quit: SIGSEGV]
flyback has quit [Ping timeout: 245 seconds]
flyback has joined #u-boot
tlwoerner has quit [Ping timeout: 268 seconds]
tlwoerner has joined #u-boot
dsimic has quit [Ping timeout: 265 seconds]
dsimic has joined #u-boot
vardhan_ has joined #u-boot
Daanct12 has quit [Quit: WeeChat 4.5.2]
clamor has joined #u-boot
sng has joined #u-boot
sng has quit [Changing host]
sng has joined #u-boot
Daanct12 has joined #u-boot
sng has quit [Ping timeout: 252 seconds]
Daanct12 has quit [Ping timeout: 252 seconds]
Daaanct12 has joined #u-boot
<shadow>
uh... so I need help to understand mechanics of how the CPU frequency on StarFive JH7110 is established? more theory of operation and then also how I can test with U-Boot if some ideas I want to try are stable or not for the board I have using JH7110
sng has joined #u-boot
<shadow>
the patch set I sent to LKML which upstreams changes from U-Boot resulted in feedback that I don't 100% understand, and I only have the most basic of troubleshooting and code skills
jclsn has quit [Quit: WeeChat 4.5.1]
<clamor>
shadow: classic LKML
sally_ has joined #u-boot
sally has quit [Ping timeout: 245 seconds]
sng has quit [Ping timeout: 248 seconds]
<shadow>
clamor: I'm open to learning. I'm a ski instructor, not a career programmer. I want to do whatever I'm capable and have time for to help along HomeAssistant adopting RISC-V as a supported architecture, as I want eventually for there to be more options on the market than x86 and ARM
<shadow>
along the way is this interesting diversion of U-Boot, Linux Kernel, Debian, AlpineLinux, and (recently) Rocky Linux
clamor has quit [Ping timeout: 268 seconds]
clamor has joined #u-boot
sng has joined #u-boot
sng has quit [Changing host]
sng has joined #u-boot
<clamor>
shadow: I share and understand your pain
sng has quit [Ping timeout: 252 seconds]
sng has joined #u-boot
<clamor>
shadow: personally, the worst part of interacting with lkml is a schema, the code part reviews usually are quite useful and helpful (not without random weirdoes with their odd requests of course).
<shadow>
yeah it's been good except from my point of view I'm a technician, I know very well how to test "thing works when power cord is plugged into working electrical outlet, does not work when unplugged" and I'm being asked to describe why it works
<shadow>
I don't know. It just does.
sng has quit [Client Quit]
<shadow>
for the CPU frequency stuff there's this ask for 1.5GHz (which needs increased voltage) and I've observed it causes overheating when you effectively overclock the thing
<shadow>
okay so then, some mention of a divider, I'm not even sure what that is exactly
<clamor>
shadow: the best way to learn how particular arch works is usually to read trm for it. That should give you some understanding how stuff works.
<clamor>
div2 throttling on overheating in a passive cooled system?
<shadow>
something like this. The AXP15060 PMIC allegedly provides 0.9Vdc from power on unless given some other configuration, and the JH7110 CPU (from ... I don't know how) somehow is default to 1.0GHz if you don't configure ... something(!?) ; and according to StarFive people the JH7110 is stable at 0.8Vdc+ for 1.0GHz (and lesser) div1; for div1 1.5GHz it needs a bump to 1.04Vdc to be stable
<clamor>
You need trm
<shadow>
the posture from StarFive people is that 1.5GHz is golden and we should keep that for Linux and (by extension because of OF_UPSTREAM effort I'm trying to sync up with my series) that U-Boot should also run this thing at 1.5GHz
enok has joined #u-boot
<clamor>
1.5ghz in uboot seems excessive
<shadow>
yes.
<shadow>
the other way I'm thinking of this having no experience or technical background in PLL's and such is that the TRM says the thing should possibly be able to be set with a root frequency of 3.0GHz ... so ... what about power on, set div3 to make me happy, then change root frequency to 3.0GHz and denylist div1
sng has joined #u-boot
sng has quit [Changing host]
sng has joined #u-boot
<shadow>
I just don't know how to test it and save people the bother of some dummy like me asking about it if it will be a failure
<clamor>
Don't bother about that. It is better to ask then not to
sng_ has joined #u-boot
sng_ has quit [Client Quit]
<clamor>
Always ask for an explicit description of what exactly the maintainer wants from you since if you do not fully understand what you should do, you will have even more trouble and rage towards your efforts
<shadow>
thanks
<shadow>
I wish there was more expertise I could bring to the discussion