mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 15:00:42 +0530	[thread overview]
Message-ID: <4dde4acb0706290230g6a38f0cds47b0d76216f861e6@mail.gmail.com> (raw)
In-Reply-To: <4684CDCC.9030202@drzeus.cx>

Hi All,

> Let's try something a lot less complex than mounting. Try running:
>         dd if=/dev/mmcblk0 of=/dev/null count=100

    Here goes the output(error).

/ # dd if=/dev/mmcblk0 of=/dev/null count=100
dd: can't open '/dev/mmcblk0': No such device or address

    The /dev is has the following:

/ # ls -l /dev | grep mmc
brwxrwxrwx    1 0        0        254,   0 Jun 26  2007 mmcblk0
brwxrwxrwx    1 0        0        254,   1 Jun 26  2007 mmcblk0p0
brwxrwxrwx    1 0        0        254,   2 Jun 26  2007 mmcblk0p1
brwxrwxrwx    1 0        0        254,   3 Jun 26  2007 mmcblk0p2
brwxrwxrwx    1 0        0        254,   4 Jun 26  2007 mmcblk0p3

    So are the device nodes wrong? When i say `cat /proc/devices` it says :

/ # cat /proc/devices
Character devices:
  1 mem
  2 pty
  3 ttyp
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 29 fb
 90 mtd
128 ptm
136 pts

Block devices:
  1 ramdisk
  1 ramdisk
 31 mtdblock
254 mmc

  So is the major number 254 is correct for MMC ??

Midhun.

  reply	other threads:[~2007-06-29  9:30 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 [this message]
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=4dde4acb0706290230g6a38f0cds47b0d76216f861e6@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®