From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ale.deltatee.com (ale.deltatee.com. [207.54.116.67]) by gmr-mx.google.com with ESMTPS id y25si386601uaa.2.2017.11.27.19.02.35 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 27 Nov 2017 19:02:36 -0800 (PST) Message-ID: <5A1CD1A7.5040104@deltatee.com> Date: Mon, 27 Nov 2017 20:01:59 -0700 From: Logan Gunthorpe MIME-Version: 1.0 References: <37fc41d9-5191-6f41-fd65-e175f0c661fa@deltatee.com> <0557295a-c60c-4aff-95ec-cb93296066ce@googlegroups.com> <87e0fa6c-025c-d5b6-b683-dbb6be9cb115@deltatee.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Ntb Transport Driver Problem After Power-up To: Karl Kao , linux-ntb List-ID: On 2017-11-27 7:16 PM, Karl Kao wrote: > I meant to say the "peer" which was suddenly powered off. Once the > "peer" is being reset or power cycled, the peer's hardware chip is > supposed to be reset, correct There's only one hardware chip in an NTB configuration. If you reset it, you reset all the peers (which you do not want to do). Logan