From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Schmidt Subject: Re: ehca driver status? Date: Fri, 11 Sep 2015 10:55:13 +0200 Message-ID: <20150911105513.4bbf9e9e@worktp> References: <20150826134648.GA21814@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150826134648.GA21814-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Christoph Hellwig Cc: Hoang-Nam Nguyen , Christoph Raisch , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, stefan.roscher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Wed, 26 Aug 2015 06:46:48 -0700 Christoph Hellwig 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