ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
Pali has quit [Ping timeout: 272 seconds]
XV8 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
XV8 has joined #armlinux
apritzel has quit [Ping timeout: 256 seconds]
archetech has joined #armlinux
sakman has joined #armlinux
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #armlinux
tachoknight has joined #armlinux
tachoknight has quit [Ping timeout: 240 seconds]
amitk has joined #armlinux
sakman has quit [Quit: Leaving]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
toastloop has joined #armlinux
scosu has quit [Quit: No Ping reply in 180 seconds.]
scosu has joined #armlinux
cbeznea has joined #armlinux
apritzel has joined #armlinux
monstr has joined #armlinux
iivanov has joined #armlinux
<krzk>
olofj: arnd: Hi, my Samsung pulls (Samsung pinctrl, Tesla, usual Samsung) seem to be still pending. Any comments on these?
<krzk>
arnd: olofj: if I need to re-do something, I should do it soon.
<arnd>
krzk: I'm late with the feature pull requests again, haven't pulled anything else, but yours is at the start of the queue
<arnd>
should be able to do my first pass today, which will include it
<krzk>
ok :)
headless has joined #armlinux
matthias_bgg has joined #armlinux
matthias_bgg has quit [Remote host closed the connection]
frieder has quit [Read error: Connection reset by peer]
frieder has joined #armlinux
nsaenz has joined #armlinux
toastloop has quit [Quit: Leaving]
toastloop has joined #armlinux
wolfshappen has quit [Ping timeout: 272 seconds]
wolfshappen has joined #armlinux
tom5760 has quit [Ping timeout: 240 seconds]
tom5760 has joined #armlinux
toastloop has left #armlinux [Leaving]
apritzel has quit [Ping timeout: 272 seconds]
mcoquelin has quit [Quit: Leaving]
frieder has quit [Ping timeout: 272 seconds]
frieder has joined #armlinux
apritzel has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
headless has quit [Quit: Konversation terminated!]
prabhakarlad has joined #armlinux
Misotauros has joined #armlinux
atorgue has joined #armlinux
nsaenz has quit [Quit: Leaving]
nsaenz has joined #armlinux
shailangsa has quit [Remote host closed the connection]
Amit_T has quit [Ping timeout: 256 seconds]
Amit_T has joined #armlinux
atorgue has quit [Quit: Client closed]
nsaenz has quit [Remote host closed the connection]
headless has joined #armlinux
nsaenz has joined #armlinux
atorgue has joined #armlinux
Misotauros has quit [Ping timeout: 272 seconds]
archetech has quit [Quit: Konversation terminated!]
prabhakarlad has quit [Quit: Client closed]
torez has joined #armlinux
headless has quit [Ping timeout: 256 seconds]
headless has joined #armlinux
shawnguo has joined #armlinux
headless has quit [Client Quit]
<mwalle>
aren't the min and max voltages of all the regulators the ones which can be set without breaking the board?
* mwalle
is looking at arch/arm64/boot/dts/freescale/imx8mm-evk.dtsi
<mwalle>
and the settings there doesn't make much sense
<mwalle>
*dont
<broonie>
mwalle: Yes.
<broonie>
That's the point of the machine constraints.
<broonie>
People do have a distressing tendency to just put whatever the maximum range that the regulator supports is in there regardless of what's safe/useful on the board though.
<broonie>
Ugh, looking at that why is BUCK3 in the code BUCK5 in the datasheet !?
<broonie>
mwalle: As a rule of thunb if a regulator has no consumers mapped it probably shouldn't have a range specified at all.
<mwalle>
broonie: yeah, I don't know what thats with the BUCK3/5 and the others, but according to the schematics, nothing fits together :(
<mwalle>
broonie: I'm still puzzled how's setting the operating voltage of the dcdc converter though, the bootloader? and linux just ignores it?
<broonie>
There will likely be some hardware default from power on, firmware may or may not set something while it runs.
<broonie>
Linux won't touch the voltage unless explicitly told it's safe to do so, if it's been given a voltage range it will at least bring the voltage into that range.
<mwalle>
broonie: ok thanks
russ has quit [Ping timeout: 256 seconds]
vigneshr has joined #armlinux
shailangsa has joined #armlinux
russ has joined #armlinux
mcoquelin has joined #armlinux
Misotauros has joined #armlinux
frieder has quit [Ping timeout: 256 seconds]
XV8 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
XV8 has joined #armlinux
Tokamak has joined #armlinux
tom5760 has quit [Remote host closed the connection]
tom5760 has joined #armlinux
headless has joined #armlinux
tchebb_ has quit [Ping timeout: 256 seconds]
tom5760 has quit [Remote host closed the connection]
tom5760 has joined #armlinux
Misotauros has quit [Ping timeout: 256 seconds]
nsaenz has quit [Remote host closed the connection]
XV8 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wens has quit [Ping timeout: 250 seconds]
XV8 has joined #armlinux
wens has joined #armlinux
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Misotauros has joined #armlinux
monstr has quit [Remote host closed the connection]
apritzel has quit [Ping timeout: 240 seconds]
dliviu has quit [Ping timeout: 256 seconds]
dliviu has joined #armlinux
Amit_T has quit [Remote host closed the connection]
headless has quit [Quit: Konversation terminated!]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
djrscally has joined #armlinux
aposm has joined #armlinux
torez has quit [Quit: torez]
<amstan>
anyone still using the samsung exynos arm32 chromebooks? what's the best way one can boot more than 8MB kernels, leming's wondering
<amstan>
jwerner: maybe you know a quick trick for this, even if it means recompiling the firmware
<amstan>
leming: i guess uboot might be an option if this is just for the personal setup?
<amstan>
kexec with an older kernel?
<leming>
that might be the route.. chainload with u-boot
<amstan>
leming: i think you had those uboot packages at some point, but when i showed you the depthcharge kpart stuff you gave up on it
<leming>
i have a one for veyron, and an unreleased one for peach, can't remember at all where i left that one
<leming>
they're both building a kpart the same as with the kernel
<amstan>
alpernebbi: you mentioned CONFIG_KERNEL_SIZE to me in the other channel a couple of days ago
tachoknight has joined #armlinux
<alpernebbi>
yeah
<amstan>
alpernebbi: did you ever use any workarounds for it?
<alpernebbi>
I'm trying to automate the kpart image thing in u-boot builds, but not sure how good mainline u-boot is with the old boards: https://github.com/alpernebbi/u-boot/releases
<alpernebbi>
I also found old kpart builds online for peach-pi, peach-pit, snow, nyan-big
<alpernebbi>
also have one for spring, didn't notice when writing here just now
<amstan>
so this is a uboot that fits inside the kpart and lets you boot something else?
<alpernebbi>
yep
<amstan>
RW_LEGACY payload is less desired I guess?
<alpernebbi>
it's more resilient as you'd write it to SPI
<alpernebbi>
but kpart did work better on gru-kevin