All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ccool <ccool@ninjatech.biz>
To: Linux MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Trouble with mtd partition
Date: Sat, 28 Aug 2004 16:00:36 -0400	[thread overview]
Message-ID: <200408281600.36216.ccool@ninjatech.biz> (raw)
In-Reply-To: <1093595310.21861.18.camel@icampbell-debian>

Le 27 Août 2004 04:28, Ian Campbell a écrit :
> > If it helps (because I surely don't understand what's happenning), it is
> > like if the partition structure in the physmap.c was not taken count off.
>
> The example you said had the contents of the partition structure
> definition surrounded with "#if 0" / "#endif". Perhaps you should change
> that to a 1.
I just tried that, and it did'nt work, I still have:

/ # cat /proc/mtd                                                                                                                                       
dev:    size   erasesize  name                                                                                                                          
mtd0: 01000000 00040000 "Physically mapped flash" 

I would really like it if my mtd1,mtd2, etc partitions were working...

> Also make sure you have the CONFIG_MTD_PARTITIONS turned on in your
> config (and CONFIG_MTD_CMDLINE_PARTS for mtdparts= if that's your
> thing).

Yeah, I did that, but I think CONFIG_MTD_CMDLINE_PARTS is giving me some kind 
of error.  When I do a "dmesg" I get this message

physmap flash device: 1000000 at ff000000                                                                                                               
 Amd/Fujitsu Extended Query Table v1.2 at 0x0040                                                                                                        
number of CFI chips: 1                                                                                                                                  
cfi_cmdset_0002: Disabling fast programming due to code brokenness.                                                                                     
mtd: Giving out device 0 to Physically mapped flash                                                                                                     
$Id: ftl.c,v 1.45 2003/01/24 23:31:27 dwmw2 Exp $                                                                                                       
ftl_cs: FTL header not found.                          

As you can see, cfi_cmdset_0002 gets itself disable.  I don't know if this is 
the cause of the problem ?!?

My init string is:
Linux/PPC load: console=ttyS0,9600 nfsroot=10.0.0.2:/exports/823_new 
ip=10.0.0.10 root=/dev/nfs 
mtdparts=physmap:512k(boot)ro,1M(zImage)ro,3M(ramdisk.gz)ro 

I've read many "how to" to get this right, but this is my "best" result.  I 
really don't know what to do next.  This problem is my main reason for 
getting on this mailing-list.  If you have an idea, I'm all ears :-)

Thanks
Raphael

      reply	other threads:[~2004-08-28 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27  6:10 Trouble with mtd partition Ccool
2004-08-27  8:28 ` Ian Campbell
2004-08-28 20:00   ` Ccool [this message]

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=200408281600.36216.ccool@ninjatech.biz \
    --to=ccool@ninjatech.biz \
    --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 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.