From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 118701] x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device
Date: Mon, 23 May 2016 21:39:00 +0000 [thread overview]
Message-ID: <bug-118701-2300-cH6rK1wSRe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118701-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=118701
--- Comment #2 from Stuart Foster <smf.linux@ntlworld.com> ---
(In reply to Patrik Jakobsson from comment #1)
> Hi Stuart
>
> Did you try with a 64-bit userspace? I haven't tried gma500 on a 64-bit
> system so not sure what the status is. GPU can only address 32-bit so there
> could be interesting problems.
Hi Patrik,
No I have not tried a 64-bit userspace. I only planned on using a 32-bit user
space. I use LFS/BLFS for my systems so I could try and build a cut down 64-bit
user space if you think it will help. These are not the quickest machines so it
may take me some time.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-23 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 10:08 [Bug 118701] New: x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device bugzilla-daemon
2016-05-23 20:07 ` [Bug 118701] " bugzilla-daemon
2016-05-23 21:39 ` bugzilla-daemon [this message]
2016-05-24 22:44 ` bugzilla-daemon
2016-05-25 7:40 ` bugzilla-daemon
2016-05-25 21:36 ` bugzilla-daemon
2016-05-27 7:39 ` bugzilla-daemon
2016-08-08 7:28 ` bugzilla-daemon
2017-02-13 13:45 ` bugzilla-daemon
2017-02-14 8:34 ` 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-118701-2300-cH6rK1wSRe@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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.