From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: maurie <maurie@risc.sps.mot.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Vga on sandpoint
Date: Tue, 07 Oct 2003 23:28:03 +0200 [thread overview]
Message-ID: <1065561997.31018.54.camel@gaston> (raw)
In-Reply-To: <000a01c38ce9$4c8ec740$9b7c520a@sps.mot.com>
On Tue, 2003-10-07 at 17:40, maurie wrote:
> Linuxppc developers,
>
> I am attempting to get pci vga working on the sandpoint platform
> using dink32 to start linux. I have tried several S3 cards with no video
> success. The kernel has vga driver support for SIS and ATI support, but
> these are classified as experimental and will not compile, undefined
> externals for __floatsidf, __divdf3, __adddf3, __fixunsdfsi, __muldf3, and
> __vmalloc.
What kernel is this exactly ? Those symbols seem to imply something
is trying to do floating point in the kernel, which is totally
forbidden. Most video cards need to be soft-booted (POSTed) some way
before a kernel driver can use them. This require some firmware support,
typically an x86 BIOS emulator, do you have that in dink32 ? Some
fbdev's, afaik, can run a card booted from scratch (I think Matroxfb
with earlier cards and some clgen but I don't know the details).
Regarding __vmalloc, that should be defined (and exported) by the
core kernel.
Now, regarding he availability of the VGA space, that depends how
your host bridge is configured, do you have a pass-through window
to legacy VGA addresses on the PCI ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-07 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 15:40 Vga on sandpoint maurie
2003-10-07 21:28 ` Benjamin Herrenschmidt [this message]
2003-10-08 14:49 ` Tom Rini
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=1065561997.31018.54.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=maurie@risc.sps.mot.com \
/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).