On Thu, Jan 22, 2009 at 3:17 PM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Thu, Jan 22, 2009 at 03:04:35PM +0100, Johannes Berg wrote: >> On Thu, 2009-01-22 at 08:49 -0500, John W. Linville wrote: >> > On Thu, Jan 22, 2009 at 06:32:55AM +0200, Nick Kossifidis wrote: >> > > 2009/1/21 Stefanik Gábor <netrolller.3d@xxxxxxxxx>: >> > > > >> > > > I think EMBEDDED is for options that replace full-featured Linux >> > > > components with dumbed-down, "low-profile" equivalents (like SLOB) - >> > > > PID vs. minstrel is more like SLAB vs. SLUB. >> > > > >> > > > Gábor >> > > > >> > > >> > > Minstrell performs very well even on embedded devices, i don't think >> > > it's that heavy compared to pid. >> > >> > I think his point was that people should be able to select multiple >> > algorithms without having to select EMBEDDED. >> >> The reason it was originally under EMBEDDED is that this allows you to >> turn off _all_ algorithms, and that breaks, but might be desirable if >> you have a system where you know you're using iwlagn or ath9k only which >> have their own algorithms. > > I see. But currently it limits you to only one generic algorithm, the > one chosen as the default. I don't think that was really the intent? > I think RC_NONE should depend on embedded, but not the chooser itself. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) -- 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
