https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #132 from Mark Millard <[email protected]> --- (In reply to Mark Millard from comment #126, #128, #131) Interesting finding? . . . I've tested putting the -mcpu=cortex-a72 based kernel on the cortext-a53 system and . . . The result boots and operates fine. (It is also a USB3 SSD based root file system.) But the xhci context (from the cortext-a53 system) is: # dmesg -a | grep -i xhci xhci0: <Synopsys Designware DWC3> mem 0xff600000-0xff6fffff irq 57 on rk_dwc30 xhci0: 64 bytes context size, 32-bit DMA usbus0 on xhci0 ugen0.1: <Synopsys XHCI root HUB> at usbus0 uhub0: <Synopsys XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Instead of (from the cortext-a53 kernel on the cortext-a72 system): # dmesg -a | grep -i xhci | more xhci0: <Generic USB 3.0 controller> iomem 0x600000000-0x600000fff irq 0 on acpi0 xhci0: 32 bytes context size, 32-bit DMA usbus0 on xhci0 ugen0.1: <Generic XHCI root HUB> at usbus0 uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 xhci0: Resetting controller uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 So more than the cpu type and its properties provide distinctions. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[email protected]"
