Searched hist:10518 (Results 1 - 3 of 3) sorted by relevance

/gem5/src/mem/ruby/system/
H A DDMASequencer.hhdiff 11339:c45bfadcd51b Sun Feb 14 20:28:00 EST 2016 Michael LeBeane <Michael.Lebeane@amd.com> ruby: make DMASequencer inherit from RubyPort

This patch essentially rolls back 10518:30e3715c9405 to make RubyPort the
parent class of DMASequencer. It removes redundant code and restores some
features which were lost when directly inheriting from MemObject. For
example,
DMASequencer can now communicate to other devices using PIO, which is useful
for memmory-mapped communication between multiple DMADevices.
diff 10518:30e3715c9405 Thu Nov 06 01:55:00 EST 2014 Nilay Vaish <nilay@cs.wisc.edu> ruby: dma sequencer: remove RubyPort as parent class
As of now DMASequencer inherits from the RubyPort class. But the code in
RubyPort class is heavily tailored for the CPU Sequencer. There are parts of
the code that are not required at all for the DMA sequencer. Moreover, the
next patch uses the dma sequencer for carrying out memory accesses for all the
io devices. Hence, it is better to have a leaner dma sequencer.
H A DSequencer.pydiff 11339:c45bfadcd51b Sun Feb 14 20:28:00 EST 2016 Michael LeBeane <Michael.Lebeane@amd.com> ruby: make DMASequencer inherit from RubyPort

This patch essentially rolls back 10518:30e3715c9405 to make RubyPort the
parent class of DMASequencer. It removes redundant code and restores some
features which were lost when directly inheriting from MemObject. For
example,
DMASequencer can now communicate to other devices using PIO, which is useful
for memmory-mapped communication between multiple DMADevices.
diff 10518:30e3715c9405 Thu Nov 06 01:55:00 EST 2014 Nilay Vaish <nilay@cs.wisc.edu> ruby: dma sequencer: remove RubyPort as parent class
As of now DMASequencer inherits from the RubyPort class. But the code in
RubyPort class is heavily tailored for the CPU Sequencer. There are parts of
the code that are not required at all for the DMA sequencer. Moreover, the
next patch uses the dma sequencer for carrying out memory accesses for all the
io devices. Hence, it is better to have a leaner dma sequencer.
H A DDMASequencer.ccdiff 11339:c45bfadcd51b Sun Feb 14 20:28:00 EST 2016 Michael LeBeane <Michael.Lebeane@amd.com> ruby: make DMASequencer inherit from RubyPort

This patch essentially rolls back 10518:30e3715c9405 to make RubyPort the
parent class of DMASequencer. It removes redundant code and restores some
features which were lost when directly inheriting from MemObject. For
example,
DMASequencer can now communicate to other devices using PIO, which is useful
for memmory-mapped communication between multiple DMADevices.
diff 10518:30e3715c9405 Thu Nov 06 01:55:00 EST 2014 Nilay Vaish <nilay@cs.wisc.edu> ruby: dma sequencer: remove RubyPort as parent class
As of now DMASequencer inherits from the RubyPort class. But the code in
RubyPort class is heavily tailored for the CPU Sequencer. There are parts of
the code that are not required at all for the DMA sequencer. Moreover, the
next patch uses the dma sequencer for carrying out memory accesses for all the
io devices. Hence, it is better to have a leaner dma sequencer.

Completed in 31 milliseconds