Let's code a Linux Driver - 32: The mmap Callback

แชร์
ฝัง
  • เผยแพร่เมื่อ 29 พ.ย. 2024

ความคิดเห็น • 8

  • @alinezhadi
    @alinezhadi 6 หลายเดือนก่อน

    Thank you so much for this great tutorial

  • @fghoussen
    @fghoussen 2 หลายเดือนก่อน

    Could you detail why `pgoff = phys_addr >> PAGE_SHIFT`?
    Is that because each page has an ID which is stored in the first PAGE_SIZE bits of each page (and that the allocated data "begins" only after - this is how I understand it)? Or a similar reason?
    What if you do `pgoff = phys_addr` instead of `pgoff = phys_addr >> PAGE_SHIFT`?

  • @tranminhquan1752
    @tranminhquan1752 10 หลายเดือนก่อน

    HI Johannes,
    At 4:34, it's called a page table entry, right? 20 bits for the "page frame nr" that specific position for 12 bits "data" is locating at the physical ram, correct?

  • @vishaalvishaal2118
    @vishaalvishaal2118 6 หลายเดือนก่อน

    hi at 6:11 what will be the problem ? if physically not contiguous memory ptr shared with user space.

  • @randypeeters3931
    @randypeeters3931 ปีที่แล้ว

    Can you give me some advice? I made a custom peripheral using a FPGA which is a soc. The peripheral is memory mapped. The peripheral also uses a BRAM peripheral which is close to the custom peripheral. I have to write a driver so i can easily control it. I was thinking to use this mmap method(the method in your video) to write to the BRAM and to use ioctl to set some status or control bits. Do i understand the application of this video well?

  • @niccolazo
    @niccolazo ปีที่แล้ว

    nice 8:00