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: <XNM1$9$0$4$$3$3$7$A$9002705U45372f1d@hitachi.com>
Date:	Thu, 19 Oct 2006 16:54:19 +0900
From:	<eiichiro.oiwa.nm@...achi.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<alan@...hat.com>, <jesse.barnes@...el.com>, <greg@...ah.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re:pci_fixup_video change blows up on sparc64

>
>This change in 2.6.19-GIT:
>
>commit b5e4efe7e061ff52ac97b9fa45acca529d8daeea
>Author: eiichiro.oiwa.nm@...achi.com <eiichiro.oiwa.nm@...achi.com>
>Date:   Thu Sep 28 13:55:47 2006 +0900
>
>    PCI: Turn pci_fixup_video into generic for embedded VGA
>
>breaks sparc64 with ATI Radeon and ATY128 cards.
>
>The problem is that there is no system rom at 0xc0000 on sparc64, and
>therefore nothing copies the VGA bios of the graphics card there on
>bootup.  Therefore all of this code is bogus and will just result in
>bus errors when the Radeon or ATY128 driver tries to pci_map_rom() and
>read the graphics card ROM.  Nothing will respond to accesses at the
>0xc0000 region on sparc64.
>
>The existence of a primary video ROM at 0xc0000 is quite platform
>specific.  If some non-x86 systems have this too, that's great.
>However, assuming all systems do is not correct.
>

Does ATI Radeon card have an expansion ROM (video ROM)?
Could you show me "lspci -vv" on sparc64?

If an expansion ROM exists on ATI Radeon or ATY128 card, pci_map_rom returns
the expansion ROM base address instead of 0xC0000 because fixup_video checks
the VGA Enable bit in the Bridge Control register.
The Bridge Control register describes in "PCI-to-PCI Bridge Architecture
Specification Revision 1.2".
This specification is the standard specification in PCI.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