Hi, > Let's deal with the first one. It seems like a real problem because > it distracts people debugging other problems. The second should be > filed as a separate bug if you are interested in working on it. > [snip] > > The test has been that way ever since v2.6.15-rc1~731^2~22^2~13 > (shpchp: detect SHPC capability before doing a lot of work, > 2006-10-13). The false positive (if it actually is a false positive) > is clearly harmless. If someone wants to remove the "if (dev->vendor > == PCI_VENDOR_ID_AMD)" exception, it would be necessary to research > why it is there in the first place (are there AMD hotplug controllers > that do not advertise the shpc capability for which that exception is > needed?) and if so, what a more precise exception to solve the same > problem would be. > > If interested, please take this upstream (that means the > [email protected] list) and let us know the message-ID. > Otherwise I will probably mark this bug as wontfix or close it, since > without someone doing the research just mentioned, it seems expensive > to fix, without much benefit. The problem is, I have got no experience whatsoever with kernel or driver development (e.g., I never heard "shpc" before), I didn't even compile a kernel myself yet. I do a lot of programming, but it's all user-space. I am willing to learn though, and for the next few weeks I even got the time (no university currently). Do you think that will suffice to carry this to the kernel mailing list?
Kind regards, Ralf -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
