On 13/12/2018 17.50, Russell King - ARM Linux wrote: > On Thu, Dec 13, 2018 at 03:58:45PM +0200, Peter Ujfalusi wrote: >> 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. >> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@xxxxxx> > > Hi Peter, > > Digging up where my u-boot came from, I found: > > https://plus.google.com/103895730806848715870/posts/cCq2CxDogW9 > > Unfortunately, gitorious no longer exists, but I do still have a clone > of that tree locally, containing: > > 9f384308319e OMAP4SDP: Add Micrel KS8851 net chip support > ae631b095a87 NET: Add driver for Micrel KS8851 > 78e43f2a8987 ARMV7: OMAP: Add spi driver for OMAP3/OMAP4 > e576c6a9cbc9 omap4_common: config: remove I2C for SPL mode > 19d5934c4b3b ARM: OMAP4: Move TEXT_BASE down to non-HS limit > > plus some of my own modifications to fix the problems stated in that > post. I certainly have the version of u-boot which can do only one tftp load (or dhcp request). - Péter Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
