On Mon, 2008-10-20 at 13:05 -0700, Daniel Gimpelevich wrote: > On Mon, 2008-10-20 at 12:45 -0700, Luis R. Rodriguez wrote: > > On Mon, Oct 20, 2008 at 11:03 AM, Daniel Gimpelevich > > <daniel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > The "Duh..." was a response to the "Not that I have heard of. Don't > > > know." statement, which was pretty ironic. > > > > Well your question was "Has anyone stepped up to help in the port of > > this to mac80211" and I thought you already knew I had that tree. > > I did not ask that, because I saw the tree, and that the initial import > was from the marvell.git tree. The OP might not have realized that the > code was TopDog-related even if he did see it. Since there is no working > mac80211 code for TopDog, any existing hardware-specific code for it may > prove to be a useful reference during the porting process. Anybody > investigating the possibility of stepping up to help in the port needs > to know what is already available and what is not. 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: 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 The _most_ important thing is first to get a stable b/g driver, then add the candy later. Since we have a full TopDog driver implementation, 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. > I don't think there is any question of *whether* TopDog support is > possible in mrv8k, only when, and "right now" does not yet appear to be > the answer. I really hope to be proven wrong on that, though. Oh, it's certainly possible in mrv8k. But obviously you just want to get something up and running first, then add the tasty bits like N support later. Dan -- 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
