On Mon, May 03, 2004 at 03:34:48PM -0700, carbonated beverage wrote: > On Mon, May 03, 2004 at 12:58:28PM -0500, Branden Robinson wrote: > > 1) Is this a Linux 2.6-specific problem? > > 2) Are you the author of the patch? If not, can you tell me where you > > got it? > > Not sure, I haven't run 2.4.x on the box in a while. I can test later tonight > when I have access to it again (at work right now). > > Yes, I wrote the patch, but I'm not entirely sure it's correct. The only > box I have that exports PCI domain information under Linux right now is the > Ultra 5, so the code will have to be exercised a bit more under other > platforms to ensure it works correctly on other systems and that it's the > right fix. On Mon, May 03, 2004 at 10:24:52PM -0700, carbonated beverage wrote: > > 1) Is this a Linux 2.6-specific problem? > > Yup, I just booted 2.4.x to check, and the PCI domain information isn't > there in /proc. It's just using /proc/bus/pci/<bus>/<dev>.<func> > > In 2.6.x, there doesn't seem to be a way to turn it off from the config > interface. I manually edit .config and do a make oldconfig, and it gets > set again. In 2.4.x, I can't find a way to turn it on via the config > proggies. Outstanding. You've confirmed as well that your patched X server doesn't get confused on 2.4.x, then? If your patch works as intended and causes no breakage both on 2.4.x and 2.6.x, then it's probably good enough for us to apply. Please confirm (or correct) my understanding of the situation. -- G. Branden Robinson | Don't use nuclear weapons to Debian GNU/Linux | troubleshoot faults. branden@debian.org | -- US Air Force Instruction 91-111 http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature