From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Schmidt
<alexs-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
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 11:44:06 -0400 [thread overview]
Message-ID: <55F2F6C6.8060002@redhat.com> (raw)
In-Reply-To: <20150911105513.4bbf9e9e@worktp>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On 09/11/2015 04:55 AM, Alexander Schmidt wrote:
> 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.
I'll get it moved over to staging ASAP so it can be on the same schedule
as the other two drivers we are deprecating. Thanks!
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2015-09-11 15:44 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
2015-09-11 15:44 ` Doug Ledford [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=55F2F6C6.8060002@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=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).