[haiku-bugs] Re: [Haiku] #2769: Radeon driver is Slower than VESA ...
- From: "stippi" <trac@xxxxxxxxxxxx>
- Date: Wed, 06 Jun 2012 12:42:01 -0000
#2769: Radeon driver is Slower than VESA ...
---------------------------------------+---------------------------
Reporter: herdemir | Owner: euan
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: Drivers/Graphics/radeon | Version: R1/pre-alpha1
Resolution: | Keywords:
Blocked By: | Blocking: 7662
Has a Patch: 0 | Platform: All
---------------------------------------+---------------------------
Comment (by stippi):
Replying to [comment:32 mks]:
> I can't notice any flickering on the T23 and I am pretty certain there
wasn't any flickering on the other 2 machines.
I don't remember what kind of trick I pulled to avoid flickering with a
S/W cursor and no double buffering...
> I wanted to start by putting in some test outputs for myself to better
understand, what's going on but I already have some more questions …
>
> How can I properly enable the trace output in app_server? There is a
DEBUG_DRIVER_MODULE ifdef at the top of AccelerantHWInterface, but how can
I tell jam to enable this? Also, where do those trace outputs appear?
I can only think of two easy methods to see debug output.
* One is to run Haiku in emulation, QEMU/KVM for example, and enable
serial debug output to arrive in the Terminal where you start the
emulation. QEMU at least used to have an easy option for this, something
like "--serial=stdout" or similar. I am relatively sure that I used this
before and also simple output like "printf" arrived in the Terminal
running QEMU. I don't think I needed dprintf() or stuff like that.
* The second option is to run the "app_server test environment". The
app_server supports being build as a regular Haiku application that runs
inside a window. It's actually quite complicated behind the scenes with
applications having to use the right "libbe" to run inside the test
app_server. To build this setup, go into src/test/servers/app and run
"TARGET_PLATFORM=libbe_test jam install-test-apps". And then inside that
directory, there is a script called "run" which you can use to launch any
of the test apps in that directory within the test app_server. You can use
any test app, doesn't matter, but that will launch the test app_server.
Thinking about it, however, the second option is probably totally useless,
since in this case, the AccelerantHWInterface is not used, but the
ViewHWInterface is used instead (it's running inside a BWindow/BView...
not on an accelerated graphics card). So the second option is nice to test
other stuff, but you probably have to use the first option.
> Regarding the memory speed measuring: I guess I need to do this with
fFrameBufferConfig.frame_buffer(_dma?). Do I understand you correctly,
that I only have to get the time needed to read/write a (few) frame(s)?
Yes. You should be able to use the same memory address that is used for
attaching the front buffer a little later in SetMode(). I wouldn't even
read for long, since that will directly delay the boot process, a short
test is hopefully reliable enough.
> And lastly: Should I rather take my questions to the mailing list, or is
it Ok right here in the ticket?
Either is fine, I guess. Sometimes communication gets more direct/easier
with the mailing list, but your findings are better preserved here for the
generations to come.
--
Ticket URL: <http://dev.haiku-os.org/ticket/2769#comment:33>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
