From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3921AC0650E for ; Mon, 1 Jul 2019 13:29:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 11CA520665 for ; Mon, 1 Jul 2019 13:29:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="5H3GX93u" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728954AbfGAN30 (ORCPT ); Mon, 1 Jul 2019 09:29:26 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:45620 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727415AbfGAN3Z (ORCPT ); Mon, 1 Jul 2019 09:29:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=/wH7gsNCFutjcBkNMwkLgvVyn4BWXgcGFHl/aAlbf7A=; b=5H3GX93u95qcsN7JLwzaoO9hqB QO6yrOAAU3gkVrw5rlwjymr7mFEHAeDi/BgGDQIVZw4ifeHjU8eVerL3m8KR1R0u1xvtv4WGLLY4q q5PAUZJd9ErfqUzM9poNdilibKK7H9cDdqGWHJLEPS2CpaANTFa0VLrXCGTFbPYHGcYs=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1hhwMw-0006yh-BC; Mon, 01 Jul 2019 15:29:18 +0200 Date: Mon, 1 Jul 2019 15:29:18 +0200 From: Andrew Lunn To: Corentin Labbe Cc: jacmet@sunsite.dk, davem@davemloft.net, netdev@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [BUG] net: dm9600: false link status Message-ID: <20190701132918.GA25795@lunn.ch> References: <20190627132137.GB29016@Red> <20190627144339.GG31189@lunn.ch> <20190701122050.GA11021@Red> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190701122050.GA11021@Red> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > But thoses chips should have marking (according to some photos on > the web), so I probably own a counterfeiting of a > clone/counterfeiting. > At least, now i know that have a chip not designed to work with an external PHY, so all EXTPHY registers could be ignored. > My last ressort is to brute force all values until something happen. Does the rest of this work? You can actually transmit/receive frames, but it is a 10/Half? So the MAC is working, just the PHY is missing? > My simple tries, write 0xsomeval everywhere, lead to something, phy/eeprom return now 0x000y. > Probably, this chip doesnt have any PHY... If you look at dm9601_mdio_write() and dm9601_mdio_read() it always passes 1. 0 is used for the EEPROM, at least in a real device. so try 1-31 and see if you get anything interesting. Andrew