From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux@armlinux.org.uk,
bcousson@baylibre.com
Subject: Re: [PATCH] ARM: dts: omap4-sdp: Make ethernet working even if booted with latest u-boot
Date: Thu, 24 Jan 2019 08:17:29 -0800 [thread overview]
Message-ID: <20190124161729.GO5720@atomide.com> (raw)
In-Reply-To: <20181213135845.3965-1-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [181213 05:57]:
> The ethernet works in kernel only if we use some binary u-boot from the
> past which have support for KS8851.
>
> The u-boot sources are not available for this mysterious u-boot image
> people tends to hold on... Mainline u-bott does not have ethernet support
> for sdp4430 and if we use that the ethernet is not working.
>
> After some debugging I have managed to get the ethernet working with
> mainline u-boot while not breaking the networking with the case when we
> boot with the mysterious binary u-boot.
>
> Basically we were missing bunch of pinmux settings and the 'magic'
> gpio_138 handling in kernel.
Applying into omap-for-v5.1/dt thanks.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-24 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 13:58 [PATCH] ARM: dts: omap4-sdp: Make ethernet working even if booted with latest u-boot Peter Ujfalusi
2018-12-13 15:17 ` Tony Lindgren
2018-12-14 13:06 ` Peter Ujfalusi
2018-12-13 15:50 ` Russell King - ARM Linux
2018-12-14 13:08 ` Peter Ujfalusi
2018-12-14 13:16 ` Russell King - ARM Linux
2018-12-18 10:28 ` Peter Ujfalusi
2019-01-24 16:17 ` Tony Lindgren [this message]
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=20190124161729.GO5720@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=peter.ujfalusi@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).