public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Joseph M Dupre (AVAB Inc.)" <dupre@avab.com>
To: linux-mtd@lists.infradead.org
Cc: Dan Brown <dan_brown@ieee.org>
Subject: Re: docboot: nandwrite:  Input file is not page aligned
Date: Tue, 11 Oct 2005 14:44:25 -0700	[thread overview]
Message-ID: <434BCFC9.20808.127FE1D@localhost> (raw)
In-Reply-To: <434BFE23.4060701@ieee.org>

On 11 Oct 2005 at 14:02, Dan Brown wrote:

> ./mtd_debug info /dev/mtd1
> 
> Could you send me the output from that?  On my DOC device it says
> (among other things):
> 
> mtd.erasesize = 16384 (16K)
> mtd.oobblock = 512
> mtd.oobsize = 16
> 
> If you get the same result, then we're in really weird territory, and
> I'd start to wonder if the mtd tools just don't build (or run)
> properly under uClibc.  Is there any chance you can use a standard
> glibc environment to doublecheck?

I get this output for 'mtd_debug info /dev/mdt1':

mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CLEAR_BITS | MTD_ERASEABLE | MTD_OOB | MTD_ECC
mtd.size = 10567680 (10M)
mtd.erasesize = 16384 (16K)
mtd.oobblock = 512 
mtd.oobsize = 16 
mtd.ecctype = MTD_ECC_SW
regions = 0

Yes I think can set up a clean glibc system on this hardware to test. 
I had a Linux From Scratch system up and running at one time.  If I 
can only find it now...

- Joe

  reply	other threads:[~2005-10-11 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11  0:04 docboot: nandwrite: Input file is not page aligned Joseph M Dupre (AVAB Inc.)
2005-10-11 13:42 ` Dan Brown
2005-10-11 17:49   ` Joseph M Dupre (AVAB Inc.)
2005-10-11 18:02     ` Dan Brown
2005-10-11 21:44       ` Joseph M Dupre (AVAB Inc.) [this message]
2005-10-13 16:44       ` Joseph M Dupre (AVAB Inc.)
2005-10-21 17:45       ` Joseph M Dupre (AVAB Inc.)
2005-10-24 13:15         ` Dan Brown

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=434BCFC9.20808.127FE1D@localhost \
    --to=dupre@avab.com \
    --cc=dan_brown@ieee.org \
    --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