All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Kaiser <rob@sysgo.de>
To: "Alexander Melichenko" <AlexanderM@lrpeople.com>
Cc: <mtd@infradead.org>
Subject: Re: Elan SC520 - problem with MTD
Date: Wed, 11 Apr 2001 14:22:59 +0200	[thread overview]
Message-ID: <01041114460500.00396@rob> (raw)
In-Reply-To: <00ae01c0c24e$5b566480$4d02010a@lrpeople.com>

On Mit, 11 Apr 2001 you wrote:
> We use Elan SC520 CDP Rev.1.3.
> I have linux-2.2.18 (on hard drive) with MTD support. I use MTD MAKEDEV script to make MTD devices. I want to place kernel image into flash. But when I do 
>   #cat zFlashImage > /dev/mtd0
> I see the message : bash: /dev/mtd0: No such device
>  
> During booting I see following messages :
> AMD Elan SC520 flash mapping: 1000000 at 4800000 
> mapped physical memory to c4800000
> Elan SC520 Physically mapped flash: Found no CFI device at location zero
> JFFS version 1.0, (C) 1999, 2000 Axis Communications AB
> 
> When I inspect directory /proc  I see 2 (!!!) files mtd with no information about MTD devices.
>  
> How can I solve this problem?

Which mapping module are you using ?

There is one specifically designed for the SC520 CDP in the current MTD CVS.
It works fine on my (rev1.2) board. 

Cheers

Rob

----------------------------------------------------------------
Robert Kaiser                         email: rkaiser@sysgo.de
SYSGO RTS GmbH
Am Pfaffenstein 14                    phone: (49) 6136 9948-762
D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10


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

  reply	other threads:[~2001-04-11 12:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11  6:12 Elan SC520 - problem with MTD Alexander Melichenko
2001-04-11 12:22 ` Robert Kaiser [this message]
2001-04-11 14:33   ` Vipin Malik
2001-04-12  5:23   ` Alexander Melichenko
2001-04-17 13:38     ` David Woodhouse
2001-04-17 13:42       ` Robert Kaiser
2001-04-17 13:54         ` David Woodhouse
2001-04-17 13:58           ` Robert Kaiser
2001-04-17 14:08             ` David Woodhouse
2001-04-17 15:35               ` Vipin Malik
2001-04-17 16:26                 ` David Woodhouse
2001-04-17 16:47                   ` Vipin Malik
2001-04-17 22:16                     ` David Woodhouse
2001-04-19 18:11                       ` Robert Kaiser
2001-04-18 13:50                   ` Robert Kaiser
2001-04-18 13:14                 ` Robert Kaiser
2001-04-18 16:05                   ` Vipin Malik
     [not found] <Pine.LNX.4.21.0104151822270.6721-100000@dagobert.svc.sysgo.de>
2001-04-16  8:35 ` Alexander Melichenko
     [not found] <Pine.LNX.4.21.0104161208120.12472-100000@dagobert.svc.sysgo.de>
     [not found] ` <01041713245700.01481@rob>
     [not found]   ` <005801c0cbd3$2bdb3c60$4d02010a@lrpeople.com>
2001-04-23  9:59     ` Robert Kaiser
2001-04-23 13:10       ` David Woodhouse
2001-04-23 13:45       ` Alex Lennon
2001-04-23 13:54         ` Robert Kaiser
2001-04-23 14:26           ` Alex Lennon
2001-04-23 14:43             ` Robert Kaiser
2001-04-23 23:07               ` Vipin Malik
2001-04-24  7:56                 ` Robert Kaiser
2001-04-24 12:28                   ` David Woodhouse
2001-04-24 14:07                     ` Ronald G Minnich
  -- strict thread matches above, loose matches on Subject: below --
2001-04-26 18:23 mark.langsdorf

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=01041114460500.00396@rob \
    --to=rob@sysgo.de \
    --cc=AlexanderM@lrpeople.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 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.