All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: sparclinux@vger.kernel.org
Subject: Re: Access to older 64-bit sparcs for developers
Date: Thu, 29 Jun 2017 07:18:40 +0000	[thread overview]
Message-ID: <934876c4-ac57-4b1d-e606-bb9ce3a0e753@ilande.co.uk> (raw)
In-Reply-To: <alpine.LRH.2.20.1706271559250.28262@math.ut.ee>

On 28/06/17 21:37, David Miller wrote:

> From: chase rayfield <cusbrar1@gmail.com>
> Date: Wed, 28 Jun 2017 16:32:06 -0400
> 
>> David, is that an XVR-100 or something newer? Mine doesn't work with
>> my Gentoo installation currently beyond the console... if so what
>> Distro/Release are you on? Maybe I can match to that and get it
>> working.
> 
> It's a built-from-source X server on an old debian install from
> about 5 years ago.

Is that using drm at all? As per my post a while back, I'm still
chipping away at trying to get the bochs_drm framebuffer fired up in
QEMU's sun4u.

So far I've managed to figure out that I need to add Simba support to
QEMU which is taking longer than expected as various OSs make
assumptions about the interrupt-swizzling for Ultra 5 on-board devices.

However outside of the interrupt issues, I now have something that
seemingly boots a kernel built from source and initialises the IOMMU
correctly. Now all I need to do now is figure out why the DRM memory
mapping routines never map the framebuffer to a virtual address and
always fallback to returning the physical address...


ATB,

Mark.


  parent reply	other threads:[~2017-06-29  7:18 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 [this message]
2017-06-29 15:23 ` David Miller
2017-06-29 19:32 ` Mark Cave-Ayland
2017-06-29 20:10 ` David Miller
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=934876c4-ac57-4b1d-e606-bb9ce3a0e753@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --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.