All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Priewasser <priewasser@gmail.com>
To: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: /dev/mtd* not there with latest MTD
Date: Thu, 13 Oct 2005 16:41:21 +0200	[thread overview]
Message-ID: <434E7211.6020709@gmail.com> (raw)

Hello,

I'm using a modified 2.6.11 kernel running on a Hynix eval board with 
NOR flash. Using the existing MTD works fine (CONFIG_MTD_BLOCK and 
CONFIG_MTD_CHAR enabled), MTD is using a custom map and is running fine. 
U-Boot uses nfsroot.

Today I patched in the latest CVS snapshot (2005-10-10). Kernel is 
starting without problems (MTD debug level 3):

 > H720x-MTD probing 32bit FLASH
 > H720X: Found 2 x16 devices at 0x0 in 32-bit bank
 >  Intel/Sharp Extended Query Table at 0x0031
 > Using buffer write method
 > cfi_cmdset_0001: Erase suspend on write enabled
 > cmdlinepart partition parsing not available
 > Using builtin partition table
 > Creating 5 MTD partitions on "H720X":
 > 0x00000000-0x00080000 : "ArMon"
 > mtd: Giving out device 0 to ArMon
 > 0x00080000-0x000c0000 : "Env"
 > mtd: Giving out device 1 to Env
 > 0x000c0000-0x00240000 : "Kernel"
 > mtd: Giving out device 2 to Kernel
 > 0x00240000-0x00640000 : "Ramdisk"
 > mtd: Giving out device 3 to Ramdisk
 > 0x00640000-0x02000000 : "jffs2"
 > mtd: Giving out device 4 to jffs2

But: there is no /dev/mtd* or /dev/mtdblock* at all!
There are no changes to u-boot or some other kernel config, only the new 
MTD source.

Patching the kernel with 2005-06-21 CVS results in having only 
/dev/mtdblock*, but no /dev/mtd*!..... very confusing.

I would be glad if someone could help, I can provide more information if 
needed.

Regards,
Bernhard

             reply	other threads:[~2005-10-13 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 14:41 Bernhard Priewasser [this message]
2005-10-13 16:13 ` /dev/mtd* not there with latest MTD Todd Poynor
2005-10-14 10:38   ` Bernhard Priewasser
2005-10-14  6:25 ` Holger Schurig
2005-10-24 13:30   ` Bernhard Priewasser

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=434E7211.6020709@gmail.com \
    --to=priewasser@gmail.com \
    --cc=linux-mtd@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.