From: "Giacomo A. Catenazzi" <cate@student.ethz.ch>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>,
linux-kernel@vger.kernel.org, linux-kbuild@torque.net
Subject: Re: [KBUILD] How do we handle autoconfiguration?
Date: Wed, 27 Dec 2000 15:27:29 +0100 [thread overview]
Message-ID: <3A49FC51.F67BABA8@student.ethz.ch> (raw)
In-Reply-To: <200012262313.eBQNDBi07719@snark.thyrsus.com> <3A49CF1C.19A0FB55@student.ethz.ch>
I forgot:
The program is in http://people.debian.org/~cate/autoconfigure/
Notes of implementation:
It is a bash script. I've split in two file:
rules file: contain the pci id, device name, resources names,...
It is in a simple format, so that it can used in other programs.
Every resource has also a comment writing where I found it in
kernel sources.
main file: define how to use the rules file and how to detect
special configurations.
The autoconfiguration can be done in an external (target) machine
(it doesn't need nothing of kernel, no lspci, no special programs).
Now autoconfigure is in debug mode:
It write some extra debug information and rewrite twice some config
(one for every time it is detected). It write now only to std output,
to not corrupt actual .config files.
giacomo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-27 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-26 23:13 How do we handle autoconfiguration? Eric S. Raymond
2000-12-27 9:57 ` Kai Henningsen
2000-12-27 11:14 ` [KBUILD] " Giacomo A. Catenazzi
2000-12-27 14:27 ` Giacomo A. Catenazzi [this message]
2000-12-27 16:10 ` Eric S. Raymond
-- strict thread matches above, loose matches on Subject: below --
2000-12-26 23:18 Eric S. Raymond
2000-12-27 10:31 ` [KBUILD] " Giacomo A. Catenazzi
2000-12-27 0:52 Michael Elizabeth Chastain
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=3A49FC51.F67BABA8@student.ethz.ch \
--to=cate@student.ethz.ch \
--cc=esr@snark.thyrsus.com \
--cc=linux-kbuild@torque.net \
--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