All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: Tom Gundersen <teg@jklm.no>, "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Abhay Salunke" <abhay_salunke@dell.com>,
	"Cristian Rodríguez" <crrodriguez@opensuse.org>,
	"Takashi Iwai" <tiwai@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	"systemd Mailing List" <systemd-devel@lists.freedesktop.org>,
	"Hayes, Stuart" <Stuart_Hayes@dell.com>,
	"Singh, B B" <B_B_Singh@dell.com>
Subject: Re: dell rbu driver and FW_LOADER_USER_HELPER
Date: Tue, 26 Aug 2014 12:40:21 -0500	[thread overview]
Message-ID: <53FCC685.8060305@dell.com> (raw)
In-Reply-To: <CAG-2HqULGgC5ftNKOML4XJZ5v_1b+z0t92nctTh7RB2tniRb9Q@mail.gmail.com>


On 08/26/2014 12:20 PM, Tom Gundersen wrote:
> On Tue, Aug 26, 2014 at 7:14 PM, Luis R. Rodriguez<mcgrof@suse.com>  wrote:
> The rework is now upstream, but not yet released [1].
>
> The dell driver dose not use rely on udev in userspace, nor the
> /lib/firmware path. It has its own userspace component, which just
> happens to reuse some of the infrastructure the udev firmware helper
> used to use. This has now been split up, and as of 3.17 the firmware
> loader can safely be removed from udev.
>
> [1]:<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5a1379e8748a5cfa3eb068f812d61bde849ef76c>
Loop in Stuart Hayes and BB Singh.  RBU support is primarily used/supported on poweredge today, and they should be able to help comment and sort this out.

      reply	other threads:[~2014-08-26 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140826170946.GP3347@wotan.suse.de>
2014-08-26 17:14 ` dell rbu driver and FW_LOADER_USER_HELPER Luis R. Rodriguez
2014-08-26 17:20   ` Tom Gundersen
2014-08-26 17:40     ` Mario Limonciello [this message]

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=53FCC685.8060305@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=B_B_Singh@dell.com \
    --cc=Stuart_Hayes@dell.com \
    --cc=abhay_salunke@dell.com \
    --cc=crrodriguez@opensuse.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=teg@jklm.no \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.