public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Doug Warzecha <Douglas_Warzecha@dell.com>
Cc: Michael Brown <mebrown@michaels-house.net>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Matt Domsch <Matt_Domsch@dell.com>
Subject: Re: Class device namespaces
Date: Tue, 28 Apr 2009 21:06:03 +0200	[thread overview]
Message-ID: <20090428210603.604a6586@hyperion.delvare> (raw)
In-Reply-To: <20090428173929.GA5006@sysman-doug.us.dell.com>

Hi Doug,

On Tue, 28 Apr 2009 12:39:29 -0500, Doug Warzecha wrote:
> On Tue, Apr 28, 2009 at 10:10:20AM +0200, Jean Delvare wrote:
> > On Mon, 27 Apr 2009 12:23:30 -0500, Michael Brown wrote:
> > > On Mon, Apr 27, 2009 at 10:27 AM, Jean Delvare <khali@linux-fr.org> wrote:
> > > > The question was: any change to _which_ paths exactly? Sysfs often
> > > > offers several ways to reach the same object, and it matters to know
> > > > which need to be preserved and which can change.
> > > >
> > > > const char *rbu_v2_fw_data_file = "/sys/class/firmware/dell_rbu/data";
> > > > const char *rbu_v2_fw_load_file = "/sys/class/firmware/dell_rbu/loading";
> > > > const char *rbu_v2_img_type_file = "/sys/devices/platform/dell_rbu/image_type";
> > > > const char *rbu_v2_pkt_size_file = "/sys/devices/platform/dell_rbu/packet_size";
> > > >
> > > > I guess that noawadays v2 applies, so the only path which needs to be
> > > > preserved is "/sys/class/firmware/dell_rbu". Is that correct? Is it the
> > > > same for srvadmin-hap?
> > > 
> > > You are correct WRT libsmbios. For hapi, I've cc'd Doug who can tell
> > > you about their code. I've done a quick grep of their code, and the
> > > paths above look like the same ones he is using, but I could be wrong.
> > > 
> > > hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> > > HBAS_RBU_SYSFS_NEW_DATAREAD_PFNAME		"/sys/devices/platform/dell_rbu/data"
> > > hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> > > HBAS_RBU_SYSFS_NEW_IMAGETYPE_PFNAME		"/sys/devices/platform/dell_rbu/image_type"
> > > hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> > > HBAS_RBU_SYSFS_NEW_PKTSIZE_PFNAME		"/sys/devices/platform/dell_rbu/packet_size"
> > 
> > This doesn't make use of the firmware class at all, so I guess it won't
> > be affected by any change to the firmware class?
> > 
> 
> Dell makes use of the following dell_rbu paths:
> 
> /sys/class/firmware/dell_rbu/loading
> /sys/class/firmware/dell_rbu/data
> /sys/devices/platform/dell_rbu/data
> /sys/devices/platform/dell_rbu/image_type
> /sys/devices/platform/dell_rbu/packet_size

Thanks for the clarification, which confirms my earlier findings.

-- 
Jean Delvare

      parent reply	other threads:[~2009-04-28 19:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 15:48 Class device namespaces Jean Delvare
2009-03-29 16:36 ` Kay Sievers
2009-03-30  8:49   ` Jean Delvare
2009-03-30 11:24     ` Kay Sievers
2009-04-26  6:54       ` Jean Delvare
2009-04-26 12:44         ` Matt Domsch
2009-04-26 13:01           ` Matt Domsch
2009-04-27 15:30             ` Jean Delvare
2009-04-27 17:30               ` Matt Domsch
2009-04-26 13:42         ` Kay Sievers
2009-04-27 16:00           ` Jean Delvare
2009-04-27 21:57             ` Kay Sievers
2009-04-28  8:08               ` Jean Delvare
2009-04-28 12:36                 ` Kay Sievers
2009-04-29 12:19                   ` Jean Delvare
2009-04-27 13:20         ` Michael E Brown
2009-04-27 15:27           ` Jean Delvare
2009-04-27 17:23             ` Michael Brown
2009-04-28  8:10               ` Jean Delvare
2009-04-28 17:39                 ` Doug Warzecha
2009-04-28 17:46                   ` Kay Sievers
2009-04-28 21:58                     ` Doug Warzecha
2009-04-29  1:42                       ` Kay Sievers
2009-04-29  3:19                         ` Michael Brown
2009-04-29 10:30                           ` Kay Sievers
2009-04-29 17:00                             ` Michael Brown
2009-04-29 19:10                               ` Kay Sievers
2009-04-29 21:28                                 ` Michael Brown
2009-04-29 21:53                                   ` Kay Sievers
2009-04-30 15:18                                     ` David Dillow
2009-04-30 16:34                                       ` Kay Sievers
2009-04-28 19:06                   ` Jean Delvare [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=20090428210603.604a6586@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=Douglas_Warzecha@dell.com \
    --cc=Matt_Domsch@dell.com \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mebrown@michaels-house.net \
    /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