On Fri, Apr 30, 2010 at 12:00 PM, Anatolij Gustschin <agust@xxxxxxx> wrote: > Thanks. Sorry for my wrong answer above, now I remember the logic > behind this and will try to explain. Actually the reason I do not > use kmalloc() here is that I do not want to _copy_ bitmap data to > newly allocated frame buffer area (It will negatively affect boot > time). Instead I reserve the already configured frame buffer area > so that it won't be destroyed. The starting address of the area > to reserve and also the lenght is passed to reserve_bootmem(). > This is the real reason for using reserve_bootmem() here. > I could alloc new bitmap area using allocators, but then I have > to copy the bitmap data (splash image) to newly allocated area > and have to re-configure the descriptors to display from new > bitmap buffer. Ok, I understand. Please add this comment to the code, so that no one else will wonder what you're doing. -- Timur Tabi Linux kernel developer at Freescale -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
