danger/u/
AGP

| Accelerated Graphics Port (AGP) is an obsolete parallel expansion card standard, designed by Intel independently of the PCI-SIG for attaching a video card to a computer system to assist in the acceleration of 3D computer graphics. It was originally designed as a generally compatible successor to PCI-type connections for video cards.


| The AGP slot was separate from the PCI bus, so that the graphics card as the top consumer of bandwidth in a computer system would not have to compete for bandwidth with other devices, while the overall throughput of the system was greatly increased by the addition of another data connection. The separation also allowed for improvements that broke compatibility with the myriad of existing PCI cards and AGP was not required to be a lowest common denominator standard.


| The introduction of more efficient queued transactions on top of PCI made it possible for the graphics card to use system memory directly in many circumstances where regular PCI cards required local copies of the data. Since 2004, AGP and PCI were progressively phased out in favor of PCI Express (PCIe).


| By mid-2008, PCI Express cards dominated the market and only a few AGP models were available, with GPU manufacturers and add-in board partners eventually dropping support for the interface relatively quickly in favor of PCI Express. The analogue of AGP in ISA bus systems was the VESA Local Bus.


| AGP is a superset of the PCI standard, designed to overcome PCI's limitations in serving the requirements of the era's high-performance graphics cards.[2]

The primary advantage of AGP is its independence from the PCI bus, providing a dedicated, point-to-point pathway between the expansion slot(s) and the motherboard chipset. The direct connection also allows backward-incompatible changes such as a lower signal voltage, which in turn allows a higher clock speed.


| The second major change is the use of split transactions, wherein the address and data phases (request and response phases) are separated. More than one transaction can be in-flight.


| This allows READ transactions to perform equally well to WRITE transactions, which is hard to achieve with just strictly serial transaction processing where the bus must remain idle (in a wait state) while waiting for the read data access to finish (on the other hand, with or without queues, a "fire and forget" write transaction can be complete when it is received and before the actual memory write completes).


| With AGP's queued transactions, the bandwidth realized can be close to the theoretical maximum bandwidth. AGP has a high priority queue and a low priority queue to allow for fine-grained optimization. This great improvement in memory read performance makes it practical for an AGP card to read textures directly from system RAM, while a PCI graphics card must copy it from system RAM to the card's video memory.


| System memory is made available using the graphics address remapping table (GART), which apportions main memory as needed for texture storage.[4] The maximum amount of system memory available to AGP is defined as the AGP aperture. Thus a trade-off could be realized in which the newly gained bandwidth could be exchanged for a lower parts count (graphics cards with little or no onboard memory).


| Third, AGP allows (mandatory only in AGP 3.0) sideband addressing, meaning that the address and data buses are separated, so the address phase does not use the main address/data (AD) lines at all. This is done by adding an extra 8-bit "SideBand Address" bus, over which the graphics controller can issue new AGP requests while other AGP data is flowing over the main 32 address/data (AD) lines. This results in improved overall AGP data throughput.


| Finally, PCI bus handshaking is simplified. Unlike PCI bus transactions, whose length is negotiated on a cycle-by-cycle basis using the FRAME# and STOP# signals, AGP transfers are always a multiple of 8 bytes long, with the total length included in the request. Further, rather than using the IRDY# and TRDY# signals for each word, data is transferred in blocks of 4 clock cycles (32 words at AGP 8× speed), and pauses are allowed only between blocks.


| The AGP slot first appeared on x86-compatible system boards based on Socket 7 Intel P5 Pentium and Slot 1 P6 Pentium II processors. Intel introduced AGP support with the i440LX Slot 1 chipset on August 26, 1997, and a flood of products followed from all the major system board vendors.[5] AGP was developed by Intel independently of the PCI Special Interest Group, which neither reviewed nor endorsed it.[3]: 20 


| The first Socket 7 chipsets to support AGP were the VIA Apollo VP3, SiS 5591/5592, and the ALI Aladdin V. Intel never released an AGP-equipped Socket 7 chipset. FIC demonstrated the first Socket 7 AGP system board in November 1997 as the FIC PA-2012 based on the VIA Apollo VP3 chipset, followed very quickly by the EPoX P55-VP3 also based on the VIA VP3 chipset which was first to market.[6]


