From: Lucas Stach <l.stach@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>
Cc: "patchwork-lst@pengutronix.de" <patchwork-lst@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"manivannan.sadhasivam@linaro.org"
<manivannan.sadhasivam@linaro.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy
Date: Mon, 21 Jan 2019 18:31:37 +0100 [thread overview]
Message-ID: <1548091897.2465.10.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5BFZVUT8x8o57TkYfwfT9OF1a=g5pNo48bW1qwfYXUrRg@mail.gmail.com>
Am Montag, den 21.01.2019, 15:30 -0200 schrieb Fabio Estevam:
> Hi Daniel,
>
> > On Mon, Jan 21, 2019 at 3:25 PM Daniel Baluta <daniel.baluta@nxp.com> wrote:
>
> > Hi Fabio,
> >
> > Your patch helps.
>
> Thanks for testing. I will send it as a formal patch.
If you look closely that's exactly the patch 2/2 from this series.
Regards,
Lucas
>
> > Now the console works. Anyhow, it seems that now there
> > is a problem with the network card.
> >
> > [ 0.831454] mdio_bus 30be0000.ethernet-1:00: error -2 loading PHY driver module for ID 0x004dd074
> > [ 0.840796] fec 30be0000.ethernet: Dropping the link to regulator.0
> > [ 0.847212] fec: probe of 30be0000.ethernet failed with error -2
> >
> > Booting fails now because kernel isn't able to mount to nfs rootfs.
> >
> > [ 111.652134] VFS: Unable to mount root fs via NFS, trying floppy.
> > [ 111.658510] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
> >
> > This problem is similar with the one met on i.MX 8QXP.
>
> Does this patch help?
> https://www.spinics.net/lists/netdev/msg545573.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-21 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 11:04 [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Lucas Stach
2019-01-15 11:04 ` [PATCH 2/2] arm64: imx8mq: select GPCv2 irqchip driver Lucas Stach
2019-01-21 17:45 ` Fabio Estevam
2019-01-16 10:51 ` [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Shawn Guo
2019-01-22 6:29 ` Shawn Guo
[not found] ` <VI1PR0402MB3357FAB48888D99A809F41AEF99F0@VI1PR0402MB3357.eurprd04.prod.outlook.com>
[not found] ` <AM6PR04MB51581FBD4D21FEFDCAC2B27FE39F0@AM6PR04MB5158.eurprd04.prod.outlook.com>
[not found] ` <7f92c150219832eb9fb54e72021116ad78ae71c3.camel@nxp.com>
2019-01-21 17:30 ` Fabio Estevam
2019-01-21 17:31 ` Lucas Stach [this message]
2019-01-21 17:34 ` Fabio Estevam
2019-01-21 17:42 ` Lucas Stach
2019-01-21 17:59 ` Daniel Baluta
2019-01-21 18:03 ` Daniel Baluta
2019-01-22 3:41 ` Manivannan Sadhasivam
2019-01-22 7:22 ` Manivannan Sadhasivam
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=1548091897.2465.10.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=daniel.baluta@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=patchwork-lst@pengutronix.de \
--cc=shawnguo@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).