coalms wrote:Where or how do you usually search for the right kernel drivers for your architecture?
In the unlikely event that you can't find the documentation from searching, you can just throw everything at it and see what it uses. With hardware drivers like ALSA audio drivers, the kernel won't load modules for hardware that isn't present... so you can just build every driver you think your chipset could possibly be (as modules), see which one your kernel actually loads, and then rebuild disabling all the others.
In fact you don't even need to disable the others: that's how generic (prebuilt) distro kernels work, providing a huge range of modules and allowing the kernel to pick what it needs based on the hardware it detects. But, if you want a lean, tidy little kernel with only the drivers you need, booting a generic one and then using lsmod to see what it loaded can work as a clumsy way to identify your drivers. There is also a make localmodconfig method for going straight from the running modules to a kernel .config (obviously you need to plug in webcams, USB drivers, printers and anything else you want built before attempting it), although I don't use that myself so can't vouch for it.