mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Emmanuel Fleury <fleury@cs.aau.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Framework for automatic Configuration of a Kernel
Date: Thu, 29 Sep 2005 20:09:38 -0700	[thread overview]
Message-ID: <20050929200938.779ce6e2.rdunlap@xenotime.net> (raw)
In-Reply-To: <43396A6A.30104@cs.aau.dk>

On Tue, 27 Sep 2005 17:51:06 +0200 Emmanuel Fleury wrote:

> Ahmad Reza Cheraghi wrote:
> > 
> > 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. 
> 
> I might be wrong, but I don't think that there is any other way to get
> hardware information but through the /proc or /sys interface.
> 
> Can somebody comment on this ?

You can use libpciutils (whatever lspci uses) to enumerate
PCI devices  (but I wouldn't, I'd just use lspci :).

You can clone lsusb to enumerate USB devices... but I would
just use lsusb.

You can probably clone 'pnpdump' to enumerate ISA PNP devices.
But I would just use pnpdump.

There's probably a ieee1394/firewire enumeration program.

You won't be able (safely) to discover ISA devices/ports.
(other than "standard" cnipset/motherboard devices)

Anyway, I would just use the existing tools unless there are
things that you must have that they don't provide.

---
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law

  parent reply	other threads:[~2005-09-30  3:09 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
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 [this message]
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=20050929200938.779ce6e2.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --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®