| Early video chipsets featuring AGP support included the Rendition Vérité V2200, 3dfx Voodoo Banshee, Nvidia RIVA 128, 3Dlabs PERMEDIA 2, Intel i740, ATI Rage series, Matrox Millennium II, and S3 ViRGE GX/2. Some early AGP boards used graphics processors built around PCI and were simply bridged to AGP.


| if you can read this, op owes me $10


| This resulted in the cards benefiting little from the new bus, with the only improvement used being the 66 MHz bus clock, with its resulting doubled bandwidth over PCI, and bus exclusivity.


| >>1113386 Intel's i740 was explicitly designed to exploit the new AGP feature set; in fact it was designed to texture only from AGP memory, making PCI versions of the board difficult to implement (local board RAM had to emulate AGP memory), though this was eventually accomplished much later in the form of AGP-to-PCI bridges.


| Microsoft first introduced AGP support into Windows via the USB Supplement patch for OSR2 of Windows 95 in 1997, also known as OSR2.1.[7][b] The first Windows NT-based operating system to receive AGP support was Windows NT 4.0 with Service Pack 3, also in 1997. Linux support for AGP-enhanced fast data transfers was first added in 1999 with the implementation of the AGPgart kernel module.


| With the increasing adoption of PCIe, graphics cards manufacturers continued to produce AGP cards as the standard became obsolete. As GPUs began to be designed to connect to PCIe, an additional PCIe-to-AGP bridge-chip was required to create an AGP-compatible graphics card. The inclusion of a bridge, and the need for a separate AGP card design, incurred additional board costs.


| The GeForce 6600 and ATI Radeon X800 XL, released during 2004–2005, were the first bridged cards.[8][9] In 2009 AGP cards from Nvidia had a ceiling of the GeForce 7 series. In 2011 DirectX 10-capable AGP cards from AMD vendors (Club 3D, HIS, Sapphire, Jaton, Visiontek, Diamond, etc.) included the Radeon HD 2400, 3450, 3650, 3850, 4350, 4650, and 4670. The HD 5000 AGP series mentioned in the AMD Catalyst software was never available.


| There were many problems with the AMD Catalyst 11.2 - 11.6 AGP hotfix drivers under Windows 7 with the HD 4000 series AGP video cards;[10] use of 10.12 or 11.1 AGP hotfix drivers is a possible workaround. Several of the vendors listed above make available past versions of the AGP drivers.


| By 2010, no new motherboard chipsets supported AGP and few new motherboards had AGP slots, however some continued to be produced with older AGP-supporting chipsets.

In 2016, Windows 10 version 1607 dropped support for AGP.[11][unreliable source?] Possible future removal of support for AGP from open-source Linux kernel drivers was considered in 2020.[12][needs update]


| OP clickbaited me with that sexy title


| >>1113413 HTTP Strict Transport Security (HSTS) is a policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks and cookie hijacking. It allows web servers to declare that web browsers (or other complying user agents) should automatically interact with it using only HTTPS connections, which provide Transport Layer Security (TLS/SSL), unlike the insecure HTTP used alone.


| The HSTS Policy is communicated by the server to the user agent via an HTTP response header field named Strict-Transport-Security. HSTS Policy specifies a period of time during which the user agent should only access the server in a secure fashion.[2]: §5.2  Websites using HSTS often do not accept clear text HTTP, either by rejecting connections over HTTP or systematically redirecting users to HTTPS (though this is not required by the specification).


| The consequence of this is that a user-agent not capable of doing TLS will not be able to connect to the site.


|
The protection normally only applies after a user has visited the site at least once, relying on the principle of "trust on first use". The way this protection works is that when a user entering or selecting an HTTP (not HTTPS) URL to the site, the client, such as a Web browser, will automatically upgrade to HTTPS without making an HTTP request, thereby preventing any HTTP man-in-the-middle attack from occurring.


| To counteract this problem, an HSTS preload list maintained by Google Chrome and used by other major web browsers is maintained. If a domain is on this list, the browser skips the initial request and encrypts all communication immediately.[3] Additional domains can be registered at no cost.[4]


| TwT


| Good meme op I approve


| High effort shitposting

Total number of posts: 31, last modified on: Sat Jan 1 00:00:00 1789876552

Refresh