From: Dan Malek <dan@netx4.com>
To: Geir Frode Raanes <geirfrs@invalid.ed.ntnu.no>
Cc: Neil Russell <caret@c-side.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Floating Point problems with Linux on the EST SBC8260
Date: Thu, 25 May 2000 13:30:54 -0400 [thread overview]
Message-ID: <392D634E.3328E9C5@embeddededge.com> (raw)
In-Reply-To: Pine.BSF.4.21.0005251319150.9249-100000@invalid.ed.ntnu.no
Geir Frode Raanes wrote:
> You tell me your HW designers can't operate a logic analyzer?
Hardware designers? This is just software and a few wires :-).
> ...... BTW, when you
> already have a full FPGA installed then why waste a UPM?
You know, I keep hearing this question and continually find boards
with external hardware and no one using the integrated control logic.
Everyone is "saving it for something else". Geeze, these are embedded
systems that will probably never change. After I use up all of the
GP I/O and internal control logic, I will start looking for alternatives.
The 8260 is even better. Separate DRAM controllers so you don't even
use up the UPMs for that, more chip selects, more I/O, multiple busses.
You bought it, may as well use it.
> .... But to keep power
> drain low I will probabely use the second PCMCIA port for it
> by means of Xilinx Coolrunner and an AVR for autoconfiguration.
> Then I could (but will not) expand this into a full ISA bus.
Why bother with the Xilinx? Just connect the IDE to the PCMCIA.
I think you could even DMA over the port.
> .... How does PPC/Linux handle this addressing
> problem?
What addressing problem? The 860 supports 32 bits of address, so
does Linux. No problem. I started to add support for multiple real
memory spaces (which isn't hard, you just have to detect it), and then
realized it isn't necessary. With the 8xx memory controller you can
make external RAM one linear space, unless you wire it up really stupid.
> One more - if anyone has the specification for Sony Memorystick
> I would be interested. I am pretty certain that this flashstick
> has a serial interface on it.
Maybe it is similar to the SanDisk MMC interface? That is an SPI
interface, perhaps there is some access standard.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-25 17:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000524134257.A9100@lx.c-side.com>
[not found] ` <m12uikI-001SyaC@bucks>
2000-05-24 22:05 ` Floating Point problems with Linux on the EST SBC8260 Neil Russell
2000-05-24 22:26 ` Dan Malek
2000-05-24 23:06 ` Neil Russell
2000-05-25 1:22 ` Dan Malek
2000-05-25 3:17 ` Neil Russell
2000-05-25 3:45 ` Dan Malek
2000-05-25 12:13 ` Geir Frode Raanes
2000-05-25 17:30 ` Dan Malek [this message]
2000-05-26 10:01 ` Adrian Cox
2000-05-26 12:49 ` Geir Frode Raanes
2000-05-26 13:52 ` Adrian Cox
2000-05-24 23:33 ` diekema_jon
2000-05-25 14:44 Gessner, Matt
2000-05-25 16:52 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-05-24 19:47 diekema_jon
2000-05-24 20:42 ` Bill Roman
2000-05-30 15:36 ` diekema_jon
2000-05-24 20:43 ` Neil Russell
2000-05-24 20:44 ` Neil Russell
2000-05-24 21:31 ` Dan Malek
2000-05-24 23:41 ` diekema_jon
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=392D634E.3328E9C5@embeddededge.com \
--to=dan@netx4.com \
--cc=caret@c-side.com \
--cc=geirfrs@invalid.ed.ntnu.no \
--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).