From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: WANTED: .../modules.*map to (X)HTML
Date: Mon, 15 Jan 2001 17:17:22 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97957914411596@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97944222604210@msgid-missing>
> > - (dream on) some XML file holding all the modutils
> > data "MODULE_DESCRIPTION", "MODULE_PARM_DESC" and
> > so forth, for each module.
Actually that's one of the easier parts to deliver ... since
"modinfo" already exposes that, it's just a shell script to
dump it out into a form that a document generation system can
then play with. No modutils patch necessary.
In fact, since I'm not always patient, I hacked that together
and put together part of the kind of system I want to see.
Take a peek at this (temporary?) URL, and send along any
comments that come to mind -- yes, none of the device or
class info shows up:
http://linux-hotplug.sourceforge.net/kernel.html
The shell script that extracts "modinfo" data is "modinfo.sh",
and an example of its output is there, "modinfo.xml". That's
for a kernel with most USB drivers as modules, but very few
PCI/Cardbus drivers configured.
> I am
> holding off on modutils work until Linus/Alan realises that we need the
> kernel patch to add version numbers to device tables, I want an agreed
> working base to extend on.
Yes, that's a problem. Sigh.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-15 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 23:40 WANTED: .../modules.*map to (X)HTML Keith Owens
2001-01-15 17:17 ` David Brownell [this message]
2001-01-15 22:56 ` Keith Owens
2001-01-16 0:16 ` Miles Lane
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 16:41 David Brownell
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-97957914411596@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 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.