From: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>
To: Emmanuel Fleury <fleury@cs.aau.dk>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Framework for automatic Configuration of a Kernel
Date: Tue, 27 Sep 2005 05:53:00 -0700 (PDT) [thread overview]
Message-ID: <20050927125300.24574.qmail@web51014.mail.yahoo.com> (raw)
In-Reply-To: <4339344C.9050305@cs.aau.dk>
Hi Emmanuel
--- Emmanuel Fleury <fleury@cs.aau.dk> wrote:
> Hi,
>
> First of all, I guess that the point of a script
> here is to decide
> whether or not the hardware device is here or not.
> So, the output should
> be something like "true" or "false", better than
> echoing some stupid
> characters, maybe a direct "exit 0" and "exit 1"
> would be much less
> troublesome.
Good idea!
>
> Then, I might be wrong but I think we can get a more
> stable detection of
> the PCI devices by grabbing directly the PCI vendor
> and device codes as
> numbers instead of looking them up in the PCI ID
> database.
>
> lspci -n
>
> Or even, ask for a specific device like this:
> lspci -d [<vendor>]:[<device>]
>
> Which would give something like this:
>
> [fleury@rade7 ~]$ lspci -d 8086:1a30
> 0000:00:01.0 PCI bridge: Intel Corporation 82845 845
> (Brookdale) Chipset
> AGP Bridge (rev 04)
>
> Or if the device is not present:
> [fleury@rade7 ~]$ lspci -d 8087:1a30
> <no output>
>
> This way just avoid to depend from the way the PCI
> database is written,
> because whenever there is a change in the spelling
> of one keyword, it
> might need quite a lot of updates in the Kconfigs.
> On the contrary, the
> vendor and device PCI code will never change
> (hopefully).
> So, the 'autorule' would look like this:
>
> autorule pciscript.sh "8086:1a30"
>
> And the script would be:
> #/bin/sh
>
> if [ -z "`lspci -d $1`" ]
> then
> exit 1
> else
> exit 0
> fi
>
> What do you think ?
Again another good Idea. Your right;-) Its better.
But it better getting another way of detecting the
Hardware/Software etc. from the System without using
lspci or the proc-files...? Something that gets all
the Hardware Information directly from the I/O and not
from the Kernel. The good thing about lspci is that it
does both . But it doesnt say if there is a CDROM or
floppy-disc... I tryed alot to search for something
like that but without any success. I heard about this
Otopia Project. I google after it but I didnt find
anything usefule. I think its dead.
Regards
Ahmad Reza Cheraghi
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
next prev parent reply other threads:[~2005-09-27 12:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 9:39 Ahmad Reza Cheraghi
2005-09-27 12:00 ` Emmanuel Fleury
2005-09-27 12:53 ` Ahmad Reza Cheraghi [this message]
2005-09-27 12:58 ` Emmanuel Fleury
2005-09-27 16:47 ` Ahmad Reza Cheraghi
2005-09-27 15:51 ` Emmanuel Fleury
2005-09-28 8:46 ` Andreas Jellinghaus
2005-09-28 8:46 ` Emmanuel Fleury
2005-09-28 9:05 ` Emmanuel Fleury
2005-09-28 9:16 ` Ahmad Reza Cheraghi
2005-09-28 17:11 ` Andreas Jellinghaus
2005-09-30 3:09 ` Randy.Dunlap
2005-09-30 3:23 ` Jody McIntyre
2005-09-28 9:25 ` Emmanuel Fleury
2005-09-28 11:22 ` Ahmad Reza Cheraghi
2005-09-28 11:43 ` Emmanuel Fleury
2005-09-29 7:22 ` Ahmad Reza Cheraghi
[not found] <4Rne4-4sd-3@gated-at.bofh.it>
[not found] ` <4Rq2b-i7-1@gated-at.bofh.it>
[not found] ` <E1EKSQx-0002Pf-M5@be1.lrz>
2005-09-28 8:36 ` Emmanuel Fleury
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=20050927125300.24574.qmail@web51014.mail.yahoo.com \
--to=a_r_cheraghi@yahoo.com \
--cc=fleury@cs.aau.dk \
--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
all inboxes | Powered by JetHome®