00:05 <enyc> OpenWRT 23.05.3 any time soon? I guess there may be no reason for it as-yet.

00:15 <Habbie> any reason you ask? :)"

01:23 <owrt-images-builds> Build [#10](https://buildbot.openwrt.org/images/#/builders/4/builds/10) of `master_mvebu/cortexa53` failed.

08:39 <enyc> Habbie: simplistically, curiosity, complex -- may affect deployment decisions if know release soon , but in any cose curious how this comes about... I guess ''bugfixes and CVEs'' generally trigger rather than routine?

11:54 <russell--> i have a zyxel gs1900-24e that's assigning a macaddr to the switch interface of 00:00:00:01:00:00

13:46 <KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_kirkwood.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)

15:23 <owrt-images-builds> Build [#11](https://buildbot.openwrt.org/images/#/builders/4/builds/11) of `master_mvebu/cortexa53` completed successfully.

23:32 <hadis> Hello, I am trying to port openwrt to a new device and I have run into an issue. I got a kernel runninb but it won't recognise the 8GB eMMC of the device. I already looked at some other DTS files that mention mmcblk devices in their bootargs but those don't seem to define any mmcblk devices otherwise. Am I missing a specific kernel module maybe?

23:33 <hadis> Help with this woud be greatly appreciated

23:34 <Habbie> hi hadis, i'm no expert, but i can ask a few questions that may or may not help

23:34 <hadis> Yes?

23:35 <Habbie> do you, or did you, have access to whatever was running on the device originally? kernel logs? can you extract a dts/dtb from the original firmware?

23:35 <Habbie> also, can you pastebin what you know about the device?

23:41 <hadis> I can boot the original firmware, an ancient version of openwrt and I already extraced the (or one of, there's like 8 that I was able to dump). The device is based on a linkit smart 7688. https://github.com/VioSynthax/Klippventurer-Pi/issues/1 there are lots of photos of it in this github issue. Here is a stock kernel log https://pastebin.com/FfH2KDhi and here is the most probably correct dts file https://past

23:41 <PaulFertser> hadis: you're supposed to have appropriate data in the DT to have mmc controller enabled and working and then it should recognise eMMC automatically, no kernel command line needed.

23:42 <PaulFertser> hadis: truncated after correct dts file

23:42 <hadis> https://pastebin.com/JBBFghgu and this is my DTS file

23:42 <PaulFertser> hadis: and kernel output with that dts file?

23:43 <hadis> PaulFertser: You are always here and ready to help. Thank you : )

23:43 <PaulFertser> hadis: right now I need to go to sleep though.

23:44 <hadis> https://pastebin.com/kdF0q0WQ this is the current dmesg

23:44 <hadis> ah I did not use earlyprintk, that would be relevant here, right?

23:45 <PaulFertser> hadis: no, earlyprintk is needed only when the kernel hangs before loading uart driver and you do not see anything at all.

23:45 <hadis> alright

23:46 <PaulFertser> hadis: so my idea would be to check compatible property in sdhci node in mt7628an.dtsi and then I'd git grep in drivers/ for that compatible string.

23:46 <PaulFertser> That would tell you what config option is needed to enable SD/MMC controller in question.

23:49 <hadis> I have kmod-sdhci-mt7620 selected already but not kmod-sdhci

23:50 <hadis> the former is listed as compatible `compatible = "ralink,mt7620-sdhci";`

23:50 <PaulFertser> hadis: so you need kmod-sdhci-mt7620 and it should pull in the necessary deps

23:51 <PaulFertser> hadis: but adding that is a kmod, it's not built in kernel so you can't use eMMC for root that way.

23:51 <hadis> ohhhh

23:51 <hadis> because the module isn't loaded yet

23:51 <hadis> I just have it selected like this in the config `<*> kmod-sdhci-mt7620`

23:52 <hadis> I thought that includes it in the kernel while <M> compiles it as a loadable module. But that's no the case?

23:52 <PaulFertser> Is mtk_sd visible in lsmod?

23:52 <PaulFertser> hadis: not the case in OpenWrt, yes, sorry.

23:53 <PaulFertser> hadis: for custom build you can do "make kernel_menuconfig" and find it there with / and select with y.

23:53 <hadis> PaulFertser: Yes, mtk_sd 15682 0

23:53 <PaulFertser> hadis: but you should be seeing that eMMC later when the system boots fully and the module is loaded I'd expect.

23:54 <hadis> Do I unselect kmod-sdhci-mt7620 in menuconfig before selecting it in kernel_menuconfig?

23:55 <PaulFertser> hadis: doesn't matter. But I'm afraid it won't help probably something else is missing there. Like eMMC isn't powered or card detect should be assumed to always signal presence somehow.

23:57 <PaulFertser> hadis: why do you set mediatek,cd-high ?

23:59 <PaulFertser> I'd play with mediatek,cd-poll just in case too.