From: <noreply_at_sourceforge.net>
Date: Sat, 09 Feb 2002 13:10:44 -0800

Feature Requests item #515323, was opened at 2002-02-09 13:10
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=439121&aid=515323&group_id=44306

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: More RAM, & better use of whats there ..

Initial Comment:
* It would be nice if we could read ahead on each disk
access to fill the HD buffer as well as the Archos
DRAM. This way, each new disk access would transfer
would start by reading the previously cached data from
the HD buffer, whilst the HD spins up. Therefore,
there would (potentially) be no skipping due to the HD
spinning up, and it would also reduce skipping due to
physical shock (the HD would have more time to read
data around shocks).

* Further along these lines, it would also be nice if
the firmware checked the existing memory size at boot,
and also scannned any free CS lines for DRAM too.
This would allow the stout of heart to expand thier
DRAM to meet thier needs (it would be a simple matter
to double the DRAM by paralleling another chip on top
of the current DRAM, but connecting it to a different
CS line on the SH-1). NOTE: I may be teaching you
how to suck eggs here, but when scanning a bus for
memory, it is not enough to write one byte/word onto
the bus and then read it back, as bus capacitance will
often hold the last value if there is nothing else
driving the bus. It is better to write out a string
("is there any ram there" ;) and then try to read
that back. If there is no RAM, you'll get the last
written value at best.

----------------------------------------------------------------------

You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=439121&aid=515323&group_id=44306
Received on 2002-02-09