From: Alex Dubov <oakad@yahoo.com>
To: Mike Kelly <pioto@pioto.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matt Fleming <matt@console-pimps.org>,
linux-mmc@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted
Date: Sun, 19 Sep 2010 17:50:30 -0700 (PDT) [thread overview]
Message-ID: <513651.95215.qm@web37608.mail.mud.yahoo.com> (raw)
In-Reply-To: <20100919105632.6fb34fa5@aether.home.pioto.org>
>
> Unfortunately, it doesn't seem to make a difference here.
> When I plug
> in my sd card, it looks like tifm_sd gets loaded, lots of
> debugging
> output. But, no /dev/mmcblk0 shows up, and mmc_block does
> not get
> loaded.
>
It's not created, because media times out. Why it happens is a different
question. It may be that clock parameters or something similar are not
properly configured (I don't have any datasheets for these devices).
There can also be a mechanical failure of the SD socket (these things do
happen).
Can you confirm that the socket and media are good, by trying them out
under windows or something?
Additional approach you can follow is to try and enable SDHCI interface
if it's available on your chip (xx21 have it and can be made to use it)
and then try it with sdhci.ko driver.
If you want to experiment with sdhci (a tricky exercise), some information
is available here:
http://www.gentoo-wiki.info/Acer_Ferrari_4005WLMi#SDHCI
next prev parent reply other threads:[~2010-09-20 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18602-10286@https.bugzilla.kernel.org/>
2010-09-15 19:38 ` [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted Andrew Morton
2010-09-17 13:54 ` Matt Fleming
2010-09-18 7:23 ` Alex Dubov
2010-09-18 9:01 ` Mike Kelly
2010-09-19 5:19 ` Alex Dubov
2010-09-19 14:56 ` Mike Kelly
2010-09-20 0:50 ` Alex Dubov [this message]
2010-09-21 3:25 ` Mike Kelly
2010-09-21 3:50 ` Alex Dubov
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=513651.95215.qm@web37608.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=pioto@pioto.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