GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Wednesday, 22-Jan-2025 09:36:59 JST Alfred M. Szmidt Alfred M. Szmidt
    in reply to
    • Troed Sångberg

    @troed Yes.

    In conversation about a year ago from mastodon.social permalink
    • Embed this notice
      Troed Sångberg (troed@ioc.exchange)'s status on Wednesday, 22-Jan-2025 09:37:00 JST Troed Sångberg Troed Sångberg
      in reply to

      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.

      In conversation about a year ago permalink
    • Embed this notice
      Troed Sångberg (troed@ioc.exchange)'s status on Wednesday, 22-Jan-2025 09:37:01 JST Troed Sångberg Troed Sångberg

      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.

      #OpenWRT #HardwareHacking

      In conversation about a year ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.