All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@canonical.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/2] Expose firmware paths via procfs
Date: Wed, 10 Oct 2012 23:14:36 +0800	[thread overview]
Message-ID: <CACVXFVMvq-OoLOowds-4-PGyrtmZW2oAQATiTonJs7LvWc1aCA@mail.gmail.com> (raw)
In-Reply-To: <1349866585-24883-1-git-send-email-dp@opensource.wolfsonmicro.com>

On Wed, Oct 10, 2012 at 6:56 PM, Dimitris Papastamos
<dp@opensource.wolfsonmicro.com> wrote:
> Hi all, sorry missed the relevant CCs before.  This patch set
> adds support for exposing the firmware paths via procfs.  I've added
> an entry named /proc/fw_path which is a whitespace separated list
> of firmware paths.

Looks the paths are hard-coded in udev and mdev, which don't
export these paths to users , so I am wondering if users are interested
in the information.  But it is surely better to document the default
search paths.

Do you have some good use case about retrieving the info
at runtime?

>
> Once I have some time I hope to also send out a patch that allows
> the user to dynamically configure these paths.

IMO, kernel parameter should be an appropriate way to configure
the path, and the way of /proc or /sys may be a bit late.


Thanks,
--
Ming Lei

      parent reply	other threads:[~2012-10-10 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 10:56 [PATCH 0/2] Expose firmware paths via procfs Dimitris Papastamos
2012-10-10 10:56 ` [PATCH 1/2] firmware: Convert firmware path setup from an array to a list Dimitris Papastamos
2012-10-22 15:42   ` Greg Kroah-Hartman
2012-10-23  9:43     ` Dimitris Papastamos
2012-10-10 10:56 ` [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths Dimitris Papastamos
2012-10-10 13:36   ` Greg Kroah-Hartman
2012-10-10 13:40     ` Josh Boyer
2012-10-10 13:45     ` Dimitris Papastamos
2012-10-10 14:41     ` Dimitris Papastamos
2012-10-10 15:14 ` Ming Lei [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=CACVXFVMvq-OoLOowds-4-PGyrtmZW2oAQATiTonJs7LvWc1aCA@mail.gmail.com \
    --to=ming.lei@canonical.com \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.