From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-12.arcor-online.net (mail-in-12.arcor-online.net [151.189.21.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 34A8EDDE48 for ; Tue, 17 Apr 2007 09:19:38 +1000 (EST) In-Reply-To: <20070416115729.292c10b1.kim.phillips@freescale.com> References: <20070413012542.343eb848.kim.phillips@freescale.com> <95a9680c565aa196a4ef78964ef9dee1@kernel.crashing.org> <20070416102533.0f87396f.kim.phillips@freescale.com> <20070416115729.292c10b1.kim.phillips@freescale.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <53810df560c7af272cd1c71c9d5fa1ab@kernel.crashing.org> From: Segher Boessenkool Subject: Re: [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties Date: Tue, 17 Apr 2007 01:18:56 +0200 To: Kim Phillips Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > I don't need to know what type the PHY is, e.g. whether it's m88e11x1 > compatible or not, the phylib handles that. You need to tell the phylib what kind of bus the PHY uses. You can put "rgmii" or whatever in the "compatible" property as well. > If I were to put the properties in the PHY node, I wouldn't be able to > describe a 1000Mbit/s capable UCC connected to a 100Mbit/s capable PHY, > or vice versa. Of course you can. The "compatible" in the enet node implies it can do 1000Mbps; the "compatible" in the PHY node implies it does 100Mbps. Segher