From: Scott McNutt <smcnutt@psyent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [rfc] new spiflash subsystem
Date: Tue, 29 Jan 2008 05:43:10 -0500 [thread overview]
Message-ID: <479F033E.20307@psyent.com> (raw)
In-Reply-To: <20080129082814.GD8079@game.jcrosoft.org>
>>> How do you do "byte writes" which is an important feature of the AT45?
>> simple: i dont. spi flash writing isnt something to be done constantly nor is
>> it fast, so i dont sweat getting maximum performance.
This is an artificial limitation based on your _opinion_.
How, why, or what someone chooses to write into spi flash
should not be constrained by design.
>>> Your code does not support DMA transfers, while the current dataflash code
>>> runs DMA up to 50 Mbps.
>> so ? the point of u-boot is to do everything in PIO mode.
This is also an opinion -- that I happen to disagree with.
>>
>>> Erasing the entire SPI flash is generally stupid, since you store the
>>> environment there. You typically also store the initial bootloader and
>>> U-Boot.
>> so the user is stupid if they erase the entire flash ? you could say the same
>> thing about any flash type.
>>
I have valid reasons, better _requirements_, for erasing an
entire spi flash and have done so many times. I never realized
that I was stupid ... and for all these years! ;-)
>>> Very rarely you want to erase the complete flash ,and a protection
>>> mechanism is needed to avoid accidental overwrites.
>>> The current solution allows dataflash pages to be protected.
>
> I disagree on some product you use a spi flash to store other code and
> not nessarely store u-boot in it? (you can have 2 falsh)
Ditto -- I also disagree.
>> execute something else. it isnt an operating system, it doesnt get maximal
>> performance, and it isnt supposed to support all sorts of extended features.
What it's _supposed_ to support can be debated. But I'm quite
sure that preventing extended features is not a good thing to
design into a subsystem from the outset.
>> what you describe as deficiency doesnt apply to the topic at hand and really
>> sounds like a basic design decision for u-boot. if you want optimal
>> performance, use Linux.
The pot is calling the kettle black here -- WRT basic design decisions.
If I want optimal performance, I shouldn't have to find an alternative
to u-boot simply because a subsystem prevents me from doing so by
design.
I think many of the comments/suggestions in this email topic have been
sound and raise some valid issues/concerns -- this is a good thing.
Regards,
--Scott
next prev parent reply other threads:[~2008-01-29 10:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 20:00 [U-Boot-Users] [rfc] new spiflash subsystem Mike Frysinger
2008-01-28 23:01 ` Ulf Samuelsson
2008-01-29 0:41 ` Mike Frysinger
2008-01-29 7:35 ` Ulf Samuelsson
2008-01-29 9:49 ` Haavard Skinnemoen
2008-01-29 14:07 ` Mike Frysinger
2008-01-30 0:39 ` Ulf Samuelsson
2008-01-30 0:51 ` Mike Frysinger
2008-01-30 7:35 ` Haavard Skinnemoen
2008-01-30 13:05 ` Mike Frysinger
2008-01-29 22:40 ` Wolfgang Denk
2008-01-29 22:42 ` Wolfgang Denk
2008-01-30 0:39 ` Ulf Samuelsson
2008-01-30 8:56 ` Wolfgang Denk
2008-01-30 9:34 ` Ulf Samuelsson
2008-01-30 23:48 ` Wolfgang Denk
2008-01-29 8:28 ` Jean-Christophe PLAGNIOL-VILLARD
2008-01-29 10:43 ` Scott McNutt [this message]
2008-01-30 0:16 ` Ulf Samuelsson
2008-01-29 22:32 ` Wolfgang Denk
2008-01-28 23:26 ` Haavard Skinnemoen
2008-01-29 0:29 ` Mike Frysinger
2008-01-29 9:12 ` Haavard Skinnemoen
2008-01-29 14:13 ` Mike Frysinger
2008-01-29 21:06 ` Haavard Skinnemoen
2008-01-29 0:44 ` Ben Warren
2008-01-29 9:14 ` Haavard Skinnemoen
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=479F033E.20307@psyent.com \
--to=smcnutt@psyent.com \
--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