Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934386Ab1FWSro (ORCPT ); Thu, 23 Jun 2011 14:47:44 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:58751 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932831Ab1FWSrm (ORCPT ); Thu, 23 Jun 2011 14:47:42 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 0/8] Introducing a generic AMP/IPC framework Date: Thu, 23 Jun 2011 20:46:35 +0200 User-Agent: KMail/1.13.6 (Linux/3.0.0-rc1nosema+; KDE/4.6.3; x86_64; ; ) Cc: "Grosen, Mark" , Michael Williamson , "Ohad Ben-Cohen" , "davinci-linux-open-source" , Brian Swetland , Rusty Russell , "linux-kernel@vger.kernel.org" , Grant Likely , "akpm@linux-foundation.org" , "linux-omap@vger.kernel.org" , Subhasish Ghosh References: <1308640714-17961-1-git-send-email-ohad@wizery.com> <4E033041.9090606@criticallink.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106232046.35846.arnd@arndb.de> X-Provags-ID: V02:K0:faOFNApiJF98nhZH1jIj2EpeEtMh/wF3b0D+Sv+Svfv XyE2IqAgBBZjifm/f79YbbpEGdqXSjmqLc6Gy14jvqrF2UgxnQ BGYwlsia3vdddvnl0M8mTCZFNa7FH0mpzd7h8HjEjq1QCq4ASA k2CC2Cz+X3QOq6yGL34f7G7uiDE7nfpEAX2UlJpSjV8ThjCkou jOo62DRYYra3KlCKJlLiw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1047 Lines: 20 On Thursday 23 June 2011 18:27:10 Grosen, Mark wrote: > First, we are not abandoning DSPLINK. We have many users of this, even > though it is out-of-tree, and we will continue to support it. That said, we > do intend to make this new design the basis for DSPLINK-like > functionality. It's designed to be done "the right way" for Linux (and we > are looking for feedback to make it better). It is also designed to be more > scalable and extensible in userspace. With a solid kernel foundation, we can > provide lots of functionality in userspace, or users can implement their own > custom solutions. One of the key things to do is map our existing DSPLINK > APIs, like MessageQ, to the new rpmsg transport. Sounds all good. What about the PRUSS code? Does that fit into the new model as well? Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/