On Fri, 2010-10-08 at 10:45 -0700, Brett Rudley wrote: > Thanks for the input. No problem. I'd like to fix this as much as you would, since the STA driver isn't an option here. Just for kicks, I tried STA after this but it didn't work with the wireless extensions on my system and I much prefer getting the staging driver fixed. Meanwhile, I have no WiFi on my shiny new netbook, so I'm very keen to help get this fixed :) > The 4313 (Device ID 4327) is pretty solid on the 32 bit staging-next > kernel (loads, runs for days, no issues, etc). Can you do me three favors: 1). Tell me what kind of hardware you are testing on that's 32-bit? 2). How many CPUs (threads, cores, whatever) do you have? 3). Share your test kernel configuration? It's likely that we could have a combination of different config (I have every debug option turned on pretty much) and different word size and I'd love to have that data. I will look through the crash tonight. > On the other hand, I haven't been using anything other than that kernel > recently so its very, very likely there are problems with other kernels, > especially 64 bit which I haven't even attempted yet (but will of course). We need data points on 64-bit kernels. Anyone else care you share? > Please do try out the 32 bit staging-next kernel and let me know how > it goes. Sorry. I don't have a suitable test environment with this hardware (it took several hours to get to the disk and swap it out the other night since ASUS really don't want me to do that) but I suppose I might try a nightly rawhide 32-bit compose on a USB stick and built the driver against that - hmm. That might be a nice way to test 32-bit. > Yeah, turning on msglevel produces more (and possibly *much* more) > output. Yea. What about the high order bits in the phy msglevel, what are they intended to be doing? Could you, perhaps, give us some more useful docs to accompany what is in the staging tree at this point? Thanks, Jon. -- 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
