public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Florian Schirmer / TayTron" <schirmer@taytron.net>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <mtd@infradead.org>
Subject: Re: AW: Some bugs
Date: Mon, 5 Mar 2001 08:30:08 +0100	[thread overview]
Message-ID: <005901c0a546$367c8d80$0d3318b5@jolt> (raw)
In-Reply-To: Pine.LNX.4.30.0103031754080.7202-100000@imladris.demon.co.uk

Hi..

> > So please can you commit the 3 solved issues to cvs?
>
> The first was already there. The above two just joined it. Please confirm
> that the writew change is working.

Looks very good. We've tried Intel F640, 2x Intel F320 (interleaved) and 2x
AMD (interleaved). Everything is fine now.

There are still some points on my list:

1. cfi_cmdset_0001 broken:

/* We have to assume that all the erase blocks are the same size. */
mtd->erasesize = ((cfi.cfiq->EraseRegionInfo[i] >> 8) & ~0xff) *
cfi->interleave;

should be

mtd->erasesize = ((cfi->cfiq->EraseRegionInfo[0] >> 8) & ~0xff) *
cfi->interleave;

(cfi-> and  [0])

2. physmap (?) broken:

The inter_module stuff thems to have a problem somewhere. The modules cant
be unloaded since the usagecount wont decrement correctly. Dont know wether
it's the fault of physmap or not.

Happing hacking!
   Florian Schirmer



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

  reply	other threads:[~2001-03-05  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 20:44 Some bugs Florian Schirmer / TayTron
2001-03-03 16:39 ` David Woodhouse
2001-03-03 17:41   ` AW: " Florian Schirmer / TayTron
2001-03-03 18:18     ` David Woodhouse
2001-03-05  7:30       ` Florian Schirmer / TayTron [this message]
2001-03-05  8:42         ` David Woodhouse
2001-03-05 16:21           ` MTD Patches Florian Schirmer / TayTron
2001-03-06  8:38           ` AW: Some bugs Florian Schirmer / TayTron
2001-03-06  8:12             ` David Woodhouse
2001-03-06  9:11               ` 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='005901c0a546$367c8d80$0d3318b5@jolt' \
    --to=schirmer@taytron.net \
    --cc=dwmw2@infradead.org \
    --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