Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030348Ab2JSNpj (ORCPT ); Fri, 19 Oct 2012 09:45:39 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:44718 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964837Ab2JSNpi (ORCPT ); Fri, 19 Oct 2012 09:45:38 -0400 MIME-Version: 1.0 Date: Fri, 19 Oct 2012 15:45:36 +0200 Message-ID: Subject: remoteproc open issues (was [RFC 1/4] remoteproc: Bugfix assign device address to carveout (noiommu) From: =?UTF-8?Q?Sjur_Br=C3=A6ndeland?= To: Ohad Ben-Cohen , Omar Ramirez Luna , Fernando Guzman Lugo , Suman Anna , Bhavin Shah , Stephen Boyd , Loic Pallardy , Ludovic BARRE Cc: linux-kernel@vger.kernel.org, Linus Walleij Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1237 Lines: 31 Hi, On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen wrote: > The general direction I have in mind is to put the resource table in > its final location while we do the first pass of fw parsing. > > This will solve all sort of open issues we have (or going to have soon): > > 1. dynamically-allocated address of the vrings can be communicated > 2. vdev statuses can be communicated > 3. virtio config space will finally become bi-directional as it should > 4. dynamically probed rproc-to-rproc IPC could then take place > > It's the real deal :) > > The only problem with this approach is that the resource table isn't > reloaded throughout cycles of power up/down, and that is insecure. > We'll have to manually reload it somewhere after the rproc is powered > down (or before it is powered up again). > > This change will break existing firmwares, but it looks required and inevitable. Has anyone started looking into any of the open issues mentioned above? Thanks, Sjur -- 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/