linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raul <raul.garcia10101@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci: add quirk for broken write protect detection
Date: Thu, 27 Nov 2014 14:08:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141127T150653-41@post.gmane.org> (raw)
In-Reply-To: 1393198345-8365-1-git-send-email-eli.billauer@gmail.com

Eli Billauer <eli.billauer <at> gmail.com> writes:

> 
> 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 during boot, as root fails to
> mount RW.
> 
> This patch adds a quirk and an optional OF property, sdhci,wp-broken to
> work around this issue.



Hello, I am hitting the issue described in this thread, where can I get the
patch or the repo to fic it?







      parent reply	other threads:[~2014-11-27 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 23:32 [PATCH] mmc: sdhci: add quirk for broken write protect detection Eli Billauer
2014-02-24  0:12 ` Chris Ball
2014-02-24  0:54   ` Eli Billauer
2014-11-27 14:08 ` Raul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20141127T150653-41@post.gmane.org \
    --to=raul.garcia10101@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).