All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vipin Malik <vipin.malik@daniel.com>
To: "Fry, Dan" <dfry@bb.directv.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: /dev/mtdblock missing
Date: Wed, 02 May 2001 17:59:22 -0500	[thread overview]
Message-ID: <3AF0914A.418BAE6@daniel.com> (raw)
In-Reply-To: 617933180D08D311AB500090273F1F96016767D9@storm.corp.directvbroadband.net

Are you using devfs?

If not then the MAKEDEV script file in the utils file should do it. (using the
mknod command)

If you are using devfs, then I don't know.

Vipin






"Fry, Dan" wrote:

> Hi List,
>
>         I'm trying to get JFFS2 up and running on an atlas demo board.  The
> flash chip are being found and /dev/mtd0 (char device) is created.  However
> I can't mount a jffs2 because /dev/mtdblock0,1,2 etc. is missing.
> mtdblock.c is compiled in, and cat /proc/devices lists mtdblock under block
> devices.  I tried including ftl.c figuring there may be dependences.
>
> This is the output at boot up:
>
> physmap flash device: 2000000 at 1c000000
>
> <4><6>Physically mapped flash: Found 2 x16 devices at 0x0 in 32-bit mode
>
> Number of erase regions: 1
>
> Erase Region #0: BlockSize 0x20000 bytes, 64 blocks
>
> Primary Vendor Command Set: 0001 (Intel/Sharp Extended)
>
> Primary Algorithm Table at 0031
>
> Alternative Vendor Command Set: 0000 (None)
>
> No Alternate Algorithm Table
>
> Vcc Minimum: 4.5 V
>
> Vcc Maximum: 5.5 V
>
> No Vpp line
>
> Typical byte/word write timeout: 128 µs
>
> Maximum byte/word write timeout: 2048 µs
>
> Typical full buffer write timeout: 128 µs
>
> Maximum full buffer write timeout: 2048 µs
>
> Typical block erase timeout: 1024 µs
>
> Max. bytes in buffer write: 0x20
>
> Number of Erase Block Regions: 1
>
> Physically mapped flash: Found 2 x16 devices at 0x1000000 in 32-bit mode
>
> JEDEC ID: 89 15
>
> 0: offset=0x0,size=0x40000,blocks=64
>
> 1: offset=0x1000000,size=0x40000,blocks=64
>
> <5>ftl_cs: FTL header not found.
>
> Questions:
> 1) How to I get /dev/mtdblock0 created?
>
> 2) Is ftl.c needed -- the HOWTO doesn't include it?
>
> Cheers,
>
>         - Dan
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2001-05-02 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 22:51 /dev/mtdblock missing Fry, Dan
2001-05-02 22:59 ` Vipin Malik [this message]
2001-05-03  5:29   ` AW: " Florian Schirmer / TayTron

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=3AF0914A.418BAE6@daniel.com \
    --to=vipin.malik@daniel.com \
    --cc=dfry@bb.directv.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.