public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 with sync burst mode
Date: Thu, 10 Mar 2005 17:40:24 +0100	[thread overview]
Message-ID: <20050310164024.GD4910@synertronixx3> (raw)
In-Reply-To: <Pine.LNX.4.58.0503101554220.5450@phoenix.infradead.org>

Am 2005-03-10 15:54 +0000 schrieb Artem B. Bityuckiy:

> OK, why does this mean JFFS2 is guilty of this? Why don't you suspect your 
> drivers? Why don't you suspect that you flashed your (say, correct) image 
> incorrectly?

The image is created in different ways, copied, dd'ed, mkfs.jffs2. Same
error picture.
All other constellations in software on this Hardware are working
perfect.
Kernel XIP out of this Flash device with this settings runs perfect.

No matter if partitions are cat'ed or dd'ed or files copied and such:
identical md5sums read back. 

I tested cramfs as rootfilesystem which works ok also.

> Just configure your kernel properly: switch on the "Test driver using RAM" 
> (MTD_MTDRAM) option in your kernel configuration. Type "modprobe mtdram" 
> if you have configured it as the kernel module.
> 
> If you do this your JFFS2 will work over emulated 4MiB in-RAM flash and 
> this will help you to exclude driver problems.

No clue until now. On Host-PC or on the embedded system?

Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2005-03-10 16:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 13:14 jffs2 with sync burst mode Konstantin Kletschke
2005-03-10 13:15 ` Artem B. Bityuckiy
2005-03-10 15:22   ` Konstantin Kletschke
2005-03-10 15:54     ` Artem B. Bityuckiy
2005-03-10 16:40       ` Konstantin Kletschke [this message]
2005-03-10 19:25         ` Steve Wahl
2005-03-10 23:24           ` Konstantin Kletschke
2005-03-10 15:46   ` Konstantin Kletschke
2005-03-10 16:21     ` Artem B. Bityuckiy
2005-03-10 16:48       ` Konstantin Kletschke
2005-03-10 17:08         ` Artem B. Bityuckiy
     [not found]         ` <JPEALJAFNGDDLOPNDIEECEJFDBAA.joakim.tjernlund@lumentis.se>
2005-03-10 23:18           ` Konstantin Kletschke
     [not found]             ` <BCEFJBPJCGFCNMMMIDBHEEPKCKAA.Joakim.Tjernlund@lumentis.se>
2005-03-11  0:03               ` Konstantin Kletschke
2005-03-10 17:02       ` Konstantin Kletschke
2005-03-10 17:17         ` Artem B. Bityuckiy
2005-03-10 18:27           ` Konstantin Kletschke
2005-03-10 18:53           ` Konstantin Kletschke
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 10:44 Konstantin Kletschke
2005-03-11 11:15 ` Artem B. Bityuckiy
2005-03-11 11:27   ` Konstantin Kletschke
2005-03-11 11:59     ` Artem B. Bityuckiy
2005-03-11 11:57 ` Konstantin Kletschke

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=20050310164024.GD4910@synertronixx3 \
    --to=lists@ku-gbr.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox