summaryrefslogtreecommitdiffstats
path: root/sys/arm/freescale
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2016-04-10 22:43:36 +0000
committermarius <marius@FreeBSD.org>2016-04-10 22:43:36 +0000
commitbadebc350a608060082d5f1b86f3038714a7d433 (patch)
tree4c9ce4cb14e163447cabeb9576007078c0adc5d4 /sys/arm/freescale
parent858f336801b9b036dd48c5e5d8f38c3441aa5686 (diff)
downloadFreeBSD-src-badebc350a608060082d5f1b86f3038714a7d433.zip
FreeBSD-src-badebc350a608060082d5f1b86f3038714a7d433.tar.gz
Since r296250 it is no longer possible for devices to use bus space
addresses exceeding 32 bit, so bump BUS_SPACE_MAXADDR to 64 bit. The whole situation is sub par, though; prior to r296250 and despite what their names imply, BUS_SPACE_MAX* were primarily, even almost exclusively used for bus_dma(9). Now these macros also have a vital role for bus_space(9). However, it does not necessarily hold that both bus DMA and space addresses universally have the same limits per platform. As for sparc64, 64 bit clearly is beyond what can be addressed via the various IOMMUs. With this change in place, we now rely on the parent bus DMA tags of the host-to-foo drivers causing the child tags to be capped as necessary. PR: 207998
Diffstat (limited to 'sys/arm/freescale')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud