From: "Kevin D. Kissell" <kevink@mips.com>
To: Linux MIPS Org <linux-mips@linux-mips.org>
Subject: Still More MIPS 34K APRP Patches
Date: Fri, 23 May 2008 00:42:37 +0200 [thread overview]
Message-ID: <4835F6DD.4090409@mips.com> (raw)
This message will be followed by a couple more patches
to the APRP support for the 34K. The first fixes a few
bugs (minor memory leak, some ELF loader failure cases)
and reorganizes functions so as to allow for more than
just the RTLX service for run-time support. This assumes
that the 0001-Rewrite-of-APRP-VPE-ELF-Loader.patch patch
that I sent out on May 3 has already been applied.
The second patch adds a new driver to drivers/net,
along with some platform support in
arch/mips/mips-boards/generic. I call this a M3P
(pronounced "mehp") driver, for MIPS Memeory Message
Passing. It creates a ethernet-compatible networking
interface between Linux and the RP. With a little more
work, it could also be used for message passing between
Linux and other OSes in a software-heterogeneous SMP
environment. Dropping it into drivers/net will make
it harder to propagate, but the more narrowly specialized
mipsnet driver is already there, and in principle the
driver module could have the remaining MIPSisms filed
off and become useful in heterogeneous multiprocessors.
Regards,
Kevin K.
reply other threads:[~2008-05-22 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4835F6DD.4090409@mips.com \
--to=kevink@mips.com \
--cc=linux-mips@linux-mips.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