Hi!
> > > I agree, if we make it entirely clear that the flag is nonpolitical.
> >
> > Hm, I don't know, what makes this different from the fact that we can
> > mmap PCI device space today through the proc and sysfs entries? That's
> > how X gets direct access to the hardware for a number of di
Here is another round of the updated UIO (Userspace I/O driver framework)
patches for 2.6.21.
All of the issues raised from the last time the patches were posted
(last week) have been fixed in this version.
Many thanks for all of the review comments from everyone who took the
time to read over th
> >Right, this is just a hint, that something in user space is accessing
> >the hardware directly. Not a too bad idea, but pretty much useless when
> >we add X to the picture as it will be set always :)
>
> Index: linux-2.6.21-mm_20040728/drivers/char/mem.c
> ==
On Apr 29 2007 10:30, Thomas Gleixner wrote:
>>
>> Unless you think we should also use the same "taint" flag on those
>> accesses too, and if so, I have no objection.
>
>Right, this is just a hint, that something in user space is accessing
>the hardware directly. Not a too bad idea, but pretty mu
On Sat, 2007-04-28 at 18:23 -0700, Greg KH wrote:
> On Sat, Apr 28, 2007 at 10:31:37PM +0200, Thomas Gleixner wrote:
> > On Sat, 2007-04-28 at 21:15 +0100, Alan Cox wrote:
> > > > > I have a political question, if I have a user space driver, is my
> > > > > kernel
> > > > > tainted or not?
> > >
On Sat, Apr 28, 2007 at 10:31:37PM +0200, Thomas Gleixner wrote:
> On Sat, 2007-04-28 at 21:15 +0100, Alan Cox wrote:
> > > > I have a political question, if I have a user space driver, is my
> > > > kernel
> > > > tainted or not?
> > >
> > > Surely not. By using the kernel's userspace interfac
On Sat, 2007-04-28 at 21:15 +0100, Alan Cox wrote:
> > > I have a political question, if I have a user space driver, is my kernel
> > > tainted or not?
> >
> > Surely not. By using the kernel's userspace interface, you create no
> > "derived work" of the kernel. See COPYING in the root directory
> > I have a political question, if I have a user space driver, is my kernel
> > tainted or not?
>
> Surely not. By using the kernel's userspace interface, you create no
> "derived work" of the kernel. See COPYING in the root directory of the
> kernel sources for details.
That only covers norm
Am Samstag 28 April 2007 21:56 schrieb Bill Davidsen:
> Greg KH wrote:
> > Here are the updated UIO (Userspace I/O driver framework) patches for
> > 2.6.21.
> >
> > They have been revamped from the last time you have seen them, and they
> > include a real driver, the Hilscher CIF DeviceNet and Pro
On Sat, 2007-04-28 at 15:56 -0400, Bill Davidsen wrote:
> Greg KH wrote:
> > Here are the updated UIO (Userspace I/O driver framework) patches for
> > 2.6.21.
> >
> > They have been revamped from the last time you have seen them, and they
> > include a real driver, the Hilscher CIF DeviceNet and P
Greg KH wrote:
Here are the updated UIO (Userspace I/O driver framework) patches for
2.6.21.
They have been revamped from the last time you have seen them, and they
include a real driver, the Hilscher CIF DeviceNet and Profibus card
controller, which is being used in production systems with this
Am Samstag 28 April 2007 15:00 schrieb Matthieu CASTET:
>
> uio_dummy.c (that should be present according documentation) seems
> missing.
Well, uio_dummy was created during development to have something to
test with. It calls uio_event_notify() from a timer routine to
simulate interrupts without
Hi,
On Fri, 27 Apr 2007 15:49:57 -0700, Greg KH wrote:
> Here are the updated UIO (Userspace I/O driver framework) patches for
> 2.6.21.
>
>
> Documentation/DocBook/kernel-api.tmpl |4 +
> Documentation/DocBook/uio-howto.tmpl | 498 +++
> drivers/Kconfig
On Fri, 2007-04-27 at 16:11 -0700, Greg KH wrote:
> > I'm a bit uncertain about the whole UIO idea, really. I have this vague
> > feeling that we'd prefer to encourage people to move device drivers into
> > GPL'ed kernel rather than encouraging them to do closed-source userspace
> > implementation
Am Samstag 28 April 2007 01:04 schrieb Andrew Morton:
> On Fri, 27 Apr 2007 15:49:57 -0700
>
> Greg KH <[EMAIL PROTECTED]> wrote:
> > Here are the updated UIO (Userspace I/O driver framework) patches for
> > 2.6.21.
>
> I'm a bit uncertain about the whole UIO idea, really. I have this vague
> feel
> I'm a bit uncertain about the whole UIO idea, really. I have this vague
> feeling that we'd prefer to encourage people to move device drivers into
> GPL'ed kernel rather than encouraging them to do closed-source userspace
> implementations which will probably end up being slower, less reliable a
On Fri, Apr 27, 2007 at 04:04:25PM -0700, Andrew Morton wrote:
> On Fri, 27 Apr 2007 15:49:57 -0700
> Greg KH <[EMAIL PROTECTED]> wrote:
>
> > Here are the updated UIO (Userspace I/O driver framework) patches for
> > 2.6.21.
>
> I'm a bit uncertain about the whole UIO idea, really. I have this v
On Fri, 27 Apr 2007 15:49:57 -0700
Greg KH <[EMAIL PROTECTED]> wrote:
> Here are the updated UIO (Userspace I/O driver framework) patches for
> 2.6.21.
I'm a bit uncertain about the whole UIO idea, really. I have this vague
feeling that we'd prefer to encourage people to move device drivers into
Here are the updated UIO (Userspace I/O driver framework) patches for
2.6.21.
They have been revamped from the last time you have seen them, and they
include a real driver, the Hilscher CIF DeviceNet and Profibus card
controller, which is being used in production systems with this driver
framework
19 matches
Mail list logo
