linux-kernel - Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080229211513.GI27212@elte.hu>
Date:	Fri, 29 Feb 2008 22:15:13 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pavel Roskin <proski@....org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Zan Lynx <zlynx@....org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jon Masters <jcm@...masters.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only
	symbols

* Pavel Roskin <proski@....org> wrote:

> I already know what USB folks will say.  They want proprietary drivers 
> to be in the userspace.  I doubt ndiswrapper will ever be ported to 
> the userspace.  It's much more likely that some other approach will be 
> used.

btw., what are the technical reasons why ndiswrapper cannot be done in 
userspace, much like the (wildly successful) FUSE concept?

what's the main hardware access method of ndiswrapper - only PIO, or 
mmio as well? In the former case, ioperm() should work, in the latter 
case, mmap()ing the device aperture should work.

Frankly, it would be a great approach for the following reason: it would 
be _far_ easier for people to write a proper free driver, if the NDIS 
driver was in user-space, in a nicely debuggable, traceable, observable 
environment. I dont really see what the technical difficulties there are 
here.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/