From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3040 invoked from network); 8 Nov 2021 21:56:31 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 8 Nov 2021 21:56:31 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Mon Nov 8 16:49:36 -0500 2021 Message-ID: Date: Mon, 08 Nov 2021 22:49:26 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <0100017d00cc4300-5b748622-ae08-4f14-8093-bdd98beb656d-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: self-healing cache rich-client deep-learning service proxy-aware controller Subject: Re: [9front] pi 400 and cm4 mmc issues Reply-To: 9front@9front.org Precedence: bulk nice. makes sense. anyone with a cm4 != 1GB (with eMMC)? we'd definitely need to adjust port/sdmmc.c code to deal with eMMC cards, but it shouldnt be too difficult. one can find the JDEC standard for eMMC in duckduckgo. -- cinap