From: Alexander Schmidt <alexs-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Hoang-Nam Nguyen
<hnguyen-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Christoph Raisch <raisch-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stefan.roscher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Subject: Re: ehca driver status?
Date: Fri, 11 Sep 2015 10:55:13 +0200 [thread overview]
Message-ID: <20150911105513.4bbf9e9e@worktp> (raw)
In-Reply-To: <20150826134648.GA21814-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Wed, 26 Aug 2015 06:46:48 -0700
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
> Hi Hoang-Nam, hi Christoph, hi Alexander,
>
> do you know what the current state of the eHCA driver and hardware is?
>
> The driver hasn't seen any targeted updats since 2010, so we wonder if
> it's still alive? It's one of the few drivers not supporting FRWRs,
> and it's also really odd in that it has its own dma_map_ops
> implementation that seems to pass virtual addresses to the hardware
> (or probably rather firmware), getting in the way of at least two
> currently pending cleanups.
>
Hi again,
we are okay with removing the driver from the tree, let me know if
there is anything we should do to help.
Regards,
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-11 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 13:46 ehca driver status? Christoph Hellwig
[not found] ` <20150826134648.GA21814-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-08-26 14:34 ` Alexander Schmidt
2015-09-11 8:55 ` Alexander Schmidt [this message]
2015-09-11 15:44 ` Doug Ledford
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=20150911105513.4bbf9e9e@worktp \
--to=alexs-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=hnguyen-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=raisch-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=stefan.roscher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.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).