--- Alex Riesen <[EMAIL PROTECTED]> wrote:
> On 9/8/05, Ahmad Reza Cheraghi > <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
