From: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: Alex Riesen <raa.lkml@gmail.com>
Subject: Re: Automatic .config generation
Date: Fri, 9 Sep 2005 00:48:59 -0700 (PDT) [thread overview]
Message-ID: <20050909074900.62012.qmail@web51014.mail.yahoo.com> (raw)
In-Reply-To: <81b0412b05090814132ebe54dd@mail.gmail.com>
--- Alex Riesen <raa.lkml@gmail.com> wrote:
> On 9/8/05, Ahmad Reza Cheraghi
> <a_r_cheraghi@yahoo.com> wrote:
> > I made this Framework to generate a .config based
> on a
> > Target-System. Right-now it works on my Laptop
> Acer
>
> how about teaching it to generate .config using just
> sysfs and lsbus?
Thats another way, to find the Hardware(better than
dmesg). But is this always installed on a nacked
Kernel? And i think, lsbus is not supported by the new
sysfsutils.
The best thing is for detecting the Hardware is
directly from the I/O, and the only program I know is
lspci.
> So noone will need to contact you regarding adding
> their system to
> your files, especially when all the information is
> already present in
> the kernel in a very parsable form (pci.ids, for
> example).
Thangs, didn't know that!
> The whole scenary will then shorten to:
> $ make autoconfig
> $ make
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
next prev parent reply other threads:[~2005-09-09 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 20:39 Automatic .config generation Ahmad Reza Cheraghi
2005-09-08 21:13 ` Alex Riesen
2005-09-09 7:48 ` Ahmad Reza Cheraghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-06 9:12 Ahmad Reza Cheraghi
2005-09-06 9:02 Ahmad Reza Cheraghi
2005-05-12 18:05 Scott Robert Ladd
2005-05-12 17:07 ` jmerkey
2005-05-12 18:21 ` Matthias-Christian Ott
2005-05-12 18:49 ` Steven Rostedt
2005-05-12 18:33 ` Lennart Sorensen
2005-05-12 21:17 ` Edgar Toernig
2005-05-15 7:03 ` Borislav Petkov
2005-05-15 7:42 ` Valdis.Kletnieks
2005-05-15 9:52 ` Jesper Juhl
2005-05-15 11:13 ` Valdis.Kletnieks
2005-05-16 12:50 ` Steven Rostedt
2005-05-15 14:08 ` Scott Robert Ladd
2005-05-15 13:52 ` aq
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=20050909074900.62012.qmail@web51014.mail.yahoo.com \
--to=a_r_cheraghi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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