https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760
Rajesh <rajf...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rajf...@gmail.com
--- Comment #6 from Rajesh <rajf...@gmail.com> ---
I face the same issue, but only when I enable a EMMC device which is enumerated
by ACPI. Debugged whether the ACPI device is conflicting with the PCI MMIO
space using the ACPI DSDT tables, but seems they are not conflicting.
What I understand is, when we have hw.pci.mcfg=0, seems FreeBSD does
port-mapped access to PCI config space, rather than memory mapped access. How
this is related to the multi-function device theory mentioned here?
pciconf(8) man page says,
"If the most significant bit of the header type register is set for function 0
of a PCI device, it is a multi-function device, which contains several (similar
or independent) functions on one chip."
In my pciconf output, I don't see any device with the MSB bit set. But I see
multi-function devices listed. I assume the pciconf output should be read as
"driver@pci<unit>.<bus>.<device>.<function>".
So, Is pciconf output not proper? How can we debug which multi-function device
creates the problem here?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
