From owner-freebsd-arm@FreeBSD.ORG Thu Jul 16 09:33:54 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9180C1065672 for ; Thu, 16 Jul 2009 09:33:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.swip.net [212.247.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id EF4A78FC13 for ; Thu, 16 Jul 2009 09:33:53 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=vWjDCZN0tDgA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=6I5d2MoRAAAA:8 a=LB_BjYVugI_Mejrs-OwA:9 a=Y0hpUecGYeMhxM8fhG4A:7 a=RLYROsxkiImR_ya2IVyN9EK9df4A:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe13.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 890686109; Thu, 16 Jul 2009 10:33:51 +0200 From: Hans Petter Selasky To: Krassimir Slavchev Date: Thu, 16 Jul 2009 10:33:33 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA1; KDE/4.2.4; i386; ; ) References: <4A5C3BF5.9030200@bulinfo.net> <200907151532.03875.hselasky@c2i.net> <4A5DF89A.1070004@bulinfo.net> In-Reply-To: <4A5DF89A.1070004@bulinfo.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907161033.34560.hselasky@c2i.net> Cc: freebsd-arm@freebsd.org Subject: Re: ohci not detected on at91rm9200? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 09:33:54 -0000 On Wednesday 15 July 2009 17:41:14 Krassimir Slavchev wrote: > Hans Petter Selasky wrote: > > On Wednesday 15 July 2009 15:23:14 Krassimir Slavchev wrote: > >> Hans Petter Selasky wrote: > >>>> It is detected but after configuring the interface I cannot > >>>> send/receive > >>> > >>> You need to "ifconfig up" the interface on both sides before any > >>> traffic will pass. > >> > >> Of course they are: > >> > >> cdce0: > >> flags=108c43 > >> metric 0 mtu 1500 > >> ether 2a:00:00:00:00:00 > >> inet 192.168.2.121 netmask 0xffffff00 broadcast 192.168.2.255 > >> media: Ethernet 10baseT/UTP > >> status: active > >> > >> ate0: flags=8843 metric 0 mtu > >> 1500 options=8 > >> ether 43:00:00:01:ff:00 > >> inet 192.168.2.189 netmask 0xffffff00 broadcast 192.168.2.255 > >> media: Ethernet autoselect (100baseTX ) > >> status: active > > > > You should have cdce devices on both sides, PC and Host. Looks like there > > will be a network conflict if you use 192.168.2.xx for both network > > devices when they are not on the same cable. > > > > ? > > Yes, I realize that. > > After adding cdce on arm board: > cdce0: on usbus0 > ue0: on cdce0 > ue0: Ethernet address: 2a:23:45:67:89:54 > > ue0: flags=8843 metric 0 mtu 1500 > ether 2a:23:45:67:89:54 > > > But on the other side running 7.2: > cdce0: 1.10/1.00, addr 2> on uhub4 > cdce0: setting alternate interface failed > device_attach: cdce0 attach returned 6 Maybe the following patch helps on the ARM side: http://perforce.freebsd.org/chv.cgi?CH=166156 I'm going to test this setup, and will probably resolve the issue, if I find any, including the cache sync stuff. --HPS