| Summary: | Modify agp_via.c to recognize VIA Apollo KT133A | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | jmcoopr <jmcoopr> | ||||
| Component: | kern | Assignee: | dfr | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Unspecified | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
jmcoopr
2001-08-25 01:00:00 UTC
Change 82C8363 to just 8363. The North Bridge (which supplies the AGP services for the KT133A chipset) doesn't have an 82C prefix. jmc After a cvsup/rebuild last night, I'm now noticing that pci1b is now reporting pcib1: <PCI to PCI bridge (vendor=1106 device=8305)> at device 1.0 on pci0 This is also the Northbridge, it should state instead: pcib1: <VIA 8363 (Apollo KT133A) PCI to PCI bridge> at device 1.0 on pci0 -- jmc I "hear" rumors that some/all of what I have discussed in this PR has been applied to -CURRENT (but I don't know for sure as I don't have a -CURRENT machine). Given the relative innocuous nature of these patches (code is strictly concerned with correctly ID'ing installed hardware and does not (currently) affect kernel function in any way, is there a special reason these patch(s) have not been MFC'ed? Also, it would be nice to have someone "responsible," especially if work is actually be done on it somewhere. -- jmc State Changed From-To: open->closed MFC'ed. Responsible Changed From-To: freebsd-bugs->dfr |