All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26745] New: mach64 driver missing 32-bit ioctl compatibility routines
Date: Wed, 24 Feb 2010 20:09:45 -0800 (PST)	[thread overview]
Message-ID: <bug-26745-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26745

           Summary: mach64 driver missing 32-bit ioctl compatibility
                    routines
           Product: DRI
           Version: XOrg CVS
          Platform: SPARC
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libdrm
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: matt__m@hushmail.com


Created an attachment (id=33548)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=33548)
Xorg.log showing issue with mach64 dri on 64bit sparc kernel / 32bit userland

i've run into some issues trying to get dri going using mach64.ko and drm.ko
from libdrm-2.4.14 and 2.4.15.

hardware versions:
sunblade 2000, 2x ultrasparc 1.05ghz
ati pgx64 graphics (pci bus id: 1002:4752)

software versions:
kernel 2.6.32.8, 64-bit sparc64 (gentoo)
xorg server 1.6.5, 32bit
xf86-video-mach64 6.8.2 32bit
libdrm 2.4.15 32bit
mesa 7.5.2 32bit

libdrm kernel module builds and loads using sparc64 gcc version 4.3.4

any attempt to use the interface provided via /dev/dri/card0 results in:
[92201.864512] [drm] Initialized drm 1.1.0 20060810
[92203.149358] [drm] Initialized mach64 2.0.0 20060718 on minor 0
[92203.149394] [drm] Used old pci detect: framebuffer loaded
[92220.481429] ioctl32(X:20584): Unknown cmd fd(6) cmd(c0246400){t:'d';sz:36}
arg(001ec180) on /dev/dri/card0
[92220.481627] ioctl32(X:20584): Unknown cmd fd(6) cmd(c0246400){t:'d';sz:36}
arg(001ec180) on /dev/dri/card0
[92220.486733] ioctl32(X:20584): Unknown cmd fd(6) cmd(c0106407){t:'d';sz:16}
arg(ffe37378) on /dev/dri/card0
[92220.486759] ioctl32(X:20584): Unknown cmd fd(6) cmd(c0086401){t:'d';sz:8}
arg(ffe37380) on /dev/dri/card0
[93697.163487] ioctl32(drmstat:20956): Unknown cmd fd(3)
cmd(c0246400){t:'d';sz:36} arg(00026008) on /dev/dri/card0
[93697.163608] ioctl32(drmstat:20956): Unknown cmd fd(3)
cmd(c0106407){t:'d';sz:16} arg(ff9e6d00) on /dev/dri/card0
[93697.163630] ioctl32(drmstat:20956): Unknown cmd fd(3)
cmd(c0086401){t:'d';sz:8} arg(ff9e6d08) on /dev/dri/card0

also attached is an Xorg.log displaying the issue.

the card's (PGX64) pci bus id (is listed in libdrm's shared-core/drm_pciids.txt
under the mach64 driver: 0x1002 0x4752 0 "Rage XL"

i've spotted a couple other bugs related to using these drivers with 64bit
kernel and 32bit userland:
http://bugs.freedesktop.org/show_bug.cgi?id=22271
http://bugs.freedesktop.org/show_bug.cgi?id=23816

most of the other modules have been adjusted, using something like:
'.compat_ioctl = radeon_compat_ioctl' and radeon_ioc32.c, though this is
missing for the mach64 module.

sparc/linux has very few options for graphics, and it seems like fixing this
driver's ioctl32 compatibility could help a couple other archs as well.

thanks for your consideration,
-matt


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-02-25  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  4:09 bugzilla-daemon [this message]
2019-05-29 17:20 ` [Bug 26745] mach64 driver missing 32-bit ioctl compatibility routines 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-26745-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.