diff options
| author | Kyle Evans <kevans@FreeBSD.org> | 2026-09-09 09:00:28 +0000 |
|---|---|---|
| committer | Kyle Evans <kevans@FreeBSD.org> | 2026-09-09 09:00:28 +0000 |
| commit | 6af3031c951614f2a42dfd67ce2c3a48ee8314ae (patch) | |
| tree | c11bf6942d118ff48644bdea633a59fe72876b4a /packages/Python/lldbsuite/test/lang/objc | |
| parent | 1de79e73a8be1938911d9640d0bde0432d220dd6 (diff) | |
The original implementation assumed that the start/reply doorbells
lived within the device _CRS space, but that isn't always the case. On
my AMD Ryzen 7640U-based frame.work laptop, device memory runs from
0xc0500000-0xc0500fff while the doorbells are up around 0xc0508000.
Stop sanity checking the addresses and just map them in to work reliably
whether they're within the device range or not.
pluton_wait_reply is cribbed from tpm_wait_for_u32, but rewritten
slightly to read in just one place and to read one last time before
giving up at the end of the timeout, just in case.
Reviewed by: kbowling
Differential Revision: https://reviews.freebsd.org/D59327
Diffstat (limited to 'packages/Python/lldbsuite/test/lang/objc')
0 files changed, 0 insertions, 0 deletions