All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: Darren Stevens <darren@stevens-zone.net>,
	madalin.bacur@nxp.com, netdev@vger.kernel.org,
	mad skateman <madskateman@gmail.com>,
	oss@buserror.net, linuxppc-dev@lists.ozlabs.org,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	"contact@a-eon.com" <contact@a-eon.com>
Subject: Re: [RFC PATCH dpss_eth] Don't initialise ports with no PHY
Date: Wed, 29 Apr 2020 17:22:24 +0200	[thread overview]
Message-ID: <20200429152224.GA66424@lunn.ch> (raw)
In-Reply-To: <77E4A243-F90A-45A9-B8D3-0F7785C158C7@xenosoft.de>

On Wed, Apr 29, 2020 at 03:55:28PM +0200, Christian Zigotzky wrote:
> Hi Andrew,
> 
> You can find some dtb and source files in our kernel package.
> 
> Download: http://www.xenosoft.de/linux-image-5.7-rc3-X1000_X5000.tar.gz

I have the tarball. Are we talking about
linux-image-5.7-rc3-X1000_X5000/X5000_and_QEMU_e5500/dtbs/X5000_20/cyrus.eth.dtb

I don't see any status = "disabled"; in the blob. So i would expect
the driver to probe.

    Andrew



WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: madalin.bacur@nxp.com, "R.T.Dickinson" <rtd2@xtra.co.nz>,
	netdev@vger.kernel.org, oss@buserror.net,
	Darren Stevens <darren@stevens-zone.net>,
	"contact@a-eon.com" <contact@a-eon.com>,
	mad skateman <madskateman@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH dpss_eth] Don't initialise ports with no PHY
Date: Wed, 29 Apr 2020 17:22:24 +0200	[thread overview]
Message-ID: <20200429152224.GA66424@lunn.ch> (raw)
In-Reply-To: <77E4A243-F90A-45A9-B8D3-0F7785C158C7@xenosoft.de>

On Wed, Apr 29, 2020 at 03:55:28PM +0200, Christian Zigotzky wrote:
> Hi Andrew,
> 
> You can find some dtb and source files in our kernel package.
> 
> Download: http://www.xenosoft.de/linux-image-5.7-rc3-X1000_X5000.tar.gz

I have the tarball. Are we talking about
linux-image-5.7-rc3-X1000_X5000/X5000_and_QEMU_e5500/dtbs/X5000_20/cyrus.eth.dtb

I don't see any status = "disabled"; in the blob. So i would expect
the driver to probe.

    Andrew



  reply	other threads:[~2020-04-29 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 22:29 [RFC PATCH dpss_eth] Don't initialise ports with no PHY Darren Stevens
2020-04-24 22:29 ` Darren Stevens
2020-04-24 22:50 ` Florian Fainelli
2020-04-24 22:50   ` Florian Fainelli
2020-04-25  0:10 ` Andrew Lunn
2020-04-25  0:10   ` Andrew Lunn
2020-04-30 20:45   ` Darren Stevens
2020-04-29  8:26 ` [RFC PATCH dpss_eth] " Christian Zigotzky
2020-04-29  8:26   ` Christian Zigotzky
2020-04-29 13:12   ` Andrew Lunn
2020-04-29 13:12     ` Andrew Lunn
2020-04-29 13:55     ` Christian Zigotzky
2020-04-29 15:22       ` Andrew Lunn [this message]
2020-04-29 15:22         ` Andrew Lunn
2020-04-29 15:42         ` Christian Zigotzky
2020-04-29 15:42           ` Christian Zigotzky
2020-04-30 21:32           ` Darren Stevens
2020-05-01  5:35             ` Christian Zigotzky
2020-05-01  5:35               ` 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=20200429152224.GA66424@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=chzigotzky@xenosoft.de \
    --cc=contact@a-eon.com \
    --cc=darren@stevens-zone.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bacur@nxp.com \
    --cc=madskateman@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss@buserror.net \
    --cc=rtd2@xtra.co.nz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.