From: "Midhun Agnihotram" <agnimidhun@gmail.com>
To: "Pierre Ossman" <drzeus-mmc@drzeus.cx>
Cc: "Hans-Jürgen Koch" <hjk@linutronix.de>,
jdi@l4x.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Mounting MMC card
Date: Fri, 29 Jun 2007 16:27:52 +0530 [thread overview]
Message-ID: <4dde4acb0706290357x54d3ea32vaf75d5cfe638cb25@mail.gmail.com> (raw)
In-Reply-To: <4684DEF3.5060103@drzeus.cx>
Hi,
> > Both of them show no sign of MMC.
> >
>
> Then you cannot mount them. What output did you see in dmesg when you inserted
> the card?
>
The dmesg contains only the following when I remove and insert the card.
<6>imx-mmc imx-mmc.0: card removed
<6>imx-mmc imx-mmc.0: card inserted
Also I was looking through the code. I found this function for init
of mmc_blk (linux/drivers/mmc/mmc_block.c)
static int __init mmc_blk_init(void)
{
int res = -ENOMEM;
res = register_blkdev(major, "mmc");
if (res < 0) {
printk(KERN_WARNING "Unable to get major %d for MMC media: %d\n",
major, res);
goto out;
}
if (major == 0)
major = res;
devfs_mk_dir("mmc");
return mmc_register_driver(&mmc_driver);
out:
return res;
}
This uses the function devfs_mk_dir() - defined in
linux/fs/devfs/base.c. I don't have devfs enabled in my kernel (kernel
version 2.6.16. In fact I don't even get an option to enable it in
menuconfig.). Can this be the cause of the problem?? I have found the
same code in the original kernel version too (the one from
kernel.org).
Thanks,
Midhun.
next prev parent reply other threads:[~2007-06-29 10:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4dde4acb0706261146s5906d8f3vb787d5aecb429116@mail.gmail.com>
2007-06-28 17:00 ` Midhun Agnihotram
2007-06-28 17:08 ` Midhun Agnihotram
2007-06-28 17:53 ` Jan Dittmer
2007-06-28 18:10 ` Hans-Jürgen Koch
2007-06-28 19:22 ` Pierre Ossman
2007-06-28 20:10 ` Hans-Jürgen Koch
2007-06-29 7:40 ` Fwd: " Midhun Agnihotram
2007-06-29 8:38 ` Hans-Jürgen Koch
2007-06-29 9:09 ` Midhun Agnihotram
2007-06-29 9:15 ` Pierre Ossman
2007-06-29 9:30 ` Midhun Agnihotram
2007-06-29 9:39 ` Pierre Ossman
2007-06-29 9:45 ` Midhun Agnihotram
2007-06-29 10:01 ` Hans-Jürgen Koch
2007-06-29 10:29 ` Pierre Ossman
2007-06-29 10:57 ` Midhun Agnihotram [this message]
2007-06-29 11:00 ` Pierre Ossman
2007-06-29 11:06 ` Midhun Agnihotram
2007-06-29 11:10 ` Pierre Ossman
2007-06-29 11:22 ` Midhun Agnihotram
2007-07-03 9:09 ` Midhun Agnihotram
2007-07-03 18:48 ` Pierre Ossman
2007-06-29 9:42 ` Uli Luckas
2007-06-29 10:29 ` Pierre Ossman
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=4dde4acb0706290357x54d3ea32vaf75d5cfe638cb25@mail.gmail.com \
--to=agnimidhun@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=hjk@linutronix.de \
--cc=jdi@l4x.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®