On Fri, 24 Sep 2021, 23:42 Stefano Stabellini,
wrote:
> On Fri, 24 Sep 2021, Rahul Singh wrote:
> > Hi Stefano,
> >
> > > On 23 Sep 2021, at 8:12 pm, Stefano Stabellini
> wrote:
> > >
> > > On Thu, 23 Sep 2021, Rahul Singh wrote:
> > +goto err_exit;
> > +}
> > >>>
> > >
Hi Stefano,
> On 25 Sep 2021, at 12:26 am, Stefano Stabellini
> wrote:
>
> On Fri, 24 Sep 2021, Stefano Stabellini wrote:
>> On Fri, 24 Sep 2021, Rahul Singh wrote:
>>> Hi Stefano,
>>>
On 23 Sep 2021, at 8:12 pm, Stefano Stabellini
wrote:
On Thu, 23 Sep 2021, Rahul Singh
On Fri, 24 Sep 2021, Stefano Stabellini wrote:
> On Fri, 24 Sep 2021, Rahul Singh wrote:
> > Hi Stefano,
> >
> > > On 23 Sep 2021, at 8:12 pm, Stefano Stabellini
> > > wrote:
> > >
> > > On Thu, 23 Sep 2021, Rahul Singh wrote:
> > +goto err_exit;
> > +}
> > >>>
> > >>
On Fri, 24 Sep 2021, Rahul Singh wrote:
> Hi Stefano,
>
> > On 23 Sep 2021, at 8:12 pm, Stefano Stabellini
> > wrote:
> >
> > On Thu, 23 Sep 2021, Rahul Singh wrote:
> +goto err_exit;
> +}
> >>>
> >>> This is unnecessary at the moment, right? Can we get rid of ops->in
Hi Stefano,
> On 23 Sep 2021, at 8:12 pm, Stefano Stabellini wrote:
>
> On Thu, 23 Sep 2021, Rahul Singh wrote:
+goto err_exit;
+}
>>>
>>> This is unnecessary at the moment, right? Can we get rid of ops->init ?
>>
>> No this is required for N1SDP board. Please check b
On Thu, 23 Sep 2021, Rahul Singh wrote:
> >> +goto err_exit;
> >> +}
> >
> > This is unnecessary at the moment, right? Can we get rid of ops->init ?
>
> No this is required for N1SDP board. Please check below patch.
> https://gitlab.com/rahsingh/xen-integration/-/commit/6379ba5764
Hi Stefano,
> On 23 Sep 2021, at 3:09 am, Stefano Stabellini wrote:
>
> On Wed, 22 Sep 2021, Rahul Singh wrote:
>> XEN during boot will read the PCI device tree node “reg” property
>> and will map the PCI config space to the XEN memory.
>>
>> As of now only "pci-host-ecam-generic" compatible bo
On Thu, 23 Sep 2021, Oleksandr Andrushchenko wrote:
> Hi, Stefano!
>
> [snip]
>
>
> >> +};
> >> +
> >> +/* Default ECAM ops */
> >> +extern const struct pci_ecam_ops pci_generic_ecam_ops;
> > If we use container_of and get rid of sysdata, I wonder if we get avoid
> > exporting pci_generic_ecam_o
Hi, Stefano!
[snip]
>> +};
>> +
>> +/* Default ECAM ops */
>> +extern const struct pci_ecam_ops pci_generic_ecam_ops;
> If we use container_of and get rid of sysdata, I wonder if we get avoid
> exporting pci_generic_ecam_ops.
>
>
>> +int pci_host_common_probe(struct dt_device_node *dev, const vo
On Wed, 22 Sep 2021, Rahul Singh wrote:
> XEN during boot will read the PCI device tree node “reg” property
> and will map the PCI config space to the XEN memory.
>
> As of now only "pci-host-ecam-generic" compatible board is supported.
>
> "linux,pci-domain" device tree property assigns a fixed
XEN during boot will read the PCI device tree node “reg” property
and will map the PCI config space to the XEN memory.
As of now only "pci-host-ecam-generic" compatible board is supported.
"linux,pci-domain" device tree property assigns a fixed PCI domain
number to a host bridge, otherwise an uns
11 matches
Mail list logo
