From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BB71935C682 for ; Tue, 21 Jul 2026 23:12:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784675577; cv=none; b=CDPbpqaGq6NxfHL5u8mBTc6BxM7/GauqXpaSaYd1ivDrvjsCKvCRlhAYlz+hiEQm6w9o4ZIuH3AuN7M+8X4iNnxOgXL0TCdgNZS6Z6GAehH2W5K7lfDfKP1WpJDgCy1oP4uVUM2Qb3BTNIvgKIX/GOUwZ+h58Ed9gwBiDNQDtww= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784675577; c=relaxed/simple; bh=Qsy9pxG0ZiPzVMrZREnQD/AsgYibId+ttr/qYC+JKKQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=NgRLrUjTcQucW7W4aTR1pj/swR1lkEoleNqwcsRqV+hyekeCSH1mK5YMg/PpT5EBK2Vc7k92xIhxEnjudjZPW4V0CQuyA7UNk4Bk0/G6d/1HBmPfEeJI131Od/fIdhiCe409ie6DkFJzAUI0ROJ+EJSEQUm8pEASHoUlutXRTFE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=g/MJFhTf; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="g/MJFhTf" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=4DcE3KqVDNfHAhhkWxaeBg4TIRClxbD2Bz/bkHDor9c=; b=g/MJFhTf9l2bHpAcg4AKsoLjgN TjvfKs4UiqY6cP0Os9dj+rNvHZEUULytndd9zuvYunmeItSDdUfwBZ+U8s5MHMG2gt7WK7YO4J6VW IVN4yk3qzTn3Ut0j1jZaDs3Fljf4A1G7OKSIYIjnfCXYeJiBIN1TwQZy4wmVzmL9CNsE=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1wmJdi-00DWcD-Ep; Wed, 22 Jul 2026 01:12:42 +0200 Date: Wed, 22 Jul 2026 01:12:42 +0200 From: Andrew Lunn To: "Srinivasan, Vijay" Cc: "D H, Siddaraju" , Maxime Chevallier , David Laight , Michal Kubecek , "netdev@vger.kernel.org" , "Chintalapalle, Balaji" , "Das, Shubham" , "Samudrala, Sridhar" , "Keller, Jacob E" , "Nguyen, Anthony L" , "singhai.anjali55@gmail.com" , "Brandeburg, Jesse" Subject: Re: Ethtool is missing C2C link modes Message-ID: References: <20260711073128.7f94e0ac@pumpkin> <20dde8ba-5429-45e2-8071-ce83f1c2d6c0@lunn.ch> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > As for your comment/question about FW vs linux controiling the HW, the intent here > is to use linux to tell FW where to go based on user input. > How the link is eventually achieved is all in FW. I don't see how that works. ethtool has no APIs around phy_interface_t. All ethtool offers is link modes. How do you see this working? Andrew