From: Ingo Molnar <mingo@elte.hu>
To: Pavel Roskin <proski@gnu.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Zan Lynx <zlynx@acm.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jon Masters <jcm@jonmasters.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols
Date: Fri, 29 Feb 2008 22:15:13 +0100 [thread overview]
Message-ID: <20080229211513.GI27212@elte.hu> (raw)
In-Reply-To: <1204313978.2316.8.camel@dv>
* Pavel Roskin <proski@gnu.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
next prev parent reply other threads:[~2008-02-29 21:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:11 [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols Pavel Roskin
2008-02-28 23:25 ` Linus Torvalds
2008-02-29 6:20 ` Pavel Roskin
2008-02-29 16:08 ` Linus Torvalds
2008-02-29 16:54 ` Chris Friesen
2008-02-29 17:06 ` Linus Torvalds
2008-02-29 17:59 ` Chris Friesen
2008-03-06 14:56 ` David Woodhouse
2008-02-29 16:59 ` Zan Lynx
2008-02-29 17:07 ` Linus Torvalds
2008-02-29 17:20 ` Pavel Roskin
2008-02-29 17:33 ` Linus Torvalds
2008-02-29 19:39 ` Pavel Roskin
2008-02-29 19:53 ` Linus Torvalds
2008-02-29 20:08 ` Pavel Roskin
2008-02-29 20:28 ` Linus Torvalds
2008-02-29 21:13 ` Pavel Roskin
2008-02-29 20:17 ` John W. Linville
2008-02-29 20:40 ` David Newall
2008-02-29 20:59 ` Pavel Roskin
2008-02-29 21:08 ` David Newall
2008-02-29 22:17 ` Pavel Roskin
2008-03-01 8:15 ` David Newall
2008-02-29 20:44 ` Pavel Roskin
2008-02-29 21:15 ` Ingo Molnar [this message]
2008-02-29 22:31 ` Pavel Roskin
2008-03-03 10:57 ` Ingo Molnar
2008-03-04 5:37 ` Pavel Roskin
2008-03-04 12:57 ` Ingo Molnar
2008-03-04 17:19 ` Linus Torvalds
2008-03-04 17:38 ` Greg KH
2008-03-04 17:45 ` Pavel Roskin
2008-03-04 21:20 ` Ingo Molnar
2008-03-04 23:23 ` Pavel Roskin
2008-03-04 20:51 ` Ingo Molnar
2008-03-04 23:25 ` Jiri Kosina
2008-03-05 13:21 ` Ingo Molnar
2008-02-29 17:18 ` Jon Masters
2008-02-29 21:55 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080229211513.GI27212@elte.hu \
--to=mingo@elte.hu \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=zlynx@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.