That's a good idea.
I also wonder if kernels shipped in d-i include or not modules for
hardware specific framebuffer devices, or generic drivers (like vesafb
on i386) only.
CONFIG_FB_CIRRUS=m
CONFIG_FB_OF=y
CONFIG_FB_CONTROL=y
CONFIG_FB_PLATINUM=y
CONFIG_FB_VALKYRIE=y
CONFIG_FB_CT65550=y
CONFIG_FB_IMSTT=y
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_RADEON=y
CONFIG_FB_ATY128=y
CONFIG_FB_ATY=y
CONFIG_FB_SAVAGE=m
CONFIG_FB_SIS=y
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=y
CONFIG_FB_TRIDENT=m
So, on powerpc, we have : offb, controlfb, platinumfb, valkyriefb, imsttfb,
nvidiafb, matroxfb, radeonfb, aty128fb, atyfb, sisfb and 3dfxfb builtin.
cirrusfb, s1d13xxxfb (no idea what this one is), savagefb, neomagixfb, kyrofb
and tridentfb as modules.
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?
No idea, i on no radeon boards :(
Someone else ?
Any chanche to test if disabling HW acceleration also makes the g-i
usable on machines equippped with ATI or NVIDIA graphic boards ( where
atyfb and nvidiafb modules would be used in the case HW acceleration was
not forced off ) ?
Nope, but as soon as the fixed rootskel-gtk is uploaded, we can issue a
call
for testers on debian-powerpc, using the daily builds.
A round of PPC tests would be useful, especially it happens to find
owners of ATI or NVIDIA boards.
ati being mach64 (rage) and aty (rage 128) here.
Not sure if we ever had a success with g-i on oldworld, so it is less
important, and my prep box has a sis and a matrox, but g-i is too big to boot
on it. I do have a spare matox millenium i could plug in the pegasos, and just
got a xgi volari v3xt. Will test with them. nvidia is evil and should be
boycotted anyway :)