--- Adrian Bunk <[EMAIL PROTECTED]> wrote:
> It is interesting that someone posting with an @gnu.org address claims
> that dynamic linking of not GPLv2 compatible code into GPLv2 code was
> not a copyright violation.
There is no copyright violation: ndiswrapper is licensed under GPLv2. And the
Wi
--- [EMAIL PROTECTED] wrote:
> At some point, a compromise position of "Have ndiswrapper do the tainting
> if it loads something with contentious licensing" was suggested - whatever
> happened to that?
>
> (If for no other reason than if you load ndiswrapper for testing, and then
> do *not* actua
--- Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 29, 2007 at 09:55:18AM -0700, Giridhar Pemmasani wrote:
> > When snd-maestro3 (ESS Maestro 3 driver) is enabled, kernel 2.6.21 fails
> to
> > boot - it seems to stop at various points depending on what other m
When snd-maestro3 (ESS Maestro 3 driver) is enabled, kernel 2.6.21 fails to
boot - it seems to stop at various points depending on what other modules are
enabled. Disabling snd-maestro3 fixes all issues. Moreover, with everything
else being same, using maestro3.c from 2.6.20 kernel and using it in
--- Nick Piggin <[EMAIL PROTECTED]> wrote:
>> The patch below uses bh disabled lock for vmlist_lock, so
>> that __vmalloc can be used in interrupt context.
> Hi Giri,
>
> I'm sure I've read the reason for this one before, but when you do patches
> like these, can you include that reason in the c
ed in ntfs, xfs, but it is not clear to me if they use it
with GFP_ATOMIC or GFP_KERNEL.
Thanks,
Giri
Signed-off-by: Giridhar Pemmasani <[EMAIL PROTECTED]>
---
--- linux-2.6.21.orig/./arch/arm/mm/ioremap.c 2007-04-25 23:08:32.0
-0400
+++ linux-2.6.21.new/./arch/arm/mm/ioremap.
uence
of calls). Attached (tested) patch first initializes the rx/tx rings and
then registers the IRQ.
Giri
Signed-off-by: Giridhar Pemmasani <[EMAIL PROTECTED]>
--- drivers/net/mv643xx_eth.c 2006-11-29 16:57:37.0 -0500
+++ ../linux-2.6.20.orig/drivers/net/mv643xx_eth.c 2007-
On Thu, 8 Sep 2005 01:25:20 +0200, Jan Kiszka <[EMAIL PROTECTED]> said:
Jan> Yes, I can provide some numbers around atheros devices (10-20%
Jan> speed-up). And yes, I can explain why ndiswrapper suffers from
Are you comparing atheros Windows driver with ndiswrapper or madwifi
with ndiswrappe
Jan Kiszka wrote:
> Ndiswrapper is already slower than native drivers are, also due to
> horribly implemented Windows drivers btw (the ndis model itself isn't
> that bad, though).
Do you have any evidence to back your claims? What tests did you do to say
that ndiswrapper is slower than native dri
On Tue, 6 Sep 2005 18:19:45 -0400, Daniel Phillips <[EMAIL PROTECTED]> said:
Daniel> There are only two stacks involved, the normal kernel stack
Daniel> and your new ndis stack. You save ESP of the kernel stack
Sadly, that is not the case: Some drivers, especially USB drivers,
create multip
Jan Kiszka wrote:
> The only way I see is to switch stacks back on ndiswrapper API entry.
> But managing all those stacks correctly is challenging, as you will
> likely not want to create a new stack on each switching point. Rather,
This is what I had in mind before I saw this thread here. I, in
11 matches
Mail list logo
