From: Paul Mundt <lethal@linux-sh.org>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Januszewski <spock@gentoo.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] video: uvesafb: Add X86 dependency.
Date: Tue, 11 Sep 2007 20:53:46 +0900 [thread overview]
Message-ID: <20070911115346.GA23493@linux-sh.org> (raw)
In-Reply-To: <46E67EFD.2040902@grupopie.com>
On Tue, Sep 11, 2007 at 12:41:49PM +0100, Paulo Marques wrote:
> Paul Mundt wrote:
> >uvesafb is x86-specific, reflect that in the Kconfig.
>
> Hummm... uvesafb _shouldn't_ be x86 specific. At least according to
> their page [1] where it says: "works on non-x86 systems".
>
> Uvesafb uses a x86 emulator in userspace to run code from the video card
> ROM, so it should work on any PCI system where we can access the video
> card ROM and can emulate the hardware used by the ROM code.
>
> Why do you say that it's x86 specific? Am I missing something?
>
The emulator it uses only runs on x86 and x86_64. Thus, it's x86
specific. The v86d and uvesafb pages seem to be in disagremeent, unless
by 'non-x86' it's only implying x86_64.
Additionally, it needs the vga I/O routines, as per vgacon. Most
platforms don't define these.
next prev parent reply other threads:[~2007-09-11 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 8:17 [PATCH -mm] video: uvesafb: Add X86 dependency Paul Mundt
2007-09-11 11:41 ` Paulo Marques
2007-09-11 11:53 ` Paul Mundt [this message]
2007-09-11 12:19 ` Paulo Marques
2007-09-11 12:31 ` Paul Mundt
2007-09-11 22:59 ` Michal Januszewski
2007-09-11 23:09 ` [PATCH -mm] uvesafb: Don't access VGA registers directly when running on non-x86 Michal Januszewski
2007-09-12 0:44 ` Paul Mundt
2007-09-12 19:41 ` Michal Januszewski
2007-09-13 1:43 ` Paul Mundt
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=20070911115346.GA23493@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=spock@gentoo.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