ioc.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
INDICATORS OF COMPROMISE (IOC) InfoSec Community within the Fediverse. Newbies, experts, gurus - Everyone is Welcome! Instance is supposed to be fast and secure.

Administered by:

Server stats:

1.6K
active users

I'm currently (together with meshing) getting OpenWRT up and running on the TP-Link Deco M9+ devices. I'm on the v1 hardware, he's on v2.

The v1 has an 8MB SPI-NOR plus a massive 4GB eMMC while the v2 has a single 128MB NAND.

I'm having issues with the eMMC and this is a post looking for help from other hardware hackers.

Thanks to the GPL I have TP-Link's own configuration, but it's for a much older version of OpenWRT. I'm currently stuck on;

```
[ 20.216206] mmc0: cache flush error -84
[ 20.254030] mmc0: tried to HW reset card, got error -84
[ 20.254072] mmcblk0: recovery failed!
```
(followed by I/O errors)

The mmc is otherwise detected correctly, size and partitions etc.

The TP-Link config has an;

```
sd-ldo-gpios = <&tlmm 33 GPIO_ACTIVE_LOW>;
```

... and I can find the code using it in the old OpenWRT sdhci-msm.c with the comment "Toggle SD LDO GPIO on Init".

But the current OpenWRT version doesn't seem to have such a code path.

I have no idea if this is connected to my problem, but I'm running out of ideas here. The mmc works fine if I boot the TP-Link kernel of course.

Troed Sångberg

So the TP-Link GPL tarball has, in a Linux 3.14 tree, what looks like something of a hybrid between a backported mmc driver and their own development. It's newer than the one in Linux 3.14 actual, but it contains strings and code I cannot find in any subsequent Linux driver either.

Or I'm just completely missing something here that should be obvious. Why would they run a completely parallel development track - they're not exactly making their own silicon.