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
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
iivanov has quit [Ping timeout: 250 seconds]
iivanov has joined #armlinux
LeSpocky has quit [Ping timeout: 240 seconds]
LeSpocky has joined #armlinux
Drek45 has quit [Ping timeout: 240 seconds]
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 248 seconds]
iivanov has quit [Ping timeout: 252 seconds]
amitk has joined #armlinux
iivanov has joined #armlinux
tudorel has joined #armlinux
monstr has joined #armlinux
milkylainen_76 has joined #armlinux
milkylainen_76 has quit [Client Quit]
Nact has quit [Quit: Konversation terminated!]
apritzel has joined #armlinux
<arnd>
alyssa: ioremap_cache() is almost never correct, I think memremap() is what you want here.
<arnd>
kmap() and vmap() require a struct page, so they don't work if the memory is outside of the kernel's memblocks
tudorel has quit [Ping timeout: 250 seconds]
Drek45 has joined #armlinux
Drek45 has quit [Client Quit]
bps has quit [Ping timeout: 240 seconds]
bps has joined #armlinux
bps has joined #armlinux
bps has quit [Changing host]
Pali has joined #armlinux
<maz>
yup, memremap definitely looks like the best option if the memory is outside of the memblock range. ioremap_cache may have similar results on arm64, but that's hardly portable to another architecture.
iivanov has quit [Quit: Leaving...]
scosu has joined #armlinux
alpernebbi has joined #armlinux
iivanov has joined #armlinux
djrscally has joined #armlinux
tre has joined #armlinux
krzk_ is now known as krzk
krzk is now known as Guest320
audgirka has joined #armlinux
Guest320 is now known as krzk
eduardas has joined #armlinux
apritzel_ has joined #armlinux
apritzel__ has joined #armlinux
apritzel_ has quit [Ping timeout: 252 seconds]
apritzel__ has quit [Ping timeout: 248 seconds]
apritzel__ has joined #armlinux
apritzel__ has quit [Ping timeout: 252 seconds]
apritzel has quit [Ping timeout: 248 seconds]
CrashTestDummy3 has joined #armlinux
prabhakarlad has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 250 seconds]
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
shenki has quit [Ping timeout: 240 seconds]
shenki has joined #armlinux
CrashTestDummy2 has joined #armlinux
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
robinp__ has joined #armlinux
robinp_ has quit [Ping timeout: 250 seconds]
<alyssa>
arnd: memremap, okay, thank you :)
<alyssa>
and there's a devm_ version, even more promising
<alyssa>
maz: part of me wonders what the point of portability is for a platform driver, then again 5 years down the line we could easily see Apple Architecture™ SoCs that still use DART 🤷
<maz>
alyssa: you'd be surprised how much common IP gets copy-pasted from one SoC to another. the UART on M1 is a good example of that.
<jn>
some companies switched their SoCs from MIPS to ARM and/or back, while retaining most of the peripherals
<jn>
and then, as maz says, there's the cross-vendor sharing
<alyssa>
nod
<jn>
(wouldn't be surprised to find an SoC linage that goes MIPS->ARM->RISC-V)
<alyssa>
come to think of it even mali has been used with non-arm soc's
alyssa has quit [Remote host closed the connection]
<sven>
alyssa: DART has (with slight variations) been around since 2013 or so. wouldn't surprise me if it's still around (with more variations) 5-10 years from now in whatever architecture apple uses by then :)
audgirka has quit [Quit: Leaving]
alyssa has joined #armlinux
tre has quit [Remote host closed the connection]
<arnd>
almost every mips/powerpc/superh/tile/avr32/mn10300/cris/c6x/score/frv/blackfin based SoC that we supported in the past got replaced with an ARM based version that retained the original peripherals.
mripard has quit [Ping timeout: 240 seconds]
<arnd>
there are a couple of those that have both arm and riscv versions now (at least announced), but not a lot that had arm in the past and completely abandoned it in favor of riscv
<arnd>
imgtec went metag->mips->riscv
mripard has joined #armlinux
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 248 seconds]
iivanov has quit [Quit: Leaving...]
monstr has quit [Remote host closed the connection]
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 252 seconds]
Drek45 has joined #armlinux
<alyssa>
as long as Apple doesn't switch to big endian we good
<alyssa>
^back, I guess
eduardas has quit [Quit: Konversation terminated!]
Drek45 has quit [Ping timeout: 252 seconds]
<alyssa>
i notice a lot of drivers do `bool predicate() { return !!(foo & BAR) }` ... isn't the !! unnecessary?
iivanov has joined #armlinux
<HdkR>
It's the fun technical difference of a true bool versus just an integer masquarading as one
<HdkR>
Likelyhood of actually hitting a problem with it these days is basically zero, but it is still good to use :)
<alyssa>
Hum. Isn't the behaviour guaranteed by the spec though?
<alyssa>
and coding-style.rst says "When using bool types the
<alyssa>
!! construction is not needed, which eliminates a class of bugs."
<alyssa>
but clearly drivers don't always follow that
<alyssa>
(70+ uses in drivers/gpu alone)
<HdkR>
eh, It's an idiom. I still use it periodically in my own code even to be very visible that it is a boolean check
<alyssa>
fair enough
<maz>
absolutely. it indicates intent, which is super important.
<maz>
(whatever the coding style doc says)
<alyssa>
Hmm, okay
<j`ey>
the coding-style says to 'When using bools', but in this case 'foo' is some kind of it, it's just the return value of the function that is bool
<j`ey>
*some kind of int
<alyssa>
j`ey: fair enough!
<alyssa>
I guessfor intent, writing !!(foo & BAR) is shorthand for (bool)(foo & BAR) then?
<maz>
yup.
<alyssa>
got it, thanks 👍
Drek45 has joined #armlinux
bps has quit [Ping timeout: 250 seconds]
tudorel has joined #armlinux
apritzel has joined #armlinux
bps has joined #armlinux
bps has joined #armlinux
bps has quit [Changing host]
tudorel has quit [Quit: tudorel]
Nact has joined #armlinux
Nact has quit [Client Quit]
apritzel has quit [Ping timeout: 240 seconds]
Nact has joined #armlinux
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 248 seconds]
macromorgan_ has joined #armlinux
macromorgan_ is now known as macromorgan
macromorgan has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
headless has joined #armlinux
ndesaulniers has joined #armlinux
<ndesaulniers>
did anyone recently report a boot failure for CONFIG_THUMB2_KERNEL=y on linux-next recently? Our CI is failing to boot recently for multiple different versions of clang
apritzel has joined #armlinux
nathanchance has joined #armlinux
Drek45 has quit [Ping timeout: 250 seconds]
CrashTestDummy3 has joined #armlinux
CrashTestDummy3 has quit [Read error: Connection reset by peer]
CrashTestDummy3 has joined #armlinux
Drek45 has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
Drek45 has quit [Remote host closed the connection]
abelloni has quit [Ping timeout: 240 seconds]
abelloni has joined #armlinux
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 248 seconds]
Drek45 has joined #armlinux
apritzel has quit [Ping timeout: 240 seconds]
alpernebbi has quit [Quit: alpernebbi]
headless has quit [Quit: Konversation terminated!]