linux-kernel - Re: v5.10-rc3 vs. Droid 4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20201115192458.GA19769@duo.ucw.cz>
Date:   Sun, 15 Nov 2020 20:24:58 +0100
From:   Pavel Machek <pavel@....cz>
To:     Tony Lindgren <tony@...mide.com>
Cc:     kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, sre@...nel.org, nekit1000@...il.com,
        mpartap@....net, merlijn@...zup.org, martin_rysavy@...trum.cz
Subject: Re: v5.10-rc3 vs. Droid 4

On Sun 2020-11-15 18:49:09, Pavel Machek wrote:
> Hi!
> > > 
> > > Does anyone have Droid 4 working with 5.10-rc3?
> > > 
> > > I tried it with the original config; I got message about culomb
> > > counter calibration done scrolling (and boot progressing very slowly
> > > or not at all) . So ... I disabled cpcap battery & charger
> > > support. But init still drops me to emergency shell.
> > > 
> > > I may try some more, but if someone know what is going on, let me
> > > know.
> > 
> > I ran into this too, sorry I thought I added you to Cc but looks like not.
> > See the fix here:
> > 
> > https://lore.kernel.org/lkml/20201111170613.46057-1-tony@atomide.com/
> 
> You did (thank you!) but I failed to realize importance of that
> email. I have tested it and the culomb counter messages are gone.
> 
> Good.
> 
> But it looks like my mmcblk interfaces got re-numbered, from mmcblk0 &
> mmcblk1 to mmcblk0 & mmcblk2. ... which breaks my startup. If someone
> knows what is going on there, please tell me :-).

It seems like my wireless card sabotages the mmc? If I disable mmc3
completely, I'm back to working system. (Those omap3 changes are
probably not needed).

Best regards,
									Pavel


diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi
index ae4c0f7c7383..21a5375f1e66 100644
--- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi
+++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi
@@ -394,6 +394,7 @@
 	ti,non-removable;
 };
 
+#if 0
 &mmc3 {
 	pinctrl-names = "default";
 	pinctrl-0 = <&mmc3_pins>;
@@ -420,6 +421,7 @@
 		tcxo-clock-frequency = <26000000>;
 	};
 };
+#endif
 
 &i2c1 {
 	led-controller@38 {
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 1fed802175fc..60eb3ebdc6b8 100644
--- a/arch/arm/boot/dts/omap3-n900.dts
+++ b/arch/arm/boot/dts/omap3-n900.dts
@@ -866,9 +866,11 @@
 	no-sd;
 };
 
+#if 0
 &mmc3 {
 	status = "disabled";
 };
+#endif
 
 &gpmc {
 	ranges = <0 0 0x01000000 0x01000000>,	/* 16 MB for OneNAND */
diff --git a/arch/arm/boot/dts/omap3-n950-n9.dtsi b/arch/arm/boot/dts/omap3-n950-n9.dtsi
index 8601e5ab85b8..704e4c7149ed 100644
--- a/arch/arm/boot/dts/omap3-n950-n9.dtsi
+++ b/arch/arm/boot/dts/omap3-n950-n9.dtsi
@@ -563,9 +563,11 @@
 	ti,non-removable;
 };
 
+#if 0
 &mmc3 {
 	status = "disabled";
 };
+#endif
 
 /* RNG not directly accessible on N950/N9. */
 &rng_target {
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 9dcae1f2bc99..ba575e76b75a 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -532,6 +532,7 @@
 			dma-names = "tx", "rx";
 		};
 
+#if 0
 		mmc3: mmc@...ad000 {
 			compatible = "ti,omap3-hsmmc";
 			reg = <0x480ad000 0x200>;
@@ -540,6 +541,7 @@
 			dmas = <&sdma 77>, <&sdma 78>;
 			dma-names = "tx", "rx";
 		};
+#endif
 
 		mmu_isp: mmu@...bd400 {
 			#iommu-cells = <0>;
diff --git a/arch/arm/boot/dts/omap4-l4.dtsi b/arch/arm/boot/dts/omap4-l4.dtsi
index de742bf84efb..477246f8d5c1 100644
--- a/arch/arm/boot/dts/omap4-l4.dtsi
+++ b/arch/arm/boot/dts/omap4-l4.dtsi
@@ -2214,6 +2214,7 @@
 			ranges = <0x0 0xa8000 0x4000>;
 		};
 
+#if 0
 		target-module@...00 {			/* 0x480ad000, ap 63 50.0 */
 			compatible = "ti,sysc-omap4", "ti,sysc";
 			reg = <0xad000 0x4>,
@@ -2245,6 +2246,7 @@
 				dma-names = "tx", "rx";
 			};
 		};
+#endif		
 
 		target-module@...00 {			/* 0x480b0000, ap 47 40.0 */
 			compatible = "ti,sysc";




-- 
http://www.livejournal.com/~pavelmachek

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)