mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: "Midhun Agnihotram" <agnimidhun@gmail.com>
Cc: "Pierre Ossman" <drzeus-mmc@drzeus.cx>,
	jdi@l4x.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Mounting MMC card
Date: Fri, 29 Jun 2007 12:01:51 +0200	[thread overview]
Message-ID: <200706291201.51387.hjk@linutronix.de> (raw)
In-Reply-To: <4dde4acb0706290245t5810b9ebrbb682ecb72f21830@mail.gmail.com>

Am Freitag 29 Juni 2007 11:45 schrieb Midhun Agnihotram:
> >
> > This all looks correct. How about /proc/partitions? And what's in /sys/block?
> >
> 
> Both of them show no sign of MMC.
> 
> / # cat /proc/partitions
> major minor  #blocks  name
> 
>   31     0       8192 mtdblock0
>   31     1        384 mtdblock1
>   31     2       1664 mtdblock2
>   31     3       2048 mtdblock3
>   31     4       4096 mtdblock4
> 
> 
> 
> / # cd /sys/block/
> /sys/block # ls -l
> drwxr-xr-x    3 0        0               0 Jan  1 00:00 mtdblock0
> drwxr-xr-x    3 0        0               0 Jan  1 00:00 mtdblock1
> drwxr-xr-x    3 0        0               0 Jan  1 00:00 mtdblock2
> drwxr-xr-x    3 0        0               0 Jan  1 00:00 mtdblock3
> drwxr-xr-x    3 0        0               0 Jan  1 00:00 mtdblock4
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram0
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram1
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram10
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram11
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram12
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram13
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram14
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram15
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram2
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram3
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram4
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram5
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram6
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram7
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram8
> drwxr-xr-x    2 0        0               0 Jan  1 00:00 ram9

For comparison, here's what it looks like here (kernel 2.6.21.5, udev):

# cat /proc/partitions
major minor  #blocks  name

  31     0        512 mtdblock0
  31     1       4096 mtdblock1
  31     2      28160 mtdblock2
 254     0     250880 mmcblk0
 254     1     250697 mmcblk0p1
# ls -l /sys/block/
drwxr-xr-x    6 root     root            0 Jun 29 08:41 mmcblk0
drwxr-xr-x    5 root     root            0 Jun 29 08:41 mtdblock0
drwxr-xr-x    5 root     root            0 Jun 29 08:41 mtdblock1
drwxr-xr-x    5 root     root            0 Jun 29 08:41 mtdblock2
# ls -l /sys/block/mmcblk0
-r--r--r--    1 root     root         4096 Jun 29 08:41 dev
lrwxrwxrwx    1 root     root            0 Jun 29 10:07 device -> ../../class/mmc_host/mmc0/mmc0:0002
drwxr-xr-x    2 root     root            0 Jan  1  1970 holders
drwxr-xr-x    3 root     root            0 Jun 29 08:41 mmcblk0p1
drwxr-xr-x    3 root     root            0 Jan  1  1970 queue
-r--r--r--    1 root     root         4096 Jun 29 08:41 range
-r--r--r--    1 root     root         4096 Jun 29 08:41 removable
-r--r--r--    1 root     root         4096 Jun 29 08:41 size
drwxr-xr-x    2 root     root            0 Jan  1  1970 slaves
-r--r--r--    1 root     root         4096 Jun 29 08:41 stat
lrwxrwxrwx    1 root     root            0 Jun 29 08:41 subsystem -> ../../block
--w-------    1 root     root         4096 Jun 29 08:41 uevent
# ls -l mmcblk0p1
ls: mmcblk0p1: No such file or directory
# ls -l /sys/block/mmcblk0/mmcblk0p1
-r--r--r--    1 root     root         4096 Jun 29 10:08 dev
drwxr-xr-x    2 root     root            0 Jan  1  1970 holders
-r--r--r--    1 root     root         4096 Jun 29 10:08 size
-r--r--r--    1 root     root         4096 Jun 29 10:08 start
-r--r--r--    1 root     root         4096 Jun 29 10:08 stat
lrwxrwxrwx    1 root     root            0 Jun 29 10:08 subsystem -> ../../../block
--w-------    1 root     root         4096 Jun 29 08:41 uevent
# cat /sys/block/mmcblk0/mmcblk0p1/size
501394
#

Hans




  reply	other threads:[~2007-06-29 10:02 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 [this message]
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=200706291201.51387.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®