On 09/08/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
> > >
> > I think the only way to avoid it is to not provide something like UIO.
>
> Problem is, things like UIO provide a real solution for a wide range of
> different types of devices.
Am Donnerstag 09 August 2007 16:12 schrieb Alan Cox:
> > That's no UIO invention. Userspace software that uses kernel interfaces like
> > syscall, device files, sysfs, and so on, is by definition _not_ a derived
> > work
> > of the kernel and can be distributed under any license.
>
> This I
> That's no UIO invention. Userspace software that uses kernel interfaces like
> syscall, device files, sysfs, and so on, is by definition _not_ a derived work
> of the kernel and can be distributed under any license.
This I believe incorrect. Please cite caselaw if you know better.
> With UIO,
O> I disagree. UIO is a documented kernel<->userspace interface, like sysfs
> or proc. Using your argument, we would also have to say that a userspace
> software that is unusable without sysfs is a derived work of the kernel.
> But IANAL, tell me if I missed an important point.
It depends how
Am Donnerstag 09 August 2007 00:12 schrieb [EMAIL PROTECTED]:
>
> If you have UIO in the kernel talking to stuff in userspace, you're going to
> have to deal with closed-source stuff at the userspace end of the pipe.
That's no UIO invention. Userspace software that uses kernel interfaces like
Am Donnerstag 09 August 2007 01:40 schrieb Alan Cox:
> > On the other hand, given that we've always said that closed-source stuff in
> > userspace is OK, the only way to not let *that* horse out of the barn is to
> > not merge UIO at all.
>
> It really makes no difference whether it is merged or
On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
> >
> I think the only way to avoid it is to not provide something like UIO.
Problem is, things like UIO provide a real solution for a wide range of
different types of devices. Like the one provided in the kernel right
now, and a bunch
Am Mittwoch 08 August 2007 23:36 schrieb Jesper Juhl:
> On 19/07/2007, Greg Kroah-Hartman <[EMAIL PROTECTED]> wrote:
> > From: Hans J. Koch <[EMAIL PROTECTED]>
> >
> > Documentation for the UIO interface
> >
> ...
> > +If you use UIO for your card's driver, here's what you get:
> > +
> ...
> > +
>
Am Mittwoch 08 August 2007 23:36 schrieb Jesper Juhl:
On 19/07/2007, Greg Kroah-Hartman [EMAIL PROTECTED] wrote:
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
...
+paraIf you use UIO for your card's driver, here's what you get:/para
+
...
+listitem
+
On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
I think the only way to avoid it is to not provide something like UIO.
Problem is, things like UIO provide a real solution for a wide range of
different types of devices. Like the one provided in the kernel right
now, and a bunch of
Am Donnerstag 09 August 2007 01:40 schrieb Alan Cox:
On the other hand, given that we've always said that closed-source stuff in
userspace is OK, the only way to not let *that* horse out of the barn is to
not merge UIO at all.
It really makes no difference whether it is merged or not. The
Am Donnerstag 09 August 2007 00:12 schrieb [EMAIL PROTECTED]:
If you have UIO in the kernel talking to stuff in userspace, you're going to
have to deal with closed-source stuff at the userspace end of the pipe.
That's no UIO invention. Userspace software that uses kernel interfaces like
O I disagree. UIO is a documented kernel-userspace interface, like sysfs
or proc. Using your argument, we would also have to say that a userspace
software that is unusable without sysfs is a derived work of the kernel.
But IANAL, tell me if I missed an important point.
It depends how closely
That's no UIO invention. Userspace software that uses kernel interfaces like
syscall, device files, sysfs, and so on, is by definition _not_ a derived work
of the kernel and can be distributed under any license.
This I believe incorrect. Please cite caselaw if you know better.
With UIO, you
Am Donnerstag 09 August 2007 16:12 schrieb Alan Cox:
That's no UIO invention. Userspace software that uses kernel interfaces like
syscall, device files, sysfs, and so on, is by definition _not_ a derived
work
of the kernel and can be distributed under any license.
This I believe
On 09/08/07, Greg KH [EMAIL PROTECTED] wrote:
On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
I think the only way to avoid it is to not provide something like UIO.
Problem is, things like UIO provide a real solution for a wide range of
different types of devices. Like the
> On the other hand, given that we've always said that closed-source stuff in
> userspace is OK, the only way to not let *that* horse out of the barn is to
> not merge UIO at all.
It really makes no difference whether it is merged or not. The test is
"derivative work" and not 'linking'.
A user
On 09/08/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Wed, 08 Aug 2007 23:36:00 +0200, Jesper Juhl said:
>
> > Do we really want this?
> >
> > In my oppinion we run the risk here of encouraging behaviour akin to
> > what NVidia is doing - release a small kernel "glue" module and then
>
On Wed, 08 Aug 2007 23:36:00 +0200, Jesper Juhl said:
> Do we really want this?
>
> In my oppinion we run the risk here of encouraging behaviour akin to
> what NVidia is doing - release a small kernel "glue" module and then
> keep the driver proper in a binary blob (in userspace, but still a
>
On 19/07/2007, Greg Kroah-Hartman <[EMAIL PROTECTED]> wrote:
> From: Hans J. Koch <[EMAIL PROTECTED]>
>
> Documentation for the UIO interface
>
...
> +If you use UIO for your card's driver, here's what you get:
> +
...
> +
> + if you need to keep some parts of your driver closed source,
> +
On 19/07/2007, Greg Kroah-Hartman [EMAIL PROTECTED] wrote:
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
...
+paraIf you use UIO for your card's driver, here's what you get:/para
+
...
+listitem
+ paraif you need to keep some parts of your driver closed
On Wed, 08 Aug 2007 23:36:00 +0200, Jesper Juhl said:
Do we really want this?
In my oppinion we run the risk here of encouraging behaviour akin to
what NVidia is doing - release a small kernel glue module and then
keep the driver proper in a binary blob (in userspace, but still a
binary
On 09/08/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Wed, 08 Aug 2007 23:36:00 +0200, Jesper Juhl said:
Do we really want this?
In my oppinion we run the risk here of encouraging behaviour akin to
what NVidia is doing - release a small kernel glue module and then
keep the
On the other hand, given that we've always said that closed-source stuff in
userspace is OK, the only way to not let *that* horse out of the barn is to
not merge UIO at all.
It really makes no difference whether it is merged or not. The test is
derivative work and not 'linking'.
A user space
From: Hans J. Koch <[EMAIL PROTECTED]>
Documentation for the UIO interface
From: Hans J. Koch <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 611
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
From: Hans J. Koch [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 611 +
2
From: Hans J. Koch <[EMAIL PROTECTED]>
Documentation for the UIO interface
From: Hans J. Koch <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 611
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
From: Hans J. Koch [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 611 +
2
Am Montag 07 Mai 2007 19:46 schrieb Randy Dunlap:
> On Fri, 4 May 2007 11:37:09 +0200 Hans-Jürgen Koch wrote:
>
> > Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
> > > >
> > > > Hm, I have about 3 different patches here now, all dependant on each
> > > > other, yet I can't tell which
On Fri, 4 May 2007 11:37:09 +0200 Hans-Jürgen Koch wrote:
> Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
> > >
> > > Hm, I have about 3 different patches here now, all dependant on each
> > > other, yet I can't tell which goes first :(
> > >
> > > Can someone just send me 1, or 3
On Fri, 4 May 2007 11:37:09 +0200 Hans-Jürgen Koch wrote:
Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
Hm, I have about 3 different patches here now, all dependant on each
other, yet I can't tell which goes first :(
Can someone just send me 1, or 3 with the correct
Am Montag 07 Mai 2007 19:46 schrieb Randy Dunlap:
On Fri, 4 May 2007 11:37:09 +0200 Hans-Jürgen Koch wrote:
Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
Hm, I have about 3 different patches here now, all dependant on each
other, yet I can't tell which goes first :(
Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
> >
> > Hm, I have about 3 different patches here now, all dependant on each
> > other, yet I can't tell which goes first :(
> >
> > Can someone just send me 1, or 3 with the correct order in which to
> > apply them?
> >
> > thanks,
> >
Am Donnerstag 03 Mai 2007 08:39 schrieb Hans-Jürgen Koch:
Hm, I have about 3 different patches here now, all dependant on each
other, yet I can't tell which goes first :(
Can someone just send me 1, or 3 with the correct order in which to
apply them?
thanks,
greg k-h
Am Donnerstag 03 Mai 2007 07:37 schrieb Greg KH:
> On Wed, May 02, 2007 at 04:37:34PM -0700, Randy Dunlap wrote:
> > On Thu, 3 May 2007 00:00:28 +0200 Hans-J?rgen Koch wrote:
> >
> > > Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
> > > > On Wed, 2 May 2007 10:41:35 +0200 Hans-J?rgen Koch wrote:
On Wed, May 02, 2007 at 04:37:34PM -0700, Randy Dunlap wrote:
> On Thu, 3 May 2007 00:00:28 +0200 Hans-J?rgen Koch wrote:
>
> > Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
> > > On Wed, 2 May 2007 10:41:35 +0200 Hans-J?rgen Koch wrote:
> > > > Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
On Wed, May 02, 2007 at 04:37:34PM -0700, Randy Dunlap wrote:
On Thu, 3 May 2007 00:00:28 +0200 Hans-J?rgen Koch wrote:
Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
On Wed, 2 May 2007 10:41:35 +0200 Hans-J?rgen Koch wrote:
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
Am Donnerstag 03 Mai 2007 07:37 schrieb Greg KH:
On Wed, May 02, 2007 at 04:37:34PM -0700, Randy Dunlap wrote:
On Thu, 3 May 2007 00:00:28 +0200 Hans-J?rgen Koch wrote:
Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
On Wed, 2 May 2007 10:41:35 +0200 Hans-J?rgen Koch wrote:
Am
On Thu, 3 May 2007 00:00:28 +0200 Hans-Jürgen Koch wrote:
> Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
> > On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
> > > Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
> > > > > +The Userspace I/O HOWTO
> > > >
> > > > Most of this reads
Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
> On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
> > Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
> > > > +The Userspace I/O HOWTO
> > >
> > > Most of this reads well. Thanks.
> > > A few typo corrections are below...
> >
> > Thank
On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
> Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
>
> > > +The Userspace I/O HOWTO
> >
> > Most of this reads well. Thanks.
> > A few typo corrections are below...
>
> Thank you for your work. I generated a new patch that includes
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
> > +The Userspace I/O HOWTO
>
> Most of this reads well. Thanks.
> A few typo corrections are below...
Thank you for your work. I generated a new patch that includes all your
suggestions and also fixes the build problems.
[...]
>
>
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
+titleThe Userspace I/O HOWTO/title
Most of this reads well. Thanks.
A few typo corrections are below...
Thank you for your work. I generated a new patch that includes all your
suggestions and also fixes the build problems.
[...]
On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
+titleThe Userspace I/O HOWTO/title
Most of this reads well. Thanks.
A few typo corrections are below...
Thank you for your work. I generated a new patch that includes
Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
+titleThe Userspace I/O HOWTO/title
Most of this reads well. Thanks.
A few typo corrections are below...
Thank you for
On Thu, 3 May 2007 00:00:28 +0200 Hans-Jürgen Koch wrote:
Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
+titleThe Userspace I/O HOWTO/title
Most of this reads well.
On Fri, 27 Apr 2007 15:50:57 -0700 Greg Kroah-Hartman wrote:
> From: Hans J. Koch <[EMAIL PROTECTED]>
>
> Documentation for the UIO interface
>
> From: Hans J. Koch <[EMAIL PROTECTED]>
> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
> ---
> Documentation/DocBook/kernel-api.tmpl |4
On Fri, 27 Apr 2007 15:50:57 -0700 Greg Kroah-Hartman wrote:
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
From: Hans J. Koch [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/DocBook/kernel-api.tmpl |4 +
From: Hans J. Koch <[EMAIL PROTECTED]>
Documentation for the UIO interface
From: Hans J. Koch <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 498
From: Hans J. Koch [EMAIL PROTECTED]
Documentation for the UIO interface
From: Hans J. Koch [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/DocBook/kernel-api.tmpl |4 +
Documentation/DocBook/uio-howto.tmpl | 498 +
2
50 matches
Mail list logo
