linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Madalin-cristian Bucur <madalin.bucur@nxp.com>,
	Darren Stevens <darren@stevens-zone.net>,
	Jamie Krueger <jamie@bitbybitsoftwaregroup.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: DPAA Ethernet problems with mainstream Linux kernels
Date: Tue, 16 Jan 2018 21:42:47 +0100	[thread overview]
Message-ID: <2ca2be11-7e64-3055-0d06-7090d5dcc096@xenosoft.de> (raw)
In-Reply-To: <DB3PR0402MB38496B4FB62904321A97186AECEA0@DB3PR0402MB3849.eurprd04.prod.outlook.com>

Hi All,

I compiled the RC8 of kernel 4.15 for the X5000 without PAMU support today.

Download: http://www.xenosoft.de/uImage_without_pamu.tar.gz

Please test it on your AmigaOne X5000.

Thanks,
Christian


On 16 January 2018 at 6:33PM, Madalin-cristian Bucur wrote:
>> The PAMU related errors may be relevant to the issue, if you have incorrect
>> settings you may have no traffic passing through. The PAMU configuration
>> should be made by the bootloader. Can you try to disable CONFIG_FSL_PAMU?
>>
>> Madalin
>>
>>

  reply	other threads:[~2018-01-16 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 15:56 DPAA Ethernet problems with mainstream Linux kernels Jamie Krueger
2018-01-12 14:22 ` Madalin-cristian Bucur
2018-01-12 16:35   ` Jamie Krueger
2018-01-15 10:44     ` Madalin-cristian Bucur
2018-01-15 22:39       ` Darren Stevens
2018-01-16 17:33         ` Madalin-cristian Bucur
2018-01-16 20:42           ` Christian Zigotzky [this message]
2018-01-18  1:59           ` Jamie Krueger
2018-01-18  7:52             ` Christian Zigotzky
2018-02-26 23:11       ` PASEMI: PCI_SCAN_ALL_PCIE_DEVS Christian Zigotzky

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=2ca2be11-7e64-3055-0d06-7090d5dcc096@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=jamie@bitbybitsoftwaregroup.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@nxp.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).