lkml.org 
[lkml]   [2005]   [Sep]   [9]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 9 Sep 2005 00:48:59 -0700 (PDT)
FromAhmad Reza Cheraghi <>
SubjectRe: Automatic .config generation

--- 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/
-
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/
\
 
 \ /
  Last update: 2005-09-09 09:51    [from the cache]
©2003-2008