Hello Michal.
The Zybo board doesn't have any WP pin connected to the MicroSD card.
There is no physical possibility for the processor to know whether the
card is write-protected or not.
As I mentioned earlier, the practical problem can be worked around by
inverting the polarity of the WP
think that the device tree should
describe the hardware as it is, and not fool the driver into behaving
the way we want it to. These tricks always bite back later on.
Regards,
Eli
On 04/03/14 21:26, Sören Brinkmann wrote:
Hi Eli,
On Sun, 2014-03-02 at 01:20PM +0200, Eli Billauer wrote
-wp to
work around this issue.
Signed-off-by: Eli Billauer eli.billa...@gmail.com
---
Documentation/devicetree/bindings/mmc/mmc.txt |2 ++
drivers/mmc/host/sdhci-pltfm.c|4 +++-
drivers/mmc/host/sdhci.c |2 ++
include/linux/mmc/sdhci.h
-broken to
work around this issue.
Signed-off-by: Eli Billauer eli.billa...@gmail.com
---
Documentation/devicetree/bindings/mmc/mmc.txt |2 ++
drivers/mmc/host/sdhci-pltfm.c|4 +++-
drivers/mmc/host/sdhci.c |2 ++
include/linux/mmc/sdhci.h
Hello Chris.
On 24/02/14 02:12, Chris Ball wrote:
Hi Eli,
On Sun, Feb 23 2014, Eli Billauer wrote:
The write protection signal is absent on a board based upon Xilinx' Zynq
processor (ZyBo). This leads the kernel to think that the MicroSD card is
write protected, and causes a kernel panic
