From owner-freebsd-arm@freebsd.org Wed Dec 14 18:22:45 2016 Return-Path: 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 27888C7660A for ; Wed, 14 Dec 2016 18:22:45 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0BFAE2AD for ; Wed, 14 Dec 2016 18:22:44 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 43914b29-c22a-11e6-9ec7-5d8fa496b077 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 43914b29-c22a-11e6-9ec7-5d8fa496b077; Wed, 14 Dec 2016 18:22:26 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBEIMZZI004202; Wed, 14 Dec 2016 11:22:35 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1481739755.1889.376.camel@freebsd.org> Subject: Re: When first hooking up a cubieboard2... From: Ian Lepore To: John.Kitz@xs4all.nl, "'Ganbold Tsagaankhuu'" Cc: freebsd-arm@freebsd.org Date: Wed, 14 Dec 2016 11:22:35 -0700 In-Reply-To: <001101d25626$d4c71ad0$7e555070$@Kitz@xs4all.nl> References: <585066dd.1c7c630a.8fe44.4233SMTPIN_ADDED_BROKEN@mx.google.com> <001101d25626$d4c71ad0$7e555070$@Kitz@xs4all.nl> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 18:22:45 -0000 On Wed, 2016-12-14 at 17:26 +0100, John W. Kitz wrote: > Ganbold, > > > > > > > > > On Wed, Dec 14, 2016 at 5:22 AM, John W. Kitz > > l> wrote: > > > Hi, > > > > > > When attaching a new cubieboard2 to a FreeBSD system for the > > > first  > > > time I > > > get: > > > > > > "ugen1.2: at usbus1 > > > umass0: on usbus1 > > > umass0:  SCSI over Bulk-Only; quirks = 0x4000 > > > umass0:4:0: Attached to scbus4 > > > > > > da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 > > > da0: Removable Direct Access > > > SCSI-2  > > > device > > > da0: 40.000MB/s transfers > > > da0: Attempt to query device size failed: NOT READY, Medium not  > > > present > > > da0: quirks=0x2 > > > > > > da1 at umass-sim0 bus 0 scbus4 target 0 lun 1 > > > da1: Removable Direct Access > > > SCSI-2  > > > device > > > da1: 40.000MB/s transfers > > > da1: Attempt to query device size failed: NOT READY, Medium not  > > > present > > > da1: quirks=0x2 > > > > > > da2 at umass-sim0 bus 0 scbus4 target 0 lun 2 > > > da2: Removable Direct Access > > > SCSI-2  > > > device > > > da2: 40.000MB/s transfers > > > da2: Attempt to query device size failed: NOT READY, Medium not  > > > present > > > da2: quirks=0x2" > > > > > > While looking at the hardware schematic, am I correct in assuming > > > that  > > > da0 represents the SD card slot, and da1 and da2 represent USB > > > port 1  > > > and 2 respectively? > > > > > > I don't remember the details, but there are 2 USB host ports > > > exposed on the board, and 1 USB otg port. > > > SD would be mmcsd0. > Well not the answer I was looking for, but this is what I got when > attaching the OTG port of a new cubieboard2 (NOT in FEL mode) to a > USB port on >an AMD64 / FreeBSD system. Since the messages all seem > to refer to removable storage devices attached to the same bus on > which the storage medium itself doesn't seem to be present, resulting > in the devices being reported as not ready, the only thing I could > imagine were the SD card slot (I believe using a converter it is > possible to connect that to a USB port as well) and the two other > (i.e. non OTG) USB ports. > > Looking into this a bit further is the difference maybe the result of > a different way of enumerating devices on Linux then on FreeBSD? > > If not, what conclusion should I draw from this? > > Regards, Jk. Your question actually doesn't make much sense.  I think the best answer possible about what you see when you connect a running cubieboard2 to a freebsd host is something like... What you see is entirely dependent on what software is running on the cubieboard when you connect it, and questions about what shows up and why should be addressed to whomever wrote that software. If freebsd is what's running on the board, then this is the right place to ask, but you'd have to provide more info about exactly what you're running (where you got the image or how you built it).  If you're running some linux image then the builder/distributor of that image could answer the questions. -- Ian