From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
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
Date: Tue, 27 Jun 2017 21:08:53 +0200 [thread overview]
Message-ID: <20170627190853.GX21846@wotan.suse.de> (raw)
In-Reply-To: <20170627185915.GK18666@tuxbook>
On Tue, Jun 27, 2017 at 11:59:15AM -0700, Bjorn Andersson wrote:
> 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?
Hell No! You can fork firmwared or use whatever the hell bin-foo you want.
Even if its proprietary and glued with evil rainbow unicorns on it. The dual
mode, best-effort mode and final-mode devices it implemented are key to what
you want to mimic as an example to achieve the goal in question.
Please give that thought / architecture solution a spin and let me know if
it suffices for your needs.
Luis
next prev parent reply other threads:[~2017-06-27 19:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 23:37 [PATCH] firmware: wake all waiters Jakub Kicinski
2017-06-26 21:20 ` Luis R. Rodriguez
2017-06-26 21:23 ` [PATCH v2] firmware: fix batched requests - " Luis R. Rodriguez
2017-06-29 15:16 ` Greg KH
2017-06-29 15:17 ` Greg KH
2017-06-29 17:36 ` Luis R. Rodriguez
2017-06-26 23:41 ` [PATCH] firmware: " Luis R. Rodriguez
2017-06-27 2:10 ` Jakub Kicinski
2017-06-27 16:39 ` Luis R. Rodriguez
2017-06-27 21:25 ` Jakub Kicinski
2017-06-27 22:24 ` Luis R. Rodriguez
2017-06-27 22:39 ` Jakub Kicinski
2017-06-27 23:50 ` Luis R. Rodriguez
2017-06-28 7:06 ` [systemd-devel] " Lennart Poettering
2017-06-28 16:06 ` Luis R. Rodriguez
2017-06-28 16:21 ` Lennart Poettering
2017-06-28 17:57 ` Luis R. Rodriguez
2017-06-29 19:56 ` Daniel Wagner
2017-06-27 17:48 ` Bjorn Andersson
2017-06-27 18:03 ` Luis R. Rodriguez
2017-06-27 18:59 ` Bjorn Andersson
2017-06-27 19:08 ` Luis R. Rodriguez [this message]
2017-06-27 19:52 ` Bjorn Andersson
2017-06-27 20:24 ` Luis R. Rodriguez
2017-06-26 21:44 ` Linus Torvalds
2017-06-26 23:30 ` Luis R. Rodriguez
2017-06-26 23:43 ` Linus Torvalds
2017-06-27 0:15 ` Luis R. Rodriguez
2017-06-28 13:45 ` Davidlohr Bueso
2017-06-28 15:58 ` Luis R. Rodriguez
2017-06-28 19:03 ` Davidlohr Bueso
2017-06-29 19:08 ` Davidlohr Bueso
2017-06-29 19:48 ` Luis R. Rodriguez
2017-06-30 16:32 ` Davidlohr Bueso
2017-07-05 16:18 ` Peter Zijlstra
2017-07-05 16:33 ` Linus Torvalds
2017-07-12 18:45 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170627190853.GX21846@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=alan@linux.intel.com \
--cc=arend.vanspriel@broadcom.com \
--cc=atull@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dhowells@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ebiederm@xmission.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jakub.kicinski@netronome.com \
--cc=jewalt@lgsinnovations.com \
--cc=johannes.berg@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=luto@kernel.org \
--cc=markivx@codeaurora.org \
--cc=mawilcox@microsoft.com \
--cc=mfuzzey@parkeon.com \
--cc=ming.lei@redhat.com \
--cc=moritz.fischer@ettus.com \
--cc=mtosatti@redhat.com \
--cc=nbroeking@me.com \
--cc=oss-drivers@netronome.com \
--cc=paul.gortmaker@windriver.com \
--cc=pjones@redhat.com \
--cc=pmladek@suse.com \
--cc=rafal@milecki.pl \
--cc=rjw@rjwysocki.net \
--cc=stephen.boyd@linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=wagi@monom.org \
--cc=yi1.li@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).