On Wed, Nov 06, 2019 at 02:09:26PM +, Robin Murphy wrote:
> Hmm, that bus mask looks pretty wacky - are you able to figure out where
> that's coming from?
arch/powerpc/sysdev/fsl_pci.c:pci_dma_dev_setup_swiotlb().
___
iommu mailing list
iommu@lists.
Interesting. Give me some time to come up with a real fix, as drivers
really should not mess with GFP flags for these allocations, and even
if they did swiotlb is supposed to take care of any resulting problems.
___
iommu mailing list
iommu@lists.linux-f
Hello Christoph,
I have found the issue. :-)
GFP_DMA32 was renamed to GFP_DMA in the PowerPC updates 4.21-1 in
December last year.
Some PCI devices still use GFP_DMA32 (grep -r GFP_DMA32 *). I renamed
GFP_DMA32 to GFP_DMA in the file
"drivers/media/v4l2-core/videobuf-dma-sg.c". After compil
On 12 November 2019 at 3:41 pm, Christoph Hellwig wrote:
On Mon, Nov 11, 2019 at 01:22:55PM +0100, Christian Zigotzky wrote:
Now, I can definitely say that this patch does not solve the issue.
Do you have another patch for testing or shall I bisect?
I'm still interested in the .config and dmes
On Mon, Nov 11, 2019 at 01:22:55PM +0100, Christian Zigotzky wrote:
> Now, I can definitely say that this patch does not solve the issue.
>
> Do you have another patch for testing or shall I bisect?
I'm still interested in the .config and dmesg. Especially if the
board is using arch/powerpc/sysde
On 11 November 2019 at 09:16 am, Christian Zigotzky wrote:
On 11 November 2019 at 09:12 am, Christian Zigotzky wrote:
On 10 November 2019 at 08:27 am, Christian Zigotzky wrote:
On 07 November 2019 at 10:53 am, Christian Zigotzky wrote:
On 05 November 2019 at 05:28 pm, Christoph Hellwig wrote:
On 11 November 2019 at 09:12 am, Christian Zigotzky wrote:
On 10 November 2019 at 08:27 am, Christian Zigotzky wrote:
On 07 November 2019 at 10:53 am, Christian Zigotzky wrote:
On 05 November 2019 at 05:28 pm, Christoph Hellwig wrote:
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzk
On 10 November 2019 at 08:27 am, Christian Zigotzky wrote:
On 07 November 2019 at 10:53 am, Christian Zigotzky wrote:
On 05 November 2019 at 05:28 pm, Christoph Hellwig wrote:
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzky wrote:
Hi All,
We still have DMA problems with some PCI
On 07 November 2019 at 10:53 am, Christian Zigotzky wrote:
On 05 November 2019 at 5:28 pm, Christoph Hellwig wrote:
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzky wrote:
Hi All,
We still have DMA problems with some PCI devices. Since the PowerPC
updates
4.21-1 [1] we need to dec
On 05 November 2019 at 5:28 pm, Christoph Hellwig wrote:
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzky wrote:
Hi All,
We still have DMA problems with some PCI devices. Since the PowerPC updates
4.21-1 [1] we need to decrease the RAM to 3500MB (mem=3500M) if we want to
work with o
On 05/11/2019 16:28, Christoph Hellwig wrote:
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzky wrote:
Hi All,
We still have DMA problems with some PCI devices. Since the PowerPC updates
4.21-1 [1] we need to decrease the RAM to 3500MB (mem=3500M) if we want to
work with our PCI devi
On Tue, Nov 05, 2019 at 08:56:27AM +0100, Christian Zigotzky wrote:
> Hi All,
>
> We still have DMA problems with some PCI devices. Since the PowerPC updates
> 4.21-1 [1] we need to decrease the RAM to 3500MB (mem=3500M) if we want to
> work with our PCI devices. The FSL P5020 and P5040 have thes
Hi All,
We still have DMA problems with some PCI devices. Since the PowerPC
updates 4.21-1 [1] we need to decrease the RAM to 3500MB (mem=3500M) if
we want to work with our PCI devices. The FSL P5020 and P5040 have these
problems currently.
Error message:
[ 25.654852] bttv 1000:04:05.0: o
13 matches
Mail list logo
