public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Alice Hennessy <ahennessy@mvista.com>
To: andrzej_mialkowski@o2.pl
Cc: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: gen probe.c issue
Date: Tue, 03 Feb 2004 10:35:48 -0800	[thread overview]
Message-ID: <401FEA03.7DCCA6F5@mvista.com> (raw)
In-Reply-To: 20040130225505.8DE4ED0B17@rekin6.o2.pl

andrzej_mialkowski@o2.pl wrote:

> Not understand purpose of this change; do you really have chip that is not fully visible in system?
> Your solution would cause crash at least in two cases:
> 1) if map size is really small for instance 0 or 1 and we are attempting to detect flash. So there must be some reasonable minimal map size value.
> 2) returned size of mtd is calculated from "mtd->size = devsize * cfi->numchips" so you will get mtd size greater than supported by map driver (mapped in virtual memory?!). At least redboot parser will attempt access last sector of map:
> /* Read the start of the last erase block */
>         ret = master->read(master, master->size - master->erasesize,
>                            PAGE_SIZE, &retlen, (void *)buf);
>
> I had somehow similar case when redboot partition were located not at the end of flash. I just modified in map driver detected map size between calls to do_map_probe and parse_mtd_partitions. In your case it might be possible that you need just to lay about map size before calling do_map_probe. For you effect will be same, you will not break others code.
> Andrzej
>
> ---- Wiadomo¶æ Oryginalna ----
> Od: Alice Hennessy <ahennessy@mvista.com>
> Do: linux-mtd@lists.infradead.org
> Data: Wed, 28 Jan 2004 16:18:21 -0800
> Temat: gen_probe.c issue
>
> >Hi,
> >
> >The following patch fixes a problem seen when the map->size is less than
> >the actual chip size.
> >Without the fix,  max_chips gets set to 0.
> >
> >Alice
> >
> >Index: drivers/mtd/chips/gen_probe.c
> >===================================================================
> >RCS file: /home/cvs/mtd/drivers/mtd/chips/gen_probe.c,v
> >retrieving revision 1.14
> >diff -u -r1.14 gen_probe.c
> >--- drivers/mtd/chips/gen_probe.c       8 Nov 2003 00:51:21 -0000
> >1.14
> >+++ drivers/mtd/chips/gen_probe.c       28 Jan 2004 23:58:38 -0000
> >@@ -108,6 +108,9 @@
> >         * Align bitmap storage size to full byte.
> >         */
> >        max_chips = map->size >> cfi.chipshift;
> >+        /* correct for case where map->size is less than chip size */
> >+        if (!max_chips)
> >+                max_chips = 1;
> >        chip_map = kmalloc((max_chips / 8) + ((max_chips % 8) ? 1 : 0),
> >GFP_KERNEL);
> >        if (!chip_map) {
> >                printk(KERN_WARNING "%s: kmalloc failed for CFI chip
> >map\n", map->name);
> >
> >
> >
> >______________________________________________________
> >Linux MTD discussion mailing list
> >http://lists.infradead.org/mailman/listinfo/linux-mtd/
> >

I believe it's ok to set up partitions for a flash and not have all the flash visible.  Perhaps
a better way to do this would be to just make another partition and make the protected part
read only.   But I believe not making the whole flash visible is also acceptable.
BTW, I don't use redboot partitioning with this flash.

David,  if you think it's bad practice,  I will change my mapping file instead.

Alice

  reply	other threads:[~2004-02-03 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29  0:18 gen_probe.c issue Alice Hennessy
2004-01-30 22:55 ` andrzej_mialkowski
2004-02-03 18:35   ` Alice Hennessy [this message]
2004-02-03 22:30     ` gen probe.c issue David Woodhouse
2004-02-03 22:41       ` Alice Hennessy

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=401FEA03.7DCCA6F5@mvista.com \
    --to=ahennessy@mvista.com \
    --cc=andrzej_mialkowski@o2.pl \
    --cc=dwmw2@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