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: Thu, 13 Oct 2005 09:44:35 -0700 [thread overview]
Message-ID: <434E2C83.15605.52E248@localhost> (raw)
In-Reply-To: <434BFE23.4060701@ieee.org>
On 11 Oct 2005 at 14:02, Dan Brown wrote:
> >I am using the uClibc "Buildroot" toolchain. Dev machine is i686 and
> > target is i486 with a DOC 2000 (MD2202-D128)
> Well, I guess the next step is to examine the code in nandwrite
> carefully.
> 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?
Dan,
I was just now successful in writing doc_spl to the device using
nandwrite generated with glibc-2.2.5 on a RedHat 7.3 partition.
So, evidently there is a problem with the uClibc libraries and
nandwrite, although there are no errors or warnings generated when
compiling with uClibc.
I am just learning C, so I won't be very useful in examining the
nandwrite code "carefully". Perhaps you could suggest some 'talking
points' I could bring up with the uClibc people.
- Joe
next prev parent reply other threads:[~2005-10-13 16:47 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.)
2005-10-13 16:44 ` Joseph M Dupre (AVAB Inc.) [this message]
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=434E2C83.15605.52E248@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