While we're on the subject of framebuffers, one area which needs to be
looked into is the pixel layout for all of:
- little endian byte, little endian pixel
1bpp: word 0 bit 31..0 = pixel 31..0)
16bpp: word 0 bit 31..0 = pixel1 bits 15..0 pixel0 bits 15..0)
- little endian byte, big endian pixel
1bpp: word 0 bit 31..0 = pixel 24..31, 16..23, 8..15, 0..7)
16bpp: word 0 bit 31..0 = pixel1 bits 15..0 pixel0 bits 15..0)
- big endian byte, big endian pixel
1bpp: word 0 bit 31..0 = pixel 0..31)
16bpp: word 0 bit 31..0 = pixel0 bits 15..0 pixel1 bits 15..0)
We currently do not support all these combinations, and so far I haven't
looked into it. It is on my (great long) to do list.
-- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.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/