From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: "Midhun Agnihotram" <agnimidhun@gmail.com>
Cc: jdi@l4x.org, drzeus-mmc@drzeus.cx, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Mounting MMC card
Date: Fri, 29 Jun 2007 10:38:58 +0200 [thread overview]
Message-ID: <200706291038.58358.hjk@linutronix.de> (raw)
In-Reply-To: <4dde4acb0706290040p4f90b0b5q630b8e0bd5982908@mail.gmail.com>
Am Freitag 29 Juni 2007 09:40 schrieb Midhun Agnihotram:
>
> >* Is support for the file system on the MMC in your kernel?
>
> Yes. There is support for MMC card in my kernel.
I was talking about the file system on the card. Usually, you've
got vfat on such a card. How about that?
BTW, You mounted proc on /proc and sysfs on /sys, I hope?
>
> I have checked the log and it is attached to the end of the mail.
> The log contains debug messages for removing and inserting the MMC
> card. But nothing specific relating to mount. Can you interpret
> anything more from it?
No. You don't have jffs2 on your MMC, do you?
>
> >Have you checked that your device nodes are correct? Since you use busybox I
> >assume the system is too lightweight to run udev.
>
> Yes. I have checked the device nodes. They are fine for MMC. (I
> have made them form what I got on the internet. BTW can anybody tell
> me how can I find the corresponding major and minor number for my
> device driver? This MMC driver is from Microcross. I have put the
> device nodes as 254,0 - which are generic.).
Here's what I have (nodes created by udev):
# ls -l /dev/mmc*
brw-rw---- 1 root root 254, 0 Jun 29 08:41 /dev/mmcblk0
brw-rw---- 1 root root 254, 1 Jun 29 08:41 /dev/mmcblk0p1
>
> >I run udev on an arm system, it costs you about 200kBytes,
> >and saves you all the trouble with creating device files.
> >Note that you don't need any rules files. If you want to write
> >rules, you can even implement a poor-man's hotplug without HAL.
> >If you can afford 200k, use udev.
>
> I have seen the udev page. But I am a bit skeptic about
> implementing it with my kernelas this kernel is from Microcross -
> customized for CSB535FS board.
As long as it's a reasonable recent kernel (>=2.6.15), it shouldn't
be a problem.
> I want to try udev only as my last
> option.
Your choice.
Hans
next prev parent reply other threads:[~2007-06-29 8:39 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 [this message]
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
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=200706291038.58358.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=agnimidhun@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--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®