From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: WANTED: .../modules.*map to (X)HTML
Date: Sat, 13 Jan 2001 16:41:42 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97940409807767@msgid-missing> (raw)
Searching for what should be a quick hack in Perl,
Python, or XSLT. Or the Docbook 3.1/Jade/SGML tools
that kernel doc currently uses.
Input:
- the modutils 2.4.1 hotplug module listings and
other output, for at least USB and PCI drivers.
- "usb.ids", "pci.ids".
- (ideally) some XML template file and/or stylesheet
for the output tables (what text before/after,
how to present tables/headings/captions, etc).
- (dream on) module-specific documentation, in
XML Docbook4 "section" format.
Output:
- HTML file displaying each of these tables:
* Products sorted by (OEM) vendor name and
product ID(s), showing description and
identifying the driver(s).
* Same, but sorted by class, and maybe also
subclass/protocol for the various kinds of
USB class drivers.
* The same pair of tables for PCI/Cardbus
* (ideally) The same pair for ISAPNP too.
- (ideally) XML versions of "usbmap", "pcimap"
and so forth, with no magic numbers saying which
values are significant. Easier to massage that
with text processing tools, merging with other
metadata like annotations (like Marcus' USB
driver database at www.qbik.ch), docs, and:
- (dream on) some XML file holding all the modutils
data "MODULE_DESCRIPTION", "MODULE_PARM_DESC" and
so forth, for each module.
- (dream on) those tables tables are merged into
a Docbook4 reference to document the drivers
on each given system. Click the driver name to
go to its docbook documentation, show the data
that "modutils" exposes (description, parameters
and types, ...), and so on.
I'd like to see a list of all the products that the
Linux 2.4 kernel thinks it's able to hotplug, and that
seems like a fair way to maintain such a list. Likely
it'd be good on the linux-hotplug website (which is
rather skeletal at this time).
Right now I'd just like some quick hack, but as I
imply above, there's surely potential for lots more
if anyone's interested in pursuing that direction.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-13 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 16:41 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 23:40 WANTED: .../modules.*map to (X)HTML Keith Owens
2001-01-15 17:17 ` David Brownell
2001-01-15 22:56 ` Keith Owens
2001-01-16 0:16 ` Miles Lane
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=marc-linux-hotplug-97940409807767@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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).