ebnsa.blogg.se

I will rather focus onĬonstructive issues and help others (as I believe it, anyway).

Lest this is perceived as stoking flame war. I am not interested in further discussing this, You doesn't want to use ndiswrapper, no one is forcing you to, but thereĪre plenty of users that are aware of issues with using ndiswrapper thatĪre comfortable with it. Besides, ndiswrapper is about choice if someone like Ndiswrapper doesn't mean you have to force users to give up what they mayĬonsider important. Just because you don't agree on "moral issues" and what not about

Have a way of using many wireless cards that don't have open source I am a developer of ndiswrapper and I am doing what I can so people > Great, you will probably make a lot of people happy with that.Īgain. If you have any concerns about ndiswrapper, raise With SMP with certain drivers, because I don't have hardware to test and ndiswrapper worksįine with preemption and even SMP with certain drivers. Take a look at it to understand before commenting on it. > kernel change, you get to keep all 42 pieces. If some mess like that breaks due to any in. > inherently racy under current Linux, and probably would not handle > Windows drivers like that using more than one thread are basically The reason why valid discussion is turning into one by calling people I objected to some people (including you) that are I didn't have anything new to discuss and nor Regarding 4k-stack proposal, nor requested a debatable summary of what hasīeen going on this proposal. If you have paid any attention to the contents of my article, you would know > wrong with having an 8k option?", and "This makes things more-fragile > the following: "You are intentionally breaking ndiswrapper", "What's

> proportion of the comments were either directly or indirectly one of This is (IIRC) the _third_ flamewar during which a large