From owner-freebsd-arm@freebsd.org Wed Dec 14 16:26:34 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 54037C80349 for ; Wed, 14 Dec 2016 16:26:34 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud2.xs4all.net (lb3-smtp-cloud2.xs4all.net [194.109.24.29]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ED70B11AE for ; Wed, 14 Dec 2016 16:26:33 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id KsSV1u00R4VixDu01sSWDH; Wed, 14 Dec 2016 17:26:31 +0100 Reply-To: From: "John W. Kitz" To: "'Ganbold Tsagaankhuu'" Cc: References: <585066dd.1c7c630a.8fe44.4233SMTPIN_ADDED_BROKEN@mx.google.com> In-Reply-To: Subject: RE: When first hooking up a cubieboard2... Date: Wed, 14 Dec 2016 17:26:30 +0100 Message-ID: <001101d25626$d4c71ad0$7e555070$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdJVqeZfEplYU54lTzaAdTubtGWkGQAWGITAAAj1v6A= Content-Language: en-us 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 16:26:34 -0000 Ganbold, >> On Wed, Dec 14, 2016 at 5:22 AM, John W. Kitz = wrote: >> Hi, >> >> When attaching a new cubieboard2 to a FreeBSD system for the first=20 >> time I >> get: >> >> "ugen1.2: at usbus1 >> umass0: on usbus1 >> umass0: SCSI over Bulk-Only; quirks =3D 0x4000 >> umass0:4:0: Attached to scbus4 >> >> da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 >> da0: Removable Direct Access SCSI-2=20 >> device >> da0: 40.000MB/s transfers >> da0: Attempt to query device size failed: NOT READY, Medium not=20 >> present >> da0: quirks=3D0x2 >> >> da1 at umass-sim0 bus 0 scbus4 target 0 lun 1 >> da1: Removable Direct Access SCSI-2=20 >> device >> da1: 40.000MB/s transfers >> da1: Attempt to query device size failed: NOT READY, Medium not=20 >> present >> da1: quirks=3D0x2 >> >> da2 at umass-sim0 bus 0 scbus4 target 0 lun 2 >> da2: Removable Direct Access SCSI-2=20 >> device >> da2: 40.000MB/s transfers >> da2: Attempt to query device size failed: NOT READY, Medium not=20 >> present >> da2: quirks=3D0x2" >> >> While looking at the hardware schematic, am I correct in assuming = that=20 >> 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.