All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Buell <alex.buell@munted.org.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Using s3virge card in Sun Blade 2000
Date: Mon, 03 Jan 2011 19:39:01 +0000	[thread overview]
Message-ID: <1294083541.17576.11.camel@lithium> (raw)
In-Reply-To: <20110103.105827.112602895.davem@davemloft.net>

On Mon, 2011-01-03 at 10:58 -0800, David Miller wrote:
> From: Alex Buell <alex.buell@munted.org.uk>
> Date: Mon, 03 Jan 2011 16:32:16 +0000
> 
> > I'm aware the s3fb driver has big endian issues, I can help fix those
> > issues so I can get the card working. Or in other words, I'd welcome
> > advice on how to proceed with this. 
> 
> It's not endian issues, this driver has other problems.
> 
> It uses the VGA register accessors with a NULL regbase, which is not
> going to work on sparc64.
> 
> It needs to access the VGA register space relative to the I/O space
> of the PCI controller domain it is behind.
> 
> Probably if you replace the NULL values passes to vga_r*() and
> vga_w*() with the I/O space resource base of the chip (should be
> resource "1") it might work.

I've had a look at linux/include/video/vga.h, and yes I see what you
mean now.

Secondly, is Linux fully capable of handling different graphic cards
simultaneously? For example, plug in a pair of monitors and have
consoles on both with disparate graphic cards i.e. XVR-500 and S3ViRGE
etc? 
-- 
Tactical Nuclear Kittens

  reply	other threads:[~2011-01-03 19:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 16:32 Using s3virge card in Sun Blade 2000 Alex Buell
2011-01-03 18:58 ` David Miller
2011-01-03 18:58   ` David Miller
2011-01-03 19:39   ` Alex Buell [this message]
2011-01-03 19:43     ` David Miller
2011-01-03 19:43       ` David Miller
2011-01-03 20:33       ` Alex Buell
2011-01-03 20:39         ` David Miller
2011-01-03 20:39           ` David Miller
2011-01-03 21:36           ` Alex Buell
2011-01-03 21:36             ` Alex Buell
2011-01-03 22:36             ` David Miller
2011-01-03 22:36               ` David Miller
2011-01-04 15:57               ` Alex Buell
2011-01-04 17:26                 ` David Miller
2011-01-04 17:26                   ` David Miller
2011-01-04 20:11                   ` Alex Buell
2011-01-04 20:19                     ` David Miller
2011-01-04 20:19                       ` David Miller
2011-01-04 20:38                       ` Alex Buell
2011-01-05 19:07             ` David Miller
2011-01-05 19:07               ` David Miller
2011-01-05 21:13               ` Alex Buell
2011-01-06  0:33                 ` Alex Buell
2011-01-06 20:42                   ` Francois Romieu
2011-01-06 20:42                     ` Francois Romieu
2011-01-06 20:50                     ` Alex Buell
2011-01-06 22:24                       ` Alex Buell
2011-01-06 22:29                         ` David Miller
2011-01-06 22:29                           ` David Miller
2011-01-06 23:25                           ` Alex Buell
2011-01-06 23:25                             ` Alex Buell
2011-01-06 23:34                           ` Alex Buell
2011-01-03 20:37     ` Dave Airlie
2011-01-03 20:37       ` Dave Airlie
2011-01-05 20:37   ` Geert Uytterhoeven
2011-01-05 20:37     ` Geert Uytterhoeven

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=1294083541.17576.11.camel@lithium \
    --to=alex.buell@munted.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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.