From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org, "Tero Kristo" <t-kristo@ti.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add am335x mcasp with l3 data port ranges
Date: Mon, 10 Dec 2018 06:50:54 -0800 [thread overview]
Message-ID: <20181210145054.GA6707@atomide.com> (raw)
In-Reply-To: <45fc55d2-8c8c-e831-cdaa-970d382a432f@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [181210 13:45]:
> On 10/12/2018 11.53, Peter Ujfalusi wrote:
> > On 10/12/2018 9.05, Peter Ujfalusi wrote:
> > when looking for the non booting of am335x-evm-sk (nothing printed on
> > serial after stating kernel).
> >
> > However there is another issue: the kernel boots, but ethernet is not
> > working in the kernel. That is pointing to:
> > Author: Tero Kristo <t-kristo@ti.com>
> > 69fd70c7ff31d3f00833c472c3994a02bb0ab287
> > ARM: dts: am33xx: convert to use new clkctrl layout
> >
> > any idea what might causes these?
>
> Things definitely go wrong at 69fd70c7ff31d3f00833c472c3994a02bb0ab287:
>
> git checkout -b blah 69fd70c7ff31d3f00833c472c3994a02bb0ab287
> # can not mount the rootfs via nfs
>
> git revert 69fd70c7ff31d3f00833c472c3994a02bb0ab287
> # boots up via nfs rootfs.
>
> At commit 69fd70c7ff31d3f00833c472c3994a02bb0ab287 the bbb is not
> booting via nfs rootfs either.
>
> Can not find where the ethernet started to work after these on bbb, but
> it does work on top of next-20181207.
Tero do you have any ideas on this one? Maybe a missing optional clock
somewhere?
Regards,
Tony
next prev parent reply other threads:[~2018-12-10 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 23:03 [PATCH] ARM: dts: Add am335x mcasp with l3 data port ranges Tony Lindgren
2018-12-10 7:05 ` Peter Ujfalusi
2018-12-10 9:53 ` Peter Ujfalusi
2018-12-10 13:46 ` Peter Ujfalusi
2018-12-10 14:50 ` Tony Lindgren [this message]
2018-12-10 15:12 ` Tero Kristo
2018-12-10 15:28 ` Peter Ujfalusi
2018-12-10 14:48 ` Tony Lindgren
2018-12-10 15:44 ` Tony Lindgren
2018-12-10 16:14 ` Peter Ujfalusi
2018-12-10 16:21 ` Tony Lindgren
2018-12-10 16:38 ` Tony Lindgren
2018-12-10 17:01 ` Peter Ujfalusi
2018-12-10 17:23 ` Tony Lindgren
2018-12-11 7:11 ` Peter Ujfalusi
2018-12-11 8:20 ` Peter Ujfalusi
2018-12-11 10:55 ` Peter Ujfalusi
2018-12-11 14:18 ` Tony Lindgren
2018-12-10 22:20 ` Tony Lindgren
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=20181210145054.GA6707@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
/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).