ipbus_peephole_ram, is it still a thing?

Question

ipbus_peephole_ram, is it still a thing?

Closed this issue 5 years ago · 6 comments

The peephole ram slave seems to have been superseded by the ported dual-port ram slave.
Is that correct? Can the peephole ram be deleted in such case?

Alessandro

Answer 1 · 2018-12-06T12:28:21.000Z

Yes it can. Note however that this block is used in the canonical ipbus_example.vhd however, so that will need to be updated.

Answer 2 · 2018-12-06T12:40:40.000Z

Good point, thanks for the reminder.

Answer 3 · 2018-12-06T21:31:36.000Z

After comparing once more ipbus_peephole_ram and ipbus_ported_dram, I remembered the difference. The peephole is completely contained in the ipbus clock domain. So was it created for testing purposes only? Or does it have any other use?

Answer 4 · 2018-12-06T21:42:24.000Z

Yes, testing purposes only. You can of course get the same effect by using one of the other RAM blocks and just not connecting the other port to anything useful. Prof David M Newbold | Director Particle Physics Department STFC Rutherford Appleton Laboratory, Harwell Campus, Didcot OX11 0QX United Kingdom Tel | Office: +44 (0) 1235 446760 Tel | Mobile: +44 (0) 7542 226292 Email | dave.newbold@stfc.ac.uk<mailto:dave.newbold@stfc.ac.uk> http://www.stfc.ukri.org<http://www.stfc.ukri.org/> [STFC-UKRI1] www.ukri.org<http://www.ukri.org/> STFC is a member of UK Research and Innovation From: Alessandro Thea <notifications@github.com> Reply-To: ipbus/ipbus-firmware <reply@reply.github.com> Date: Thursday, 6 December 2018 at 21:32 To: ipbus/ipbus-firmware <ipbus-firmware@noreply.github.com> Cc: Dave Newbold <Dave.Newbold@cern.ch>, Assign <assign@noreply.github.com> Subject: Re: [ipbus/ipbus-firmware] ipbus_peephole_ram, is it still a thing? (#84) After comparing once more ipbus_peephole_ram and ipbus_ported_dram, I remembered the difference. The peephole is completely contained in the ipbus clock domain. So was it created for testing purposes only? Or does it have any other use? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#84 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AUMaSAKxtbqTZFDKRqRVxPZbBkjkq21Iks5u2Yy4gaJpZM4ZGaCP>.

Answer 5 · 2018-12-12T15:47:58.000Z

Undestood. The same reasoning applies to ipbus_ram I guess.

Answer 6 · 2018-12-12T16:12:56.000Z

Looks that way. Prof David M Newbold | Director Particle Physics Department STFC Rutherford Appleton Laboratory, Harwell Campus, Didcot OX11 0QX United Kingdom Tel | Office: +44 (0) 1235 446760 Tel | Mobile: +44 (0) 7542 226292 Email | dave.newbold@stfc.ac.uk<mailto:dave.newbold@stfc.ac.uk> http://www.stfc.ukri.org<http://www.stfc.ukri.org/> [STFC-UKRI1] www.ukri.org<http://www.ukri.org/> STFC is a member of UK Research and Innovation From: Alessandro Thea <notifications@github.com> Reply-To: ipbus/ipbus-firmware <reply@reply.github.com> Date: Wednesday, 12 December 2018 at 15:48 To: ipbus/ipbus-firmware <ipbus-firmware@noreply.github.com> Cc: Dave Newbold <Dave.Newbold@cern.ch>, Assign <assign@noreply.github.com> Subject: Re: [ipbus/ipbus-firmware] ipbus_peephole_ram, is it still a thing? (#84) Undestood. The same reasoning applies to ipbus_ram I guess. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#84 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AUMaSIELulMNh3gPsGibhhfRhBs6dGYMks5u4SUvgaJpZM4ZGaCP>.