<macc24>
>Waiting for root device /dev/mmcblk1p7...\
<macc24>
it waits for root device /dev/mmcblk1p7
<tlwoerner>
my gut feeling is that the dts file of the kernel is configured to assume the filesystem is on emmc
<macc24>
why do you specify root parameter 2 times?
ldevulder_ has joined #linux-rockchip
<macc24>
tlwoerner: have you compiled sdmmc driver as module?
<macc24>
can you try removing and inserting sd card after booting?
<tlwoerner>
if i download a prebuilt image from armbian and boot it, some of the kernel boot log looks like: https://pastebin.com/CfiW71B8
<tlwoerner>
(i could give you all of it, but i think that's the relevant part)
ldevulder has quit [Ping timeout: 240 seconds]
<macc24>
is phy driver compiled into kernel?
mmind00 has quit [Quit: No Ping reply in 180 seconds.]
mmind00 has joined #linux-rockchip
lkcl has joined #linux-rockchip
stikonas has joined #linux-rockchip
<inode>
tlwoerner: from what i can see in your kernel message log t looks like only mmc0 is detected, if this is your sd card have you tried "root=/dev/mmcblk0p7" in your kernel command line instead of "root=/dev/mmcblk1p7"?
<tlwoerner>
inode: comparing to the working armbian image, i think mmc1 is the sdcard and mmc0 is the emmc
<mmind00>
tlwoerner: not necessarily ... mainline merged some asynchronuous mmc probing patch for 5.10 ... that inadvertedly more or less randomizes mmc numbering
<macc24>
mmind00: when?
<mmind00>
5.10
<macc24>
between 5.9 to 5.10 or between 5.10 to 5.11?
<mmind00>
I think in 5.10-rc1
<macc24>
hmm
<mmind00>
but memory and me have a difficult relationship ;-)
<macc24>
yeah i have bad memory too sometimes
<tlwoerner>
inode: in any case, i have tried mmcblk0, mmcblk1, and mmcblk2 (just to be on the safe side) and they're all the same
<tlwoerner>
macc24: what driver would be for the sdmmc? CONFIG_MMC_SDHCI?
<macc24>
tlwoerner: i don't know
<tlwoerner>
macc24: the multiple "root=" is just a quirk of OpenEmbedded, i don't think it makes a difference?
<mps>
kernel supports 'root=LABEL=label_of_rootfs' so I use this on devices with unordered (random) mmc assigned numbers
<tlwoerner>
mps: i can get OE to use PARTUUID numbers, but that doesn't change my result
<tlwoerner>
u-boot has an entry in its devicetree to set the order of devices: sdmmc first, then emmc
<mps>
tlwoerner: yes, I know
<mps>
and I dislike this, for me emmc should be 0
<tlwoerner>
looking through the devicetree for this board in the upstream linux kernel, i get a feeling its the emmc that is used
field^Mop has joined #linux-rockchip
<tlwoerner>
if i were better at reading/writing devicetree things i'm guessing that's where the change would need to be
<mps>
I even patched kernel on alpine linux for mediatek to use fixed numbering
<mps>
patched dts not kernel, to be precise
<tlwoerner>
arch/arm64/boot/dts/rk3328-roc-cc.dts has an &sdmmc node that contains:
<inode>
tlwoerner: how do the *mmc nodes differ between your mainline dts and what was used to generate the dtb in your working armbian build?
<tlwoerner>
inode: i know this will sound strange, but i've been looking for the kernel sources that armbian uses for a while and wish i could find them. i'd like to take a look at their device tree
<tlwoerner>
building armbian is a matter of downloading a script and running it, but you need to run it as root (which i'm not fond of) or be running a debian host (which i don't)
<tlwoerner>
the location of the sources doesn't seem obvious from the script :-(
<tlwoerner>
the working armbian image i have was downloaded as an image, not built by me
<inode>
that sounds a bit weird :)
<inode>
but i see what you mean based on their "compile.sh"
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
lkcl has quit [Ping timeout: 264 seconds]
lkcl has joined #linux-rockchip
WoC has quit [Ping timeout: 264 seconds]
kirgene has joined #linux-rockchip
kirgene has quit [Ping timeout: 240 seconds]
mps has quit [Ping timeout: 240 seconds]
mps has joined #linux-rockchip
kirgene has joined #linux-rockchip
<kirgene>
Hello,
<kirgene>
I'd like to know if RK3399 DisplayPort IP supports MST mode?
<kirgene>
I've found this patchset which says that Rockchip uses Cadence DisplayPort IP and this patchset implements DisplayPort driver for it with MST support:
<kirgene>
I'd like to use the above patchset to implement MST support for the existing CDN DP driver and need to know if it's possible on the hardware level for RK3399.
warpme_ has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 240 seconds]
mps has quit [Ping timeout: 265 seconds]
mps has joined #linux-rockchip
WoC has joined #linux-rockchip
vagrantc has joined #linux-rockchip
kirgene has quit [Ping timeout: 240 seconds]
matthias_bgg has joined #linux-rockchip
BenG83 has joined #linux-rockchip
warpme_ has quit [Quit: Connection closed for inactivity]
matthias_bgg has quit [Ping timeout: 264 seconds]
mps has quit [Ping timeout: 256 seconds]
mps has joined #linux-rockchip
BenG83 has quit [Quit: Leaving]
WoC has quit [Remote host closed the connection]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 240 seconds]
s_frit has quit [Remote host closed the connection]