All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 33542] New: radeon: Don't read BIOS in VRAM on SPARC64
Date: Mon, 18 Apr 2011 00:20:46 GMT	[thread overview]
Message-ID: <bug-33542-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=33542

           Summary: radeon: Don't read BIOS in VRAM on SPARC64
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.39-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: detringj@gmail.com
        Regression: No


Created an attachment (id=54572)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=54572)
DRM and Radeon dmesg block containing kernel panic.

Hi!

Hurray!  Radeon KMS works again on SPARC64!  Almost.

Test platform is a Sun Ultra 45.  Test board is a Sun XVR-300 (RV380
0x1002:0x5B64) on a PCI-e bus.

There's a kernel panic when calling igp_read_bios_from_vram() from
radeon_get_bios().  See attached dmesg capture.

Patching around it with

--- a/drivers/gpu/drm/radeon/radeon_bios.c      2011-04-17 19:31:04.000000000
-0500
+++ b/drivers/gpu/drm/radeon/radeon_bios.c      2010-09-28 20:01:22.000000000
-0500
@@ -432,8 +432,10 @@
        uint16_t tmp;

        r = radeon_atrm_get_bios(rdev);
+#if !defined(__sparc__)
        if (r == false)
                r = igp_read_bios_from_vram(rdev);
+#endif /* !__sparc__ */
        if (r == false)
                r = radeon_read_bios(rdev);
        if (r == false) {


gives me a framebuffer console again.  After which, the usual desktop stack
works as well (X11, mesa, textured video).

I'm not sure this is the correct way to code the fix, stylistically speaking. 
Although I don't know of any sparc64 machines sporting a Radeon IGP, I'm sure
it could happen someday.  It also seems other architectures might run into this
as well.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

             reply	other threads:[~2011-04-18  0:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  0:20 bugzilla-daemon [this message]
2011-04-18  6:47 ` [Bug 33542] radeon: Don't read BIOS in VRAM on SPARC64 bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-33542-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.