public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Johan Adolfsson" <johan.adolfsson@axis.com>
To: "mtd" <mtd@infradead.org>
Subject: MTD device minor numbers, documentation wrong?
Date: Tue, 13 Feb 2001 10:33:34 +0100	[thread overview]
Message-ID: <003f01c095a0$08f12020$0a070d0a@axis.se> (raw)
In-Reply-To: 10792.982055747@redhat.com

The 2.4.0 Documentation/devices.txt says that
even MTD minor numbers are readonly, but that doesn't seem to
be correct when trying things in real life.
Is the documentation wrong, or do I have the wrong version of it?
Or are we doing something wrong when registering partitions?

...
 31 char        MPU-401 MIDI
                  0 = /dev/mpu401data   MPU-401 data port
                  1 = /dev/mpu401stat   MPU-401 status port
    block       ROM/flash memory card
                  0 = /dev/rom0         First ROM card (rw)
                      ...
                  7 = /dev/rom7         Eighth ROM card (rw)
                  8 = /dev/rrom0        First ROM card (ro)
...

 90 char        Memory Technology Device (RAM, ROM, Flash)
                  0 = /dev/mtd0         First MTD (rw)
                  1 = /dev/mtdr0        First MTD (ro)
                    ...
                 30 = /dev/mtd15        16th MTD (rw)
                 31 = /dev/mtdr15       16th MTD (ro)




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-02-13  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 23:04 First cut at MTD/JFFS HOWTO Vipin Malik
2001-02-13  8:21 ` Johan Adolfsson
2001-02-13  9:08 ` David Woodhouse
2001-02-13  9:09 ` David Woodhouse
2001-02-13  9:15 ` David Woodhouse
2001-02-13  9:33   ` Johan Adolfsson [this message]
2001-02-13 10:05     ` MTD device minor numbers, documentation wrong? David Woodhouse
2001-02-13 17:45   ` Second cut at MTD/JFFS HOWTO Vipin Malik

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='003f01c095a0$08f12020$0a070d0a@axis.se' \
    --to=johan.adolfsson@axis.com \
    --cc=mtd@infradead.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