Robert Hancock wrote:
> You missed this code:
name = pci_mmcfg_probes[i].probe();
This calls one of the probe functions above, which will set
pci_mmcfg_config_num to something else, as with the name variable. It
may set the name but not the config num, if the chipset is recognized
but
Scott Ashcroft wrote:
I don't think it makes any change to subsequent flow but the code in
pci_mmcfg_check_hostbridge is:
pci_mmcfg_config_num = 0;
You missed this code:
name = pci_mmcfg_probes[i].probe();
This calls one of the probe functions above, which will set
pci_mmcfg_config_num
Scott Ashcroft wrote:
I don't think it makes any change to subsequent flow but the code in
pci_mmcfg_check_hostbridge is:
pci_mmcfg_config_num = 0;
You missed this code:
name = pci_mmcfg_probes[i].probe();
This calls one of the probe functions above, which will set
pci_mmcfg_config_num
Robert Hancock wrote:
You missed this code:
name = pci_mmcfg_probes[i].probe();
This calls one of the probe functions above, which will set
pci_mmcfg_config_num to something else, as with the name variable. It
may set the name but not the config num, if the chipset is recognized
but
I don't think it makes any change to subsequent flow but the code in
pci_mmcfg_check_hostbridge is:
pci_mmcfg_config_num = 0;
...
if (name) {
printk(KERN_INFO "PCI: Found %s %s MMCONFIG support.\n",
name, pci_mmcfg_config_num ? "with" : "without");
}
So it will always
I don't think it makes any change to subsequent flow but the code in
pci_mmcfg_check_hostbridge is:
pci_mmcfg_config_num = 0;
...
if (name) {
printk(KERN_INFO PCI: Found %s %s MMCONFIG support.\n,
name, pci_mmcfg_config_num ? with : without);
}
So it will always prints
6 matches
Mail list logo
