> What exactly is irritating?
> Please name the problems so that they can be fixed.
>
> > Detecting the cpu and using march=native could be all part of that
>
> You don't need march=native for this.
>
> You have to set the right config option for your CPU and you
> automatically get the right compiler options.
Well when doing a lspci here are some specific examples:
03:02.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
What modules would you think you'd need to compile to get this to work?
No it's not budget card os buget card ci even though the card its self
has no cam interface
00:14.2 Audio device: ATI Technologies Inc SB600 Azalia
Is there any indication from this piece of info that the intel hda
driver is required?
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
This uses AHCI
As for the i2c and the hardware monitoring support well that's mostly guess work
Half the time it's easier doing a lsmod when booted on a livecd and
trying to figure out what options are required from the module names
which sometime can be just as tricky.
Why not auto detect the CPU the same way GCC does and automatically
set the correct CPU and then go the whole hog and let GCC use the
correct flags if it's new enough using native
I can't understand why you wouldn't find this useful when setting up a
customised kernel.
Maybe even having a make addnewhardware option to quickly add extra
devices to your config file.
Mike
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
