From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] forgot to mention ts7200 is working
Date: Fri, 29 Apr 2005 15:28:23 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0504291526000.23205@enigma.lanl.gov> (raw)
this is the ep93xx core.
it all seems to be working with cache etc. Due to the fact that phsyical
memory is 4 segemnts at present only 16 MB of 32MB is usable.
I'll drop the code on sources in a bit, when I'm sure it's reasonably
reliable. Sorry folks, but the eth driver is derived from linux code,
hence GPL. ah! wail! gnash teeth!
you call can rewrite it if you wish :-)
I also include a modified xalloc.c that lets you allocate "flavors" of
memory, e.g. uncached and cached regions. This may be handy at some point,
esp. when we get to 64-bit machines where at minimum you needed "low 4G"
and "above4G" flavors of memory.
At least I think it will, who knows.
ron
next reply other threads:[~2005-04-29 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 21:28 Ronald G. Minnich [this message]
2005-04-30 5:01 ` Chris Collins
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=Pine.LNX.4.58.0504291526000.23205@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).