Please find attached an updated ebuild for media-gfx/bootsplash. This new version incorporates Spock's & Oliver's patch to make bootsplash architecture-independant by not relying on VESA-framebuffer anymore. Thus i have included ~ppc in the ebuild diff as it runs fine on ppc now as has been reported by several users. The patch comes directly from http://www.bootsplash.de/files/bootsplash-3.1.4-sp2-2.6.7.diff, works fine with vanilla 2.6.7 and should be saved in /usr/share/bootsplash/bootsplash-3.1.4-sp2-2.6.7.patch.bz2 by portage. Also included is a patched version of /sbin/bootsplash_patch that can detect the ppc architecture and apply the proper patch, also giving instructions on the ppc bootloader (yaboot) config. A sample yaboot config is also included analog to the grup.conf.sample. I saw that the Changelog for the latest bootsplash revision includes a copy-and-paste from bootsplas.de on exactly this new architecture-independant patch, but the patch itself has not been included! With these fixes we should finally be able to have an easy-to-install bootsplash on ppc. Cheers, DiskBreaker
Created attachment 34636 [details, diff] bootsplash-0.6.1-r4.diff
Created attachment 34638 [details] bootsplash-0.6.1-r4.ebuild
Created attachment 34639 [details, diff] bootsplash_patch-ppc.diff
Created attachment 34640 [details] yaboot.conf.sample
Created attachment 34641 [details, diff] bootsplash-3.1.4-sp2-2.6.7.patch
I forgot to add - of course someone (I guess spock) would have to repackage bootsplash-kernel-0.6.1-r3.tar.bz2 to bootsplash-kernel-0.6.1-r4.tar.bz2 together with the bootsplash-3.1.4-sp2-2.6.7.patch. Also bootsplash-core-0.6.1-r4.tar.bz2 should include the patched bootsplash_patch script and the yaboot.conf.sample under /misc. If needed, I can easily create the new tarballs or I can further change the ebuild so that it does not rely on spock's distfile repository.
I'll test it soon, in the mean time please the kernel team and the media-gfx team have a look on it too.
It seems to be working ok. I added the patch to pegasos-dev-sources-2.6.7-r1.
Just wanted to add a "works here" on my iBook G3 with a rage128 graphics card. If anybody needs the re-tared bootsplash-core-0.6.1-r4.tar.bz2 with the patches included as comment #6 says so you can find it at http://dev.gentoo.org/~pylon/files/bootsplash-core-0.6.1-r4.tar.bz2
> I saw that the Changelog for the latest bootsplash revision includes a > copy-and-paste from bootsplas.de on exactly this new architecture-independant > patch, but the patch itself has not been included! LOL :D Just to make things clear here - it's the other way around - bootsplash.de has entries copied from OUR changelogs ;> Now about that patch.. sp2-2.6.7 is virtually identical to spock-0.1-2.6.7, included in the latest bootsplash release (0.6.1-r3). And no, it's not complete yet. It still has bugs. I've fixed most (all?) of them and made another patch, which is due to be released in bootsplash-0.6.1-r4 tomorrow. Please don't get too hasty here with adding sp2-2.6.7 to any kernel-sources packages. Thanks for the sample config file for yaboot - it'll be included in 0.6.1-r4.
>LOL :D Just to make things clear here - it's the other way around - bootsplash.de >has entries copied from OUR changelogs ;> In that case I must say I'm awefully sorry, I was talking about things I had no idea about... I guess I should have just waited a bit for a new release of the ebuild, but I was quite thrilled with finally getting a bootsplash with correctly decoded colours on ppc. I hope you still have some use for the boosplash_patch and the yaboot.conf.sample.
No need to apologize, it was quite funny, actually ;) Anyway, the new bootsplash is out. It has a shiny new fixed patch which should make 24bpp and 16bpp useable on PPCs. It also includes the new sample config file for yaboot. Thanks :)
Sam Halliday wrote on bootsplash-discussion: 15bpp and 16bpp now have much better font handling, thank you! however 24bpp is still not being set... but that could be a radeonfb bug. also, the fonts go all fuzzy again when the machine is rebooted or powering down... so not all the bugs are fixed ;-)
