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
hanetzer has quit [Ping timeout: 255 seconds]
hanetzer has joined #armlinux
hanetzer has quit [Ping timeout: 246 seconds]
hanetzer has joined #armlinux
hanetzer has quit [Ping timeout: 248 seconds]
hanetzer has joined #armlinux
apritzel has quit [Ping timeout: 260 seconds]
apritzel has joined #armlinux
Nact has joined #armlinux
mraynal has quit [Remote host closed the connection]
mraynal has joined #armlinux
justPardoned has quit [Quit: ZNC 1.8.2 - https://znc.in]
jeeeun has quit [Read error: Connection reset by peer]
jeeeun6 is now known as jeeeun
[florian] has quit [Ping timeout: 260 seconds]
[florian] has joined #armlinux
heat has quit [Ping timeout: 246 seconds]
amitk has joined #armlinux
tmlind has quit [Ping timeout: 260 seconds]
abelvesa has quit [Ping timeout: 260 seconds]
abelvesa has joined #armlinux
tmlind has joined #armlinux
mriesch has quit [Ping timeout: 260 seconds]
mriesch has joined #armlinux
sven has quit [Ping timeout: 260 seconds]
sven has joined #armlinux
alpernebbi has joined #armlinux
jeeeun9 has joined #armlinux
jeeeun has quit [Read error: Connection reset by peer]
jeeeun9 is now known as jeeeun
Xogium has quit [Quit: Leaving.]
Xogium has joined #armlinux
abelvesa has quit [Ping timeout: 260 seconds]
abelvesa has joined #armlinux
tmlind has quit [Ping timeout: 260 seconds]
tmlind has joined #armlinux
headless has joined #armlinux
jeeeun5 has joined #armlinux
jeeeun has quit [Ping timeout: 260 seconds]
jeeeun5 is now known as jeeeun
apritzel has joined #armlinux
abelvesa has quit [Ping timeout: 260 seconds]
abelvesa has joined #armlinux
Pali has joined #armlinux
headless has quit [Quit: Konversation terminated!]
<marcan>
is there any standard for describing SoC and CPU model human-readable names in the DT? if not, should there be?
<marcan>
AIUI right now userspace needs a table from CPU and SoC compatibles to human-readable names, but I don't know of any standard for that akin to pci-ids, and it seems really silly when we have a device tree that could just contain human-readable model properties for them
<marcan>
we do have `model` in the DT root for human-readable device name, why not also have it in CPU nodes and maybe some other property for an overall SoC name?
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
<broonie>
marcan: we have a similar property on the sound cards FWIW (because the plastics are important to configuration) so there’s some precedent.
<broonie>
The arm64 arch maintainers have been very resistant to adding names in the kernel because of the issues with marketing and renames.
<broonie>
That’s not the DT though
EricCurtin[m] has joined #armlinux
apritzel has quit [Ping timeout: 260 seconds]
apritzel has joined #armlinux
chip_x has quit [Remote host closed the connection]
Pali has quit [Ping timeout: 260 seconds]
Pali has joined #armlinux
elastic_dog has joined #armlinux
apritzel has quit [Ping timeout: 260 seconds]
apritzel has joined #armlinux
chipxxx has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
<marcan>
broonie: Yeah, the DT already has a device name, it seems logical to also have SoC and CPU core names, which are the things userspace sysinfo type apps care about the most
<broonie>
marcan: for the cores specifically the theory is that the ID numbers are already exported via sysfs so userspace can have a table of ID to meaningful names if it wants it.
<marcan>
yeah, but then that table needs to be updated for every new core...
<marcan>
and there is no single source of truth in userspace for this right now
<marcan>
adding Apple's latest core every year (plus whatever ARM is coming up with) seems kind of a waste of time when we already deal with all of that in the device tree anyway
<marcan>
plus IIRC they use different IDs for different SoCs for what is fundamentally the same core