From: "Kevin D. Kissell" <kevink@mips.com>
To: jeff@garzik.org
Cc: netdev@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: Patch to add M3Pnet Driver
Date: Tue, 17 Jun 2008 15:40:43 +0200 [thread overview]
Message-ID: <4857BEDB.8080603@mips.com> (raw)
In-Reply-To: <4836F40C.804@mips.com>
Jeff,
Ralf and I never heard back from you on this one. Have you had
a chance to think about it yet?
Regards,
Kevin K.
Kevin D. Kissell wrote:
> Guysm
>
> Yet another network driver is probably not what the world needs most,
> but I had to write one for MIPS Linux this month that was a little
> different from any of the others. It's a driver that impersonates
> an ethernet interface whilst actually passing packets in memory between
> different processors running different OS images in a shared memory
> environment, something that actually happens in embedded systems.
> I call it M3P (pronounced "mep"), for MIPS Memory Message Passing,
> but if I didn't think it could be adapted to non-MIPS based and indeed
> heterogeneous systems, I wouldn't trouble you with it. I note that
> the "mipsnet" driver, which is limited in its function to running
> on a MIPS simulator, made it in, so I figured I'd at least ask if
> it's something that could be absorbed into the network driver mass,
> the better for other folks to improve on it - there are a lot of
> enhancements I'd like to make, some of which are described in the
> comments, but it's not clear that I'll have time to make them any
> time soon. A familiar refrain, I suppose. Anyway, the patch is
> attached. See also Ralf's ack below.
>
> Regards,
>
> Kevin K.
>
> Ralf Baechle wrote:
>> On Fri, May 23, 2008 at 12:45:45AM +0200, Kevin D. Kissell wrote:
>>> From: "Kevin D. Kissell" <kevink@mips.com>
>>> Date: Fri, 23 May 2008 00:45:45 +0200
>>> To: Linux MIPS Org <linux-mips@linux-mips.org>
>>> Subject: Patch to add M3Pnet Driver
>>> Content-Type: multipart/mixed;
>>> boundary="------------050707080700070300010401"
>>>
>>> As per previous messages, here's 2 of 2
>>
>> This is largely a network driver patch with minor arch bits thrown in so
>> this one will have to go via jeff@garzik.org and netdev@vger.kernel.org.
>> The MIPS bits are looking good though so feel free to add my
>>
>> Acked-by: Ralf Baechle <ralf@linux-mips.org>
>>
>> line for them.
>>
>> Ralf
>
prev parent reply other threads:[~2008-06-17 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4835F799.6070302@mips.com>
[not found] ` <20080523023623.GA17651@linux-mips.org>
2008-05-23 16:42 ` Patch to add M3Pnet Driver Kevin D. Kissell
2008-06-17 13:40 ` Kevin D. Kissell [this message]
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=4857BEDB.8080603@mips.com \
--to=kevink@mips.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@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;
as well as URLs for NNTP newsgroup(s).