From owner-freebsd-arm@freebsd.org  Fri Jan 19 20:19:58 2018
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 984F4EC5A0C
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Fri, 19 Jan 2018 20:19:58 +0000 (UTC)
 (envelope-from freebsd-arm@dino.sk)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1A98372A94
 for <freebsd-arm@freebsd.org>; Fri, 19 Jan 2018 20:19:57 +0000 (UTC)
 (envelope-from freebsd-arm@dino.sk)
Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Fri, 19 Jan 2018 21:19:54 +0100
 id 00F4BEDD.5A6252EA.000134D6
Date: Fri, 19 Jan 2018 21:19:53 +0100
From: Milan Obuch <freebsd-arm@dino.sk>
To: freebsd-arm@freebsd.org
Subject: Orange Pi R1 ethernet #2 + SDIO question
Message-ID: <20180119211953.5140bb57@zeta.dino.sk>
X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; i386-portbld-freebsd10.4)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jan 2018 20:19:58 -0000

Hi,

today I looked over some docs about Orange Pi R1's second ethernet
interface. Actually it is basically the same board as Orange Pi Zero,
just onboard USB connector is replaced with some Realtek USB ethernet
chip. With our current kernel and Orange Pi Zero DTB there is nothing
in usbconfig output.

Most probably we are missing some initialization step. After finding
mention of GPIO pin 20 in some Linux DTS, I decided simply try

# gpioctl -f /dev/gpioc0 20 1

and voila, it works:

ugen2.2: <Realtek USB 10100 LAN> at usbus2
ure0 on uhub1
ure0: <Realtek USB 10100 LAN, class 0/0, rev 2.10/20.00, addr 2> on usbus2
random: harvesting attach, 8 bytes (4 bits) from ure0
miibus1: <MII bus> on ure0
rlphy0: <RTL8201E 10/100 media interface> PHY 0 on miibus1
rlphy0: OUI 0x00e04c, model 0x0008, rev. 2
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
random: harvesting attach, 8 bytes (4 bits) from rlphy0
random: harvesting attach, 8 bytes (4 bits) from miibus1
ue0: <USB Ethernet> on ure0
ue0: bpf attached
ue0: Ethernet address: c0:74:2b:ff:e5:ff
ue0: link state changed to DOWN

After

# dhclient ue0

I was able to use this USB ethernet interface.

Maybe this activation could be inserted in DTS, but for now I consider
this ethernet usable (I tried some ping, ssh and some such over it with
success).

And now the question - both Orange Pi Zero and Orange Pi R1 have SDIO
connected wifi/bluetooth chip. I know there was some work on SDIO
framework in FreeBSD, but what about current status? Do we have
anything available for test? For me it is by no means urgent, just
these boards are available for cheap and quite good for tests...

Regards,
Milan