![]() | ||||||||||
Messages in this thread |
>My Keylargo controller reports 0 as the revision number, thus it might >either be advisable to put that hw_can_byteswap = 0 into the innermost >block and not check the revision at all (if no Keylargo can do byteswap) >or or to put a check for revision <= 2 (after all, isn't it logical to >assume that only later revisions will be able to do byteswap?) inside the >innermost block and set hw_can_byteswap to 0 there. You are right, this is a pangea chipset (KeyLargo & UniNorth in a single ASIC) and in that case, KL provides no rev. number. I'll fix this. Thanks for the report, Ben. - 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-03-22 11:15 [from the cache] ©2003-2008 | ||||||||||