From: "Michael Meriin" <Michael@KSWaves.com>
To: "Chuck Partridge" <Chuck_Partridge@amx.com>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: AMD Flash Interface for updating boot flash
Date: Wed, 26 Jun 2002 18:17:12 +0200 [thread overview]
Message-ID: <019701c21d2c$edde98b0$3c0fa8c0@amitesting> (raw)
In-Reply-To: sd199301.035@mx.amx.com
Just define your flash as a MTD device and then, from user space use dd
command to copy your bootloader to flash:
dd if=bootloader of=/dev/mtdblock0
Best Regards,
Michael Meriin
----- Original Message -----
From: "Chuck Partridge" <Chuck_Partridge@amx.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, June 26, 2002 17:09
Subject: AMD Flash Interface for updating boot flash
>
> Hello all,
>
> I have been searching the archives and I am a bit confused, so bear with
me if this is too simple a question.
>
> I need to provide a way to update my boot flash from user space.
> Our user application will download an boot flash image and save it (to a
file or a buffer), we must then write the flash.
> I have seen references in the archives to Denx's drivers/char/amd_flash.c
and to MTD drivers, or I can
> implement my own driver, but I'm not sure of the best (i.e. easiest and
cleanest) way.
>
> I don't need to put a file system on the flash. All it does is hold the
PPCBoot image. The flash part is an AMD
> 29LV004B and is setup for 8 bit interface. I am running a 2.4.17 kernel
on an 8245.
>
> Any suggestions?
>
> Thanks,
>
> Chuck
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-26 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 15:09 AMD Flash Interface for updating boot flash Chuck Partridge
2002-06-26 16:17 ` Michael Meriin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 19:49 Jan.Rovins
2002-06-26 20:23 Chuck Partridge
2002-06-26 21:02 ` Wolfgang Grandegger
2002-06-26 23:00 Jan.Rovins
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='019701c21d2c$edde98b0$3c0fa8c0@amitesting' \
--to=michael@kswaves.com \
--cc=Chuck_Partridge@amx.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).