From: Patrick Mochel <mochel@osdl.org>
To: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI vendor and device strings in sysfs
Date: Thu, 17 Jul 2003 07:55:39 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0307170753240.1213-100000@cherise> (raw)
In-Reply-To: <20030717101123.GA6069@in.ibm.com>
> Here is a patch against 2.6.0-test1 to display PCI vendor and
> device strings in sysfs.
>
> At present, the PCI "name" attribute has a length restriction
> (DEVICE_NAME_SIZE) within which it tries to accomodate the vendor
> and device strings, leading to, in most cases, truncation of one
> or both strings.
>
> This patch alleviates the issue by creating the vendor_name and
> device_name attributes for PCI devices.
We don't necessarily need to keep the ASCII strings around at all, and in
the case in which CONFIG_PCI_NAMES=n, they are completely irrelevant. They
are pretty, but we could just export the vendor/device IDs and have a
userspace tool (e.g. sysutils from IBM) look up the name in a userspace
database.
-pat
next prev parent reply other threads:[~2003-07-17 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 10:11 [PATCH] PCI vendor and device strings in sysfs Ananth N Mavinakayanahalli
2003-07-17 14:55 ` Patrick Mochel [this message]
2003-07-18 2:35 ` Greg KH
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=Pine.LNX.4.44.0307170753240.1213-100000@cherise \
--to=mochel@osdl.org \
--cc=ananth@in.ibm.com \
--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 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).