On Tue, 2008-10-21 at 09:18 -0400, Dan Williams wrote: > Definitely, I've looked at marvell.git (topdog) and Luis's code, and > earlier Marvell GPL code quite extensively. The firmware interface is > quite similar between the TopDog (802.11n) parts and the b/g parts, as > are the TX and RX descriptors. From my research, I didn't think it > would be that hard to support both parts in the same driver. > > My strategy would be this, assuming you have TopDog hardware. If you do > not, I can ship you a CardBus TopDog card: The only TopDog hardware I have is the aforementioned Orion-based router, which has OpenWRT in its future. That certainly fits the strategy, but with somewhat unfortunate timing. I previously had access to an 8335 card, but don't currently. > 1) Use marvell.git and Luis' attempt to get minimal b/g support working > for the TopDog parts > > 2) Start adding in the support for 8335/8310 parts using mrv8k (and > possibly BSD's malo(4)) as a guide > > 3) Add the 802.11n bits of TopDog stuff That contrasts slightly with the understanding I had: 1) Use the in-tree libertas library to get b/g going for 8335/8310 parts, using mrv8k/malo as a guide. 2) Start adding in the support for TopDog parts in b/g mode, from mrvl_cb82.git 3) Add the 802.11n bits of TopDog stuff > The _most_ important thing is first to get a stable b/g driver, then add > the candy later. I could not agree more. > Since we have a full TopDog driver implementation, Do we? > that might be the best thing to get working first. mrv8k was never able > to get very far for me when I was poking at it, I couldn't even get > reliable scan results. -- 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
