On Tue, 2007-08-28 at 10:50 +0200, Johannes Berg wrote: > To be fair, that's not what you do, you're building two drivers from > one source rather than have a single driver that supports both. I'm > fairly certain Christoph wouldn't object to the latter. Because of the difference of the two hardwares (for example, in iwl-command.h, iwl_rxon_assoc_cmd differs between 3945 and 4965), runtime supporting is difficult if not possible (hw structures differs). So we select to do it statically by generating two drivers from one source code. Do you think if it is a good idea to split them into two drivers and make each of them "#include iwl-base.c"? Please don't hesitate to share if you have better ideas. Thanks, -yi - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
