linux-kernel - Re: [PATCH -mm] video: uvesafb: Add X86 dependency.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070911115346.GA23493@linux-sh.org>
Date:	Tue, 11 Sep 2007 20:53:46 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Paulo Marques <pmarques@...popie.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Michal Januszewski <spock@...too.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] video: uvesafb: Add X86 dependency.

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/