[PATCH] kdrive: Remove Xfbdev.

[Mikhail Gusarov]

Twas brillig at 17:28:51 08.02.2010 UTC-05 when ajax at nwnk.net did gyre and gimble:

 >>  AJ> [citation needed]
 >> 
 >>   787   664 root     S <  13628  5.5  0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolist
 >> 
 >> 13 megs, compared to 1.4 of Xfbdev.

 AJ> How much of that is .text or .rodata

Not much.

-rwxr-xr-x    1 root     root      1525468 Nov 24 17:30 /usr/bin/Xorg
-rwxr-xr-x    1 root     root       1528636 Jan  1  1970 /usr/bin/Xfbdev*

But it's a bit apples to oranges - Xfbdev here is compiled for MIPS
which features much lower code density than ARM (Xorg). Same Xfbdev for
ARM is ~1.2 megs (don't have device to check right now).

Both are compiled against glibc.

 AJ>, are they built with the same set of extensions, does xdpyinfo bear
 AJ>that out, is that actually the fbdev driver or a hardware driver,
 AJ>etc.

Do you know where to get xdpyinfo for maemo 5? :)

DDX + driver, I assume. But I did not check it yet.

 AJ> Also, what's the resolution and depth of the display under test,
 AJ> since Xfbdev does not use shadowfb by default but Xorg+fbdev does,
 AJ> and that'll show up as a malloc the size of the screen.

Xfbdev in this particular case was rotated.

 AJ> Don't get me wrong, I'm in favor of reducing the xfree86 footprint,
 AJ> I just believe the case to be overstated.

I was wrong about "1.4". It's 13 megs vs 4.2 megs after second check.

Anyway, try to run Xfree86 + fbdev (and some app) on 32meg device and
you'll see. I understand you want to continue ajaxization, but *please*
keep this stuff in tree for a bit longer, I will be the first who will
want to kill it with fire as soon as Xfree86 fits targets I work on.

-- 
  http://fossarchy.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-devel/attachments/20100208/ec3e2ca6/attachment-0001.pgp