From: Hamid IKDOUMI <hikdoumi@atmel.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] DataFlash for AT91RM9200DK board
Date: Wed, 4 Jun 2003 15:26:28 +0200 [thread overview]
Message-ID: <001201c32a9c$e82290b0$90f59f0a@pc0709> (raw)
In-Reply-To: <20030604115316.DDF12C5492@atlas.denx.de>
Ok!
We will modify the plug the dataflash functions in the cmd_mem.c file and
add the dataflash info
in the flinfo command.
Best regards,
-----Original Message-----
From: wd@denx.de [mailto:wd at denx.de]
Sent: mercredi 4 juin 2003 13:53
To: hikdoumi at atmel.fr
Cc: 'Nicolas Lacressonni?re'; 'u-boot Mailing List'; 'Olivier Debicki'
Subject: Re: [U-Boot-Users] [PATCH] DataFlash for AT91RM9200DK board
In message <000d01c32a8d$a615aea0$90f59f0a@pc0709> you wrote:
>
> I'm working with Nicholas on the dataflash driver for U-Boot.
> The dataflash is used to store big amount of data(up to 128 Mbits for the
> AT45DB128).
OK, so my understanding was correct.
> In our case, we use it to store and boot an image of linux(the dataflash
> contains the linux zImage and the ramdisk).
> This dataflash can be used also for a filesystem.
In this case I think we should offer an interface which looks to the user
like mmeory.
Instead of providing separate commands to read and write from such
"memory" I think we should integrate this into the existing code.
For example, writing to "normal" flash memory is an implicit
operation to the "cp" (copy) command when it detects that the target
address is in flash memory.
The same should be done for dataflash.
OK, with "normal" flash memory we don't have to special-case read
accesses like used by "md" or "bootm" commands - where in case of
dataflash such handling will be necessary.
But especially if you boot Linux from dataflash it seems more logical
to me to use "bootm" directly instead of using "dataflash read" +
"bootm" in separate steps.
Do you t hink tis is feasible?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
In general, they do what you want, unless you want consistency.
- Larry Wall in the perl man page
next prev parent reply other threads:[~2003-06-04 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 15:30 [U-Boot-Users] [PATCH] DataFlash for AT91RM9200DK board Nicolas Lacressonnière
2003-06-03 16:56 ` Wolfgang Denk
2003-06-04 8:00 ` Nicolas Lacressonnière
2003-06-04 9:56 ` Wolfgang Denk
2003-06-04 11:37 ` Hamid IKDOUMI
2003-06-04 11:53 ` Wolfgang Denk
2003-06-04 13:26 ` Hamid IKDOUMI [this message]
2003-06-11 9:36 ` Nicolas Lacressonnière
2003-06-16 22:19 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-11-12 9:07 Nicolas Lacressonnière
2003-12-06 23:56 ` Wolfgang Denk
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='001201c32a9c$e82290b0$90f59f0a@pc0709' \
--to=hikdoumi@atmel.fr \
--cc=u-boot@lists.denx.de \
/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