Readon

Thanks.^^

> hi @Readon @Dolu1990 , the FIFO and RAM interface of BusIf have not complete yet. I haven't figured out whether instantiate FIFO to regbank.v Internal or direct output fifo...

> Maybe it could be one function for each, i mean : > > ```scala > val myDemux = new StreamDemux(..) > val selector = myDemux.io.createStreamSelector() > //alternatively : >...

> Maybe it could be one function for each, i mean : > > ```scala > val myDemux = new StreamDemux(..) > val selector = myDemux.io.createStreamSelector() > //alternatively : >...

> > How about add an function createReg or driveReg of Stream, which can be used as > > In some ways it already exists as : > > ```scala...

> This is the cases that StreamTransactionExtender fits. However, what is the difference between this unburster and existing Axi4AxUnburstified?

> I have code supporting multiple transactions without IDs. > > I'm not sure how to handle ID pending transactions. I'm thinking some number of FIFOs for ID slots which...

This changes the existing interface of Axi4ReadOnlyMonitor which breaks my existing code ....... Changes of API is really a pain.

It might be better to define a compatible interface both. Take onWriteByte as an example : ``` scala onWriteByte(address: BigInt, data: Byte) //legacy, it can be worked as id equals...

Also, a onLast method has been removed.