Summary: | SiS760 chipset not supported for AMD64 agpgart | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Scott Fudally <sfudally> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | Keywords: | Inclusion |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to add PCI ID for SiS760 |
Description
Scott Fudally
2005-06-16 18:42:16 UTC
Created attachment 61364 [details, diff]
Patch to add PCI ID for SiS760
kernel team: Can we add this to the gentoo patchset? It seems trivial. This device is supported by the sis-agp driver You cannot select the sis-agp driver on amd64 - you have to use the amd64-agp driver. The kconfig parameters prevent it. Ok, where has the patch come from? Has it been submitted upstream? I sent the patch to the the two maintainers listed in the amd64-agp.c file but I did get a reply. I suggest you read Documentation/SubmittingPatches and re-submit if you did not do it exactly as described there. (In reply to comment #6) > I sent the patch to the the two maintainers listed in the amd64-agp.c file but I > did get a reply. Sorry, I misread this comment. If you did get a reply, what did they say? I have not received a reply from either maintainer. I wanted to get the patch at least into the Gentoo kernel so I do not have to manually re-patch my kernel. Any recommendations on another place to submit the patch? Have you read Documentation/SubmittingPatches? (Feel free to confirm the details here before you send it...) Bump.. Any progress on this? Would you like me to submit the patch for you? Yes, if you would not mind. I did not get any replies to my original submission and I do not have time right now to persue it further. Done, awaiting response Ok, its accepted into 2.6.13-rc1. I'm not going to include this in gentoo-sources, because its non-critical and you can work around it quite easily: If you have built agpgart into the kernel, boot with agp=try_unsupported If its built as module, load it with parameter agp_try_unsupported=1 Thanks for the report. |