From: "Pali Rohár" <pali.rohar@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MMC broken after a7778f8fbee098c78b1fa1e1331313a7e217fb30
Date: Mon, 05 Mar 2012 23:03:35 +0100 [thread overview]
Message-ID: <1356512.1Ex8tJMpGt@pali> (raw)
In-Reply-To: <4F54D488.3030303@ti.com>
On Monday 05 March 2012 07:58:16 Tom Rini wrote:
> On 03/04/2012 01:32 PM, Pali Roh?r wrote:
> > On Sunday 04 March 2012 13:23:44 Tom Rini wrote:
> >> On Sun, Mar 4, 2012 at 1:06 PM, Pali Roh?r<pali.rohar@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> this commit is breaking MMC support on Nokia N900:
> >>> a7778f8fbee098c78b1fa1e1331313a7e217fb30 omap_hsmmc: Wait for CMDI to be
> >>> clear
> >>>
> >>> I'm geting only error message "timedout waiting on cmd inhibit to clear"
> >>> and I cannot read files from eMMC and SD card. When I reverted commit
> >>> that commit I all is OK.
> >>
> >> OK, we need to debug what the n900 is doing (do you see this in qemu,
> >> real HW or both?) since clearing the bit fixes certain SD cards on
> >> other boards (beagleboard and gumstix iirc, but it was a generic
> >> issue). Thanks!
> >
> > RX-51 build of U-Boot in qemu cannot read mmc. It report error about bad
> > voltage. This was problem also before that commit. RX-51 Linux kernel does
> > not have any problem with mmc, special prepaired Maemo 5 image (with some
> > SW on eMMC) from Nokia working fine in qemu.
> >
> > I ignored above problem in qemu, because mmc worked fine on real n900. But
> > after that commit mmc does not working on real n900 too.
>
> First, if you change SD cards, does the problem go away? Second, my
> expectation is that we will make further changes, probably not in time
> for v2012.03, to the omap_hsmmc.c driver to bring it more in-line with
> how the kernel driver works. Thanks!
Problem is with internal eMMC (which cannot be changed) and with some external
Samsung microSD class 10. I do not have other microSD cards for testing now.
--
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120305/6d183cd8/attachment.pgp>
next prev parent reply other threads:[~2012-03-05 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 20:06 [U-Boot] MMC broken after a7778f8fbee098c78b1fa1e1331313a7e217fb30 Pali Rohár
2012-03-04 20:23 ` Tom Rini
2012-03-04 20:32 ` Pali Rohár
2012-03-05 14:58 ` Tom Rini
2012-03-05 22:03 ` Pali Rohár [this message]
2012-03-05 22:21 ` Tom Rini
2012-03-18 22:27 ` Grazvydas Ignotas
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=1356512.1Ex8tJMpGt@pali \
--to=pali.rohar@gmail.com \
--cc=u-boot@lists.denx.de \
/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