Messages in this thread | | | Date | Mon, 7 May 2007 20:02:45 +0000 | From | Pavel Machek <> | Subject | Re: [GIT PATCH] UIO patches for 2.6.21 |
| |
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 different > > cards, and that's pretty much the same thing as the UIO interface is > > doing. > > > > 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 much useless when > we add X to the picture as it will be set always :)
Some people -- like me -- use X68_fbcon over vesafb, in order not to be tainted this way.
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |