Hi,
On 10/9/19 2:25 PM, Jiri Kosina wrote:
> On Fri, 27 Sep 2019, Shah, Nehal-bakulchandra wrote:
>
> Do you have BAR memory allocation failures in dmesg with IOMMU on?
>>>
>>> No. The device is *not* treated as PCI device and I still think that
>>> this is the source of the evil.
>>>
> A
On Fri, 27 Sep 2019, Shah, Nehal-bakulchandra wrote:
> >>> Do you have BAR memory allocation failures in dmesg with IOMMU on?
> >
> > No. The device is *not* treated as PCI device and I still think that
> > this is the source of the evil.
> >
> >>> Actually, sharing both working and non-working
Hi Kurf
On 9/27/2019 3:17 PM, Kurt Garloff wrote:
> Hi Jörg,
>
> On 25/09/2019 17:42, Joerg Roedel wrote:
>> On Wed, Sep 25, 2019 at 05:27:32PM +0200, Jiri
>> Kosina wrote:
>>> On Sat, 21 Sep 2019, Kurt Garloff wrote:
[12916.740274] mmc0: sdhci:
=
On Wed, Sep 25, 2019 at 05:27:32PM +0200, Jiri Kosina wrote:
> On Sat, 21 Sep 2019, Kurt Garloff wrote:
> > [12916.740274] mmc0: sdhci:
> > [12916.740337] mmc0: error -5 whilst initialising MMC card
>
> Do you have BAR memory allocation failures in dmes
On Sat, 21 Sep 2019, Kurt Garloff wrote:
> Hi,
>
>
> enabling the IOMMU on my Ryzen v1605b (UDOO Bolt v8) does result in a
> non-working EMMC driver.
> Without enabling IOMMU, it works like a charm.
> From my POV this needs fixing, and I consider this a bug.
[ CCing Joerg ]
> I looked into
Hi,
enabling the IOMMU on my Ryzen v1605b (UDOO Bolt v8) does result in a
non-working EMMC driver.
Without enabling IOMMU, it works like a charm.
From my POV this needs fixing, and I consider this a bug.
I looked into sdhci to see whether the right dma_map_sg() calls are missing,
but th
6 matches
Mail list logo
