From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "'Kári Davíðsson'" <kd@flaga.is>, <mtd@infradead.org>
Subject: RE: CFI with 4 x8/x16 devices on a 32-bit bus
Date: Thu, 12 Apr 2001 15:52:44 +0200 [thread overview]
Message-ID: <009901c0c357$da1bf410$0a01a8c0@Win1> (raw)
In-Reply-To: <EADB10BAC266A14A85ECBF8686A73E310A9134@kolkrabbi.flaga.is>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
Hi
I been all the time wrong! I just discovered that hexl-mode i emacs is
broken!
Emacs in hexl-mode displays 81ff81ff81ff ... and od -x says fffffff ...
Sorry about that.
While I am at it perhaps someone can enlighten me somewhat ...
I am a bit confused about how add_mtd_device() and add_mtd_partitions()
work.
Looking in nora.c it looks like you can partition a flash by doing
a few calls to add_mtd_device() with different offsets, but if you can do
that with add_mtd_device(), what's the point with add_mtd_partitions()?
I am missing something here, can someone explain when and how you are
supposed to
use these two functions?
Jocke
-----Original Message-----
From: owner-mtd@infradead.org [mailto:owner-mtd@infradead.org]On Behalf
Of Kári Davíðsson
Sent: Thursday, April 12, 2001 14:42
To: mtd@infradead.org
Subject: RE: CFI with 4 x8/x16 devices on a 32-bit bus
> -----Original Message-----
> From: Joakim Tjernlund [mailto:joakim.tjernlund@lumentis.se]
> Sent: 11. apríl 2001 15:05
> To: mtd@infradead.org
> Subject: RE: CFI with 4 x8/x16 devices on a 32-bit bus
<snip>
3) 2 partitions( tried a few different sizes) - Not OK, here I get
81ff81ff81ff ... !
You get this behaviour for both partitions? Also one that has all
sectors of the same size?
<snip>
>
> Apparently this is chip with 2 erase sectors sizes. I suspect
> the different
> sector sizes
> is the cause to my problems, but I cant figure out where the
> problem is. I
> have
> tried with&whithout virtual regions.
Get it to work without the viertual regions. Then add the virtual
regions if you need them. Stricly speeking you anly need them if you
have a partition that you need to manage that crosses erase region
boundary. It is hightly experimental code
that has only be tested on my single 16bit wide Intel chip so it is
bound to fail
on more complex setups.
K.D.
<snip>
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2676 bytes --]
next prev parent reply other threads:[~2001-04-12 13:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 12:41 CFI with 4 x8/x16 devices on a 32-bit bus Kári Davíðsson
2001-04-12 13:52 ` Joakim Tjernlund [this message]
2001-04-17 13:57 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 14:59 Joakim Tjernlund
2001-04-17 15:23 ` David Woodhouse
2001-04-17 15:51 ` Joakim Tjernlund
2001-04-17 15:53 ` David Woodhouse
2001-04-17 16:26 ` Joakim Tjernlund
2001-04-14 16:54 Kári Davíðsson
2001-04-11 15:05 Joakim Tjernlund
2001-04-10 7:30 Brett Carswell
2001-04-17 14:13 ` David Woodhouse
2001-04-09 23:34 Brett Carswell
2001-04-10 0:27 ` Nicolas Pitre
2001-04-10 1:55 ` David Woodhouse
2001-04-10 1:53 ` David Woodhouse
2001-04-10 2:01 ` David Woodhouse
2001-04-05 22:58 Brett Carswell
2001-04-06 13:45 ` David Woodhouse
2001-04-06 14:12 ` David Woodhouse
2001-04-09 16:24 ` Joakim Tjernlund
2001-04-05 7:32 Brett Carswell
2001-04-05 14:09 ` David Woodhouse
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='009901c0c357$da1bf410$0a01a8c0@Win1' \
--to=joakim.tjernlund@lumentis.se \
--cc=kd@flaga.is \
--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