Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753407AbdF0S71 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 27 Jun 2017 14:59:27 -0400
Received: from mail-pf0-f182.google.com ([209.85.192.182]:36086 "EHLO
        mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752672AbdF0S7W (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 27 Jun 2017 14:59:22 -0400
Date: Tue, 27 Jun 2017 11:59:15 -0700
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
        Ming Lei <ming.lei@redhat.com>, yi1.li@linux.intel.com,
        "AKASHI, Takahiro" <takahiro.akashi@linaro.org>, nbroeking@me.com,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>, mfuzzey@parkeon.com,
        ebiederm@xmission.com, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        Daniel Wagner <wagi@monom.org>, David Woodhouse <dwmw2@infradead.org>,
        jewalt@lgsinnovations.com, rafal@milecki.pl,
        Arend van Spriel <arend.vanspriel@broadcom.com>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>, atull@kernel.org,
        Moritz Fischer <moritz.fischer@ettus.com>, pmladek@suse.com,
        Johannes Berg <johannes.berg@intel.com>, emmanuel.grumbach@intel.com,
        Luca Coelho <luciano.coelho@intel.com>, luto@kernel.org,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Kees Cook <keescook@chromium.org>, David Howells <dhowells@redhat.com>,
        pjones@redhat.com, Hans de Goede <hdegoede@redhat.com>,
        alan@linux.intel.com, "Theodore Ts'o" <tytso@mit.edu>,
        paul.gortmaker@windriver.com, mtosatti@redhat.com,
        mawilcox@microsoft.com, Stephen Boyd <stephen.boyd@linaro.org>,
        Vikram Mulukutla <markivx@codeaurora.org>,
        lkml <linux-kernel@vger.kernel.org>, oss-drivers@netronome.com
Subject: Re: [PATCH] firmware: wake all waiters
Message-ID: <20170627185915.GK18666@tuxbook>
References: <20170623233702.20564-1-jakub.kicinski@netronome.com>
 <20170626212036.GE21846@wotan.suse.de>
 <20170626191009.0c11eed0@cakuba.netronome.com>
 <CAOCOHw4GtC-7OM0g4wLAeOqYsJgQd-mTnBjqLMP9n_x06a8LqQ@mail.gmail.com>
 <20170627180341.GT21846@wotan.suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170627180341.GT21846@wotan.suse.de>
User-Agent: Mutt/1.8.2 (2017-04-18)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1118
Lines: 25

On Tue 27 Jun 11:03 PDT 2017, Luis R. Rodriguez wrote:
[..]
> Let's consider a crazy case where the uevent gets triggered, and userspace goes
> and signals Elon Musk somehow to transmit the needed firmware from Mars through
> a serial satellite link to earth, and somehow someday the device is finally
> ready to upload firmware from userspace. Once Elon's firmware lands home, we
> know all needed firmware has arrived so anything missing we can acknowledge now
> as missing, so we upload what we can and kick firmward into final-mode to tell
> the kernel we know we're really ready and any pending things will have to be
> given up.
> 
> This would prove the custom fallback crap was also never needed.
> 

Are you saying that each kernel driver should be written so that it will
either do direct loading or use firmwared?


>From the previous discussion Linus made it very clear that he expect
this driver to be compiled as a kernel module and Elon to issue a
modprobe once he lands. But IMHO, Elon's decision of using modprobe vs
firmwared should be his to make and not mine as a kernel developer.

Regards,
Bjorn