From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: nvidia on sparc32
Date: Sat, 8 Apr 2006 01:39:17 -0700 [thread overview]
Message-ID: <20060408013917.00bd96ee.akpm@osdl.org> (raw)
In-Reply-To: <20060408.012707.80122971.davem@davemloft.net>
"David S. Miller" <davem@davemloft.net> wrote:
>
> From: Andrew Morton <akpm@osdl.org>
> Date: Sat, 8 Apr 2006 01:21:07 -0700
>
> > In file included from drivers/video/nvidia/nv_setup.c:50: include/video/vga.h:24:21: asm/vga.h: No such file or directory
> >
> > Dave, do you think a copy of the sparc64 vga.h will suffice?
>
> Sure, but none of this is ever likely to work.
>
> FWIW, all sparc32 systems with PCI have internal devices only and no
> PCI add-in cards, and they'll never see an NVIDIA device.
>
> So it's a different situation than sparc64 where someone could put an
> NVIDIA card into a PCI slot and we'd like that to work.
>
> I wish there were an easy way to eliminate nonsense configuration
> combinations for a given platform.
hm, OK, thanks. Given that it all compiles with the borrowed vga.h, I
guess the simplest thing to do is to run with that - it fixes allmodconfig,
avoids mucking up the Kconfig files and gives us wide compile coverage.
What thinkest thou?
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-08 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 8:21 nvidia on sparc32 Andrew Morton
2006-04-08 8:27 ` David S. Miller
2006-04-08 8:39 ` Andrew Morton [this message]
2006-04-08 9:18 ` David S. Miller
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=20060408013917.00bd96ee.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).