From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Access to older 64-bit sparcs for developers
Date: Thu, 29 Jun 2017 20:10:37 +0000 [thread overview]
Message-ID: <20170629.161037.1268834998589565501.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1706271559250.28262@math.ut.ee>
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Date: Thu, 29 Jun 2017 20:32:56 +0100
> On 29/06/17 16:23, David Miller wrote:
>
>> From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> Date: Thu, 29 Jun 2017 08:18:40 +0100
>>
>>> Is that using drm at all?
>>
>> Using DRM fully.
>
> So I guess it must be something that bochs_drm is specifically doing?
Who knows, it means that DRM hasn't been tested and tracked on sparc64
since I got the radeon working several years ago.
When I'm in front of that computer in a few weeks I can try to play
with things again.
next prev parent reply other threads:[~2017-06-29 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 13:21 Access to older 64-bit sparcs for developers Meelis Roos
2017-06-27 18:42 ` David Miller
2017-06-28 8:43 ` Julian Calaby
2017-06-28 8:56 ` John Paul Adrian Glaubitz
2017-06-28 16:32 ` chase rayfield
2017-06-28 17:03 ` John Paul Adrian Glaubitz
2017-06-28 19:42 ` David Miller
2017-06-28 20:32 ` chase rayfield
2017-06-28 20:35 ` John Paul Adrian Glaubitz
2017-06-28 20:37 ` David Miller
2017-06-29 7:18 ` Mark Cave-Ayland
2017-06-29 15:23 ` David Miller
2017-06-29 19:32 ` Mark Cave-Ayland
2017-06-29 20:10 ` David Miller [this message]
2017-06-29 22:09 ` Mark Cave-Ayland
2017-06-30 0:36 ` David Miller
2017-06-30 19:06 ` Mark Cave-Ayland
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=20170629.161037.1268834998589565501.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.kernel.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.