From: "Marek Vašut" <marek.vasut@gmail.com>
To: tony@atomide.com, linux-omap-open-source@linux.omap.com
Subject: Re: MMC not working on Z71
Date: Fri, 1 Dec 2006 07:00:17 +0100 [thread overview]
Message-ID: <200612010700.17693.marek.vasut@gmail.com> (raw)
In-Reply-To: <20061130223920.GB9605@atomide.com>
Dne čtvrtek 30 listopad 2006 23:39 jste napsal(a):
> * Marek Vašut <marek.vasut@gmail.com> [061126 15:17]:
> > Hi,
> > since this commit
> > http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=3
> >6808520ce2c9ade647d36c80004c158c71d0510 MMC on palmz71 stopped working.
> > With latest git it doesnt even get inited. When I enable debug I get cmd3
> > timeout. I find out that when I compile initramfs into kernel and try
> > mounting mmc partition, the kernel tries to init the card (I get that
> > MMC: something and mmc: p1 p2 etc. [sorry, I dont remember it exactly, I
> > can give more details, if you need them, just ask]) but fails with a lot
> > of io errors about probs with reading mmc block 0. And that´s the end.
> > Weird is, that mmc was working with 2618-omap1, but after that sync with
> > Linuses tree it just suddenly stopped. The diff against those 2 commits
> > is 32megs, so it´s quite a prob to find what damaged the mmc. Also, it´s
> > weird that mmc works on palmte. Can this be prob, that mmc isnt powered
> > up? I doubt so though.
>
> Yeah, that a big patch :) Have you tried just undoing the mmc parts in that
> patch and see if that helps to narrow down the problem?
>
> Regards,
>
> Tony
Sure ;) I removed all patches for mmc but one - mmc-block.c.diff - which was
too complexly integrated into the kernel. But it didnt helped though :( btw.
yeah ... it is a bigger patch ;D
BR
Marex
prev parent reply other threads:[~2006-12-01 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 23:16 MMC not working on Z71 Marek Vašut
2006-11-30 22:39 ` tony
2006-12-01 6:00 ` Marek Vašut [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=200612010700.17693.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.