All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: swiotlb-xen question
Date: Wed, 26 Mar 2014 10:46:57 -0400	[thread overview]
Message-ID: <20140326144657.GC18387@phenom.dumpdata.com> (raw)
In-Reply-To: <CAN58jiv2rw1xeM5z-i8CrPfF16yx8nehA+dJSrCwRxUfEyetSQ@mail.gmail.com>

On Wed, Mar 26, 2014 at 12:35:12PM +0200, Oleksandr Dmytryshyn wrote:
> Hi to all.
> 
> Currently I'm using hypervisor on ARM Cortex A15 processor (DRA7xx
> Jacinto 6 processor). I'm using mainline xen 4.4 with some patches on
> top plus dom0 and domU linux kernel 3.8.
> 
> I've written a hack to make a camera working on my board in dom0
> (drivers for camera and display system are in dom0). An user-space
> application in dom0 is used to test camera (it reads camera captured
> data and sends it to the framebuffer). In the kernel code I've implemented
> .mmap callback function in the swiotlb-xen.c file (like xen_swiotlb_mmap())
> and copied to this new callback all content from the original function
> 'arm_dma_mmap()' from the kernel. This function creates userspace
> mapping for the DMA-coherent memory. With this hack camera is working
> (I can see captured video on display).

Why can't you use the v4l API? Won't that work?
> 
> For now I have little understanding how swiotlb-xen is working. Currently in the
> mainline linux kernel this callback is not implemented.
> 
> Here is my question.
> Does anyone know are there any plans to implement
> this callback for swiotlb-xen (in linux kernel) in the right way?
> 
> Oleksandr Dmytryshyn | Product Engineering and Development
> GlobalLogic
> P x3657  M +38.067.382.2525
> www.globallogic.com
> 
> http://www.globallogic.com/email_disclaimer.txt
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2014-03-26 14:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 10:35 swiotlb-xen question Oleksandr Dmytryshyn
2014-03-26 11:15 ` Ian Campbell
2014-03-26 14:46 ` Konrad Rzeszutek Wilk [this message]
2014-03-26 14:58   ` Oleksandr Dmytryshyn
2014-03-26 18:49     ` Stefano Stabellini
2014-03-26 19:44       ` Konrad Rzeszutek Wilk
2014-03-27 10:11       ` Oleksandr Dmytryshyn
2014-04-01 14:27         ` Oleksandr Dmytryshyn
2014-04-03 10:51           ` Stefano Stabellini
2014-04-03 11:43             ` Oleksandr Dmytryshyn
2014-04-03 12:52               ` Stefano Stabellini
2014-04-03 12:59                 ` Oleksandr Dmytryshyn
2014-04-04 11:20             ` Oleksandr Dmytryshyn
2014-04-04 11:26               ` Stefano Stabellini
2014-04-04 11:30                 ` Oleksandr Dmytryshyn
2014-04-04 16:26                   ` Konrad Rzeszutek Wilk
2014-04-07  6:34                     ` Oleksandr Dmytryshyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140326144657.GC18387@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.