From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Lynch Subject: Re: ethernet support for OMAP5 UEVM Date: Mon, 27 Jan 2014 15:09:17 -0600 Message-ID: <52E6CAFD.7080803@codesourcery.com> References: <52E6BE32.4060101@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from relay1.mentorg.com ([192.94.38.131]:38588 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754250AbaA0VJV (ORCPT ); Mon, 27 Jan 2014 16:09:21 -0500 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1W7tQm-0000Y6-1X from Nathan_Lynch@mentor.com for linux-omap@vger.kernel.org; Mon, 27 Jan 2014 13:09:20 -0800 In-Reply-To: <52E6BE32.4060101@codesourcery.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: linux-omap@vger.kernel.org On 01/27/2014 02:14 PM, Nathan Lynch wrote: > Hi, > > I am able to boot an OMAP5 uevm board with linux-next 20140124. > However, the smsc ethernet device does not show up without these patches > on top: > > ARM: dts: OMAP5: Add 60MHz clock reference to USB Host module > https://patchwork.kernel.org/patch/3001841/ > > ARM: dts: omap5-uevm: Provide USB PHY clock > https://patchwork.kernel.org/patch/3001881/ > > Just wondering if these were overlooked or if there is something else > holding them up. Ah, now I see they haven't fallen through the cracks and were in fact refreshed/posted last week: https://lwn.net/Articles/581319/ Never mind!