On Mon, 15 Sep 2003 03:59:22 +0300 Ville Syrj�l� wrote: > On Sun, Sep 14, 2003 at 09:43:35AM +0000, Sarfraz Nawaz wrote: > > 1) Without applying any patches fbset -i shows 16MB of ram > > 2) Cant find the patch for 2.4.22. So I applied the patch that came > with > > Directfb. fbset -i shows something like 25MB (cant remember exactly but > > definitely more than 16MB). > > It's probably 24MB. The 8MB is stolen by matroxfb_crtc2. Either don't > load it or give it mem=0 parameter. > > > Directfb app run fine. When the fb app exits > > and I run something on console which dumps a lot of text output (say > > make), the console becomes black after a few hundred lines of text and > > then I see garbled gray images much like the fb application. > > That sounds like you're using the old 32mb-patch. The full-memory patch > shouldn't break console acceleration. Either way you can fix it by > limiting vyres so that things stay under 16MB. > > -- > Ville Syrj�l� > [EMAIL PROTECTED] > http://www.sci.fi/~syrjala/ > > > -- > Info: To unsubscribe send a mail to [EMAIL PROTECTED] with > "unsubscribe directfb-users" as subject. > > I've applied the full memory patch that came with Directfb-0.19 and things seem to work fine for the time being. fbset -i shows 32Meg. The vsync patch however, fails.
I still cannot get Directfb to compile with profiling support. I am not using the fusion patch. Everything compiles fine with --enable-profiling. But when I run anything like dfbinfo it seg faults. Is there any other way to profile a Directfb program. Regards This message powered by EMUmail. http://EMUmail.com ����칻 �&ޱ��jf��� q���b��-}�+����칻 �&�v*�r�ۺǫ��,���r
