> Also the DmaPort doesn't send it's packets marked uncachable which we > established as being a requirement for the interrupt messages. I don't > -want- to have to write a new port type, but what I need is > fundamentally not a DMA transfer. Making the DmaPort the solution for > things other than DMA is misleading, and not having it work for other > things means I need to find a different solution. But like I said, I > don't want to have to create a new port type, so I certainly wouldn't > mind finding a way to use something that already exists.
I see the issue you're having now. That makes sense not to pollute the DmaPort with this sort of thing. I think the answer is to create a new port type. You should be able to derive from SimpleTimingPort to significantly simplify your implementation. If not, we should clean up SimpleTimingPort so that it does work for this sort of thing. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
