On Wednesday 04 November 2009 02:37:38 Jonathan Haws wrote:
All,
I have what may be an unconventional question:
Our application consists of data being captured by an FPGA, processed, and
transferred to SDRAM. I simply give the FPGA an address of where I want
it stored in SDRAM and it
On 11/04/2009 11:50 AM, Jonathan Haws wrote:
One more question about this approach: does the mmap() call prevent
the kernel from using this memory for other purposes? Will the
kernel be able to move this memory elsewhere? I guess what I am
asking is if this memory is locked for all other
Jonathan Haws wrote:
All,
I have what may be an unconventional question:
Our application consists of data being captured by an FPGA,
processed, and transferred to SDRAM. I simply give the FPGA an
address of where I want it stored in SDRAM and it simply DMAs the
data over and
1. I open /dev/mem and get a file descriptor
2. I use mmap to reserve some physical addresses for my buffers in
user space.
3. I give that address to the FPGA for DMA use.
4. When I get the FPGA interrupt, I invalidate the data cache and
write the data to disk
Does that sound like it
to User-Space
Jonathan Haws wrote:
All,
I have what may be an unconventional question:
Our application consists of data being captured by an FPGA,
processed, and transferred to SDRAM. I simply give the FPGA an
address of where I want it stored in SDRAM and it simply DMAs the
data over
All,
I have what may be an unconventional question:
Our application consists of data being captured by an FPGA, processed, and
transferred to SDRAM. I simply give the FPGA an address of where I want it
stored in SDRAM and it simply DMAs the data over and interrupts me when
finished. I then
Jonathan Haws wrote:
All,
I have what may be an unconventional question:
Our application consists of data being captured by an FPGA, processed, and
transferred to SDRAM. I simply give the FPGA an address of where I want it
stored in SDRAM and it simply DMAs the data over and interrupts me
