linux-kernel - Question about aper_size

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>] [day] [month] [year] [list]

Message-ID: <20060823091433.316970@gmx.net>
Date:	Wed, 23 Aug 2006 11:14:33 +0200
From:	"Gerhard Pircher" <gerhard_pircher@....net>
To:	linux-kernel@...r.kernel.org
Subject: Question about aper_size_info structs in agp.h

Hi,

I was wondering about the differences between the aperture size types defined in agp.h. As far as I understand the size_value field in the aper_size_info_8/16/32 structs just defines the value to be set in the AGP bridge registers to configure a specific AGP aperture size (e.g. 8 MB, 16MB, etc..).

Wouldn't it be sufficient to define size_value as 32 bit only, or does the type of size_value/aper_size_info_x have an influence on the generation of the graphics address remapping table (e.g. address alignment) ?

For example the uninorth driver uses the aper_size_info_32 struct to define the AGP aperture size, but only defines values between 1 and 64 for the size_value field (so aper_size_info_8 would be sufficient).

BTW: Can anybody explain the format of the graphics address remapping table or point me to some docs where it is described?

regards,

Gerhard

-- 

Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
-
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/