From: Alex Buell <alex.buell@munted.org.uk>
To: linux-fbdev@vger.kernel.org,
Mailing Lists - Kernel Developers <linux-kernel@vger.kernel.org>
Subject: Using s3virge card in Sun Blade 2000
Date: Mon, 03 Jan 2011 16:32:16 +0000 [thread overview]
Message-ID: <1294072336.17576.7.camel@lithium> (raw)
Hi!
I hope the fbdev list is still in use. I have just been experimenting
with using my old S3ViRGE PCI card in my Sun Blade 2000 as its primary
display adapter has no X11 driver available for it.
I put the card into my SPARC and booted up, after compiling in the s3fb
driver into the kernel.
On boot-up, it uses the e3d framebuffer driver, and detects the s3fb
card but ignores it as seen in dmesg:
s3fb 0000:00:03.0: ignoring secondary device
I then pulled out the primary graphic card (XVR-500) and rebooted. I got
the following lines in dmesg:
vgaarb: device added: PCI:0000:00:03.0,decodes=io
+mem,owns=mem,locks=none
vgaarb: loaded
s3fb 0000:00:03.0: ignoring secondary device
It seems a bit odd that it is still ignoring the S3ViRGE card given that
it is now the only graphic adapter in the system.
I then commented out the following code in drivers/video/s3fb.c:
if (! svga_primary_device(dev)) {
dev_info(&(dev->dev), "ignoring secondary device\n");
return -ENODEV;
}
and rebooted.
It got as far as the switching to console device before it hung.
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.
Thanks!
--
Tactical Nuclear Kittens
next reply other threads:[~2011-01-03 16:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 16:32 Alex Buell [this message]
2011-01-03 18:58 ` Using s3virge card in Sun Blade 2000 David Miller
2011-01-03 19:39 ` Alex Buell
2011-01-03 19:43 ` David Miller
2011-01-03 20:33 ` Alex Buell
2011-01-03 20:39 ` David Miller
2011-01-03 21:36 ` Alex Buell
2011-01-03 22:36 ` David Miller
2011-01-04 15:57 ` Alex Buell
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:38 ` Alex Buell
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:50 ` Alex Buell
2011-01-06 22:24 ` Alex Buell
2011-01-06 22:29 ` David Miller
2011-01-06 23:25 ` Alex Buell
2011-01-06 23:34 ` Alex Buell
2011-01-03 20:37 ` Dave Airlie
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=1294072336.17576.7.camel@lithium \
--to=alex.buell@munted.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).