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
mripard has quit [Ping timeout: 272 seconds]
apritzel has quit [Ping timeout: 268 seconds]
scosu has quit [Read error: Connection reset by peer]
scosu_ has joined #armlinux
sakman_ is now known as sakman
Nact has quit [Quit: Konversation terminated!]
Turingtoast has joined #armlinux
yeticheese has joined #armlinux
frieder has joined #armlinux
Crassus has quit [Ping timeout: 268 seconds]
iivanov has joined #armlinux
apritzel has joined #armlinux
frieder has quit [Ping timeout: 268 seconds]
guillaume_g has joined #armlinux
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
wwilly has joined #armlinux
frieder has joined #armlinux
mripard has joined #armlinux
guillaume_g has quit [Quit: Konversation terminated!]
apritzel has quit [Ping timeout: 268 seconds]
guillaume_g has joined #armlinux
apritzel has joined #armlinux
nsaenz has joined #armlinux
apritzel has quit [Ping timeout: 268 seconds]
CrashTestDummy has quit [Quit: Leaving]
CrashTestDummy has joined #armlinux
CrashTestDummy has quit [Client Quit]
CrashTestDummy has joined #armlinux
CrashTestDummy has quit [Client Quit]
apritzel has joined #armlinux
CrashTestDummy has joined #armlinux
CrashTestDummy has quit [Read error: Connection reset by peer]
CrashTestDummy has joined #armlinux
wwilly_ has joined #armlinux
wwilly has quit [Ping timeout: 268 seconds]
wwilly_ has quit [Quit: Leaving]
wwilly has joined #armlinux
wwilly has quit [Client Quit]
wwilly has joined #armlinux
apritzel has quit [Quit: Leaving]
wwilly has quit [Ping timeout: 268 seconds]
wwilly has joined #armlinux
wwilly has quit [Remote host closed the connection]
wwilly has joined #armlinux
wwilly has quit [Ping timeout: 264 seconds]
wwilly has joined #armlinux
yeticheese has quit [Remote host closed the connection]
yeticheese has joined #armlinux
mort has joined #armlinux
yeticheese has quit [Ping timeout: 264 seconds]
<mort>
Hey, I have a variscite sd-410 (with a snapdragon 410). With Linux 4.14, everything works as it should. However, with Linux 5.4, the built-in MMC just doesn't show up at all; no messages about "mmc" are printed during boot, and there's no /sys/block/mmc*. Any ideas about how I could debug this?
<milkylainen>
mort: Wrong dtb? Wrong kernel config? If you've migrated config and passed it through some oldconfig chances are symbols have been renamed. The kernel configuration does not warn about mismatched symbols anymore (since... 2008.).
<mort>
milkylainen: I don't think the dtb is the issue? And I've confirmed that the config option I'm setting (CONFIG_MMC_SDHCI_MSM) is the correct config option to enable the driver (the Qualcomm SDHCI Controller Support thing)
<mort>
I might just stay with 4.14
<mort>
you know, it's really annoying to hear all the talks from Greg & co. where they're complaining about how people aren't upgrading and how upgrading the kernel is super easy, when I've spent weeks trying to get 5.4 to work with essentially no progress so far
<bencoh>
does anything show up in the kernel logs?
<mort>
no
<milkylainen>
I would have thought that a grep -i mmc would yield something. Otherwise it seems to me that the subsystem is disabled somehow?
<mort>
I'm aware of the dts warning, we used a stupid name for a dts key for something unrelated. Will fix later, but it shouldn't have any effect here
<milkylainen>
mmc controller seems disabled?
<mort>
could be? Seems weird for a kernel update to disable the MMC controller though?
<milkylainen>
$ zcat /proc/config.gz | grep -i mmc on 5.4?
<mort>
hang on, I'll get that but I have to build a kernel first