TransferSizes: just because a device CAN do more does not mean it should (#15)
Capping TransferSizes at 128 fits nicely in 3 size bits.
This commit is contained in:
parent
ba7beb676d
commit
8b0d7ec91a
@ -38,8 +38,8 @@ class XilinxVC707MIGIsland(c : XilinxVC707MIGParams)(implicit p: Parameters) ext
|
||||
resources = device.reg,
|
||||
regionType = RegionType.UNCACHED,
|
||||
executable = true,
|
||||
supportsWrite = TransferSizes(1, 256*8),
|
||||
supportsRead = TransferSizes(1, 256*8))),
|
||||
supportsWrite = TransferSizes(1, 128),
|
||||
supportsRead = TransferSizes(1, 128))),
|
||||
beatBytes = 8)))
|
||||
|
||||
lazy val module = new LazyModuleImp(this) {
|
||||
|
@ -196,8 +196,8 @@ class VC707AXIToPCIeX1(implicit p:Parameters) extends LazyModule
|
||||
address = List(AddressSet(0x60000000L, 0x1fffffffL)),
|
||||
resources = Seq(Resource(device, "ranges")),
|
||||
executable = true,
|
||||
supportsWrite = TransferSizes(1, 256),
|
||||
supportsRead = TransferSizes(1, 256))),
|
||||
supportsWrite = TransferSizes(1, 128),
|
||||
supportsRead = TransferSizes(1, 128))),
|
||||
beatBytes = 8)))
|
||||
|
||||
val control = AXI4SlaveNode(Seq(AXI4SlavePortParameters(
|
||||
|
Loading…
Reference in New Issue
Block a user