On Thu, 2014-12-11 at 10:02 -0800, manish jaggi wrote:
> This is the complete smmu.c file which you can refer for PCI
> passthrough (http://pastebin.com/QDX8fpDu)
I'm afraid that as Julien says this is basically no help.
> Just FYI this is not a patch, we are still testing on our board and
> can
Hello Manish,
On 11/12/14 18:02, manish jaggi wrote:
> On 11 December 2014 at 02:30, Stefano Stabellini
> wrote:
>> On Wed, 10 Dec 2014, manish jaggi wrote:
>>> Based on my experience with PCI passthrough code merging, below are
>>> some comments:
>>> Both require a change in code
>>>
>>> a) The
On 11 December 2014 at 02:30, Stefano Stabellini
wrote:
> On Wed, 10 Dec 2014, manish jaggi wrote:
>> Based on my experience with PCI passthrough code merging, below are
>> some comments:
>> Both require a change in code
>>
>> a) The current code which is non-pci passthrough requires a devices'
>>
On Wed, 10 Dec 2014, manish jaggi wrote:
> Based on my experience with PCI passthrough code merging, below are
> some comments:
> Both require a change in code
>
> a) The current code which is non-pci passthrough requires a devices'
> device tree node to be associated with smmu node, if that devic
Hello,
On 11/12/2014 02:39, manish jaggi wrote:
I need your views how PCI passthrough / Non PCI passthrough code can
coexist with the two points mentioned above ?
It' s hard to answer to your question if you don't specify on which
version of the platform device passthrough you are based
Based on my experience with PCI passthrough code merging, below are
some comments:
Both require a change in code
a) The current code which is non-pci passthrough requires a devices'
device tree node to be associated with smmu node, if that device has
to be assigned to domU.
In our system there is
