On 2005-01-14, 13:39 -0800, Rick Stevens wrote > Scot L. Harris wrote: > > On Fri, 2005-01-14 at 04:56, Nicholas Comino wrote: > > > > > > > That's a PCMCIA card (not PCI), will ndiswrapper result in pretty much > > > the same driver for the dwl-G520+?? > > > > > > Is that wireless driver solution as good as it gets? > > > > > > The real trick with any wireless card is to sort out which chip set the > > card uses. Also don't assume that two of the same model card has the > > same chip set, check that they are the same versions. Vendors will use > > different chip sets on the same model cards and slap a version number on > > that denotes the change. This usually means you have to use different > > drivers. > > > > There are native drivers available for some chip sets like Atheros and > > Prism chip sets. Others you have to use ndiswrapper which lets you use > > the windows drivers for those chips sets (broadcom is an example). > > > > So figure out which chip set the card uses then find the appropriate > > driver for that chipset. > > Also be aware that ndiswrapper now requires a minor kernel patch (with > kernels 2.6.9-1.724 and later) in order to compile. > > If the kernel gang is listening, is there a reason you removed > > EXPORT_SYMBOL_GPL(task_nice); > > from kernel/sched.c? That's what ndiswrapper wants (and one of the > reasons I asked about rebuilding modules and having them so darned big). are you sure? with ndiswrapper-1.0rc2 and kernel-2.6.10* you don't need it anymore. from the ChangeLog: * task_nice is not used anymore, so should compile with kernels where this is not exported
