Messages in this thread | | | Date | Wed, 28 Feb 2007 16:50:05 +0000 (GMT) | From | James Simmons <> | Subject | Re: [Linux-fbdev-devel] [PATCH 2.6.20 1/1] fbdev, mm: hecuba/E-Ink fbdev driver |
| |
> I'm not sure I understand. What the current implementation does is to > use host based framebuffer memory. Apps mmap that memory and draw to > that. Then after the delay, that framebuffer is written to the > device's memory. That's the scenario for hecubafb where the Apollo > controller maintains it's own internal framebuffer. > > When you say without the framebuffer, if you meant without the host > memory, then this method doesn't work. If you mean without the > device's internal memory, then yes, I think we can do that, because it > would be up to the driver to use the touched pagelist to then perform > IO as suitable for its device.
I meant for it to work for non framebuffer devices. I realized that not such a great idea.
- 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/
| |