Page 62 of 111 FirstFirst ... 1252606162636472 ... LastLast
Results 611 to 620 of 1109

Thread: "Ask ATI" dev thread

  1. #611
    Join Date
    Mar 2009
    Posts
    54

    Default

    Quote Originally Posted by bridgman View Post
    Is that a flash video or something ? I would expect video playback to be faster on the open drivers than on fglrx these days; this should be fixable today.
    Flash!

    And I also tried the Adobe hack by creating /etc/adobe/mms.cfg and adding a line:

    OverrideGPUValidation=true

    in it.

  2. #612
    Join Date
    Mar 2009
    Posts
    54

  3. #613
    Join Date
    Mar 2009
    Posts
    54

    Default

    I cannot get TV-in working with the open source driver.

    I tried several options:

    (**) RADEON(0): Option "RageTheatreCrystal" "2950"
    (**) RADEON(0): Option "RageTheatreTunerPort" "0"
    (**) RADEON(0): Option "RageTheatreCompositePort" "2"
    (**) RADEON(0): Option "RageTheatreSVideoPort" "6"
    (**) RADEON(0): Option "TunerType" "0"
    (**) RADEON(0): Option "RageTheatreMicrocPath" "/usr/lib/xorg/modules/multimedia/ativmc20.cod"
    (**) RADEON(0): Option "RageTheatreMicrocType" "BINARY"
    (**) RADEON(0): Option "DefaultConnectorTable" "on"
    (**) RADEON(0): Option "TVStandard" "PAL"

    But the only output I get in xorg.log:

    (II) Module exa: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 2.4.0
    ABI class: X.Org Video Driver, version 4.1
    (**) RADEON(0): Rage Theatre Crystal frequency was specified as 29.50 Mhz
    (**) RADEON(0): Rage Theatre tuner port was specified as 0
    (**) RADEON(0): Rage Theatre composite port was specified as 2
    (**) RADEON(0): Rage Theatre SVideo Port was specified as 6
    (**) RADEON(0): Tuner type was specified as 0
    (**) RADEON(0): Rage Theatre Microcode path was specified as /usr/lib/xorg/modules/multimedia/ativmc20.cod
    (**) RADEON(0): Rage Theatre Microcode type was specified as BINARY
    (==) RADEON(0): Assuming overlay scaler buffer width is 1920
    (II) RADEON(0): Cannot access BIOS or it is not valid.
    If your card is TV-in capable you will need to specify options RageTheatreCrystal, RageTheatreTunerPort,
    RageTheatreSVideoPort and TunerType in /etc/X11/xorg.conf.
    (!!) RADEON(0): For information on using the multimedia capabilities
    of this adapter, please see http://gatos.sf.net.

    With previous versions of the driver it was no problem.

    Can somebody help me?

  4. #614
    Join Date
    Mar 2009
    Posts
    54

    Default

    opengl screensaver hangs/crashes system with xorg-x11-drv-ati-6.10.0-2.fc10.i386

    https://bugs.launchpad.net/ubuntu/+s...er/+bug/106060

    I changed my settings from gnome-screensaver-preferences using gconf-editor.
    I was using "blocktube" as the preferred screensaver and changed that.

    Now, when I start gnome-screensaver-preferences in a terminal I see:

    ** (gnome-screensaver-preferences:3698): DEBUG: Found best visual for GL: 0x21
    Last edited by Mr_Ed; 03-10-2009 at 04:44 PM.

  5. #615
    Join Date
    Mar 2009
    Posts
    41

    Default AMD OpenCL roadmap, brook+

    Hello!

    Is there a time frame, in which we can expect OpenCL from AMD? I mean some kind of roadmap? I'd like to start with GPGPU programming and wonder if I'd start with brook+ or wait for OpenCL. Or use cuda, as it is said to be similar to OpenCL -- I need a new GPU anyways, but I'd prefer to stick to AMD. According to the AMD homepage there will be a migration way to OpenCL when it is ready. Does anybody know about it?

    By the way, NVidia has presented this roadmap:

    http://www.geeks3d.com/?p=2582&lang=de

    Thanks for your help,

    Olaf

  6. #616
    Join Date
    Jun 2008
    Posts
    26

    Default

    I would suggest waiting for OpenCL. CUDA is fairly similar, but it will be (for the most part) proprietary to nVidia parts, whereas OpenCL looks to be what will be the industry standard and much more versatile.

  7. #617
    Join Date
    Mar 2009
    Posts
    41

    Default

    Hi!

    > I would suggest waiting for OpenCL.
    Ultimately I'll switch to OpenCL, but the question is when it will be usable. I guess it will still take half a year (which is too long to wait), but I hope ATi is quicker. That's why I pose this question ;-)

  8. #618

    Default

    It looks like AMD is getting ready to finally answer these questions... This thread will be locked shortly, so if you have any last minute, relevant questions, ask them now, The answers should be out in April.

  9. #619
    Join Date
    Dec 2007
    Location
    /dev/hell
    Posts
    297

    Default

    Quote Originally Posted by Michael View Post
    It looks like AMD is getting ready to finally answer these questions... This thread will be locked shortly, so if you have any last minute, relevant questions, ask them now, The answers should be out in April.
    ok, so, 2 questions:

    one on the fglrx side: (i'm sure an answer has already be given, but i forgot it)
    - Is fglrx going to implement KMS? if not, why not?

    two on the documentation release plan:
    - how is Power Management documentation going? how is the plan to provide it to the public?
    - are you thinking about re releasing the r200 docs?

    thanks

  10. #620
    Join Date
    Dec 2007
    Location
    /dev/hell
    Posts
    297

    Default

    Dear ATi guys, why did you put a fetch restriction on amd stream sdk!?!?!?
    I don't absolutely want to register to you website, just to be able to update my amd-stream-sdk ebuilds!
    It's nice to see you ported some new tools to linux, but putting a fetch restriction just keeps interested people away!

    that's not the right way to go!!!

    Michael, what about writing an article about this horrible decision?? thanks in advance.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •