Date: Wed, 14 Dec 2016 22:50:19 +0100 From: "John W. Kitz" <John.Kitz@xs4all.nl> To: "'Ian Lepore'" <ian@freebsd.org>, "'Ganbold Tsagaankhuu'" <ganbold@gmail.com> Cc: <freebsd-arm@freebsd.org> Subject: RE: When first hooking up a cubieboard2... Message-ID: <001701d25654$111d4c20$3357e460$@Kitz@xs4all.nl> In-Reply-To: <1481749803.1889.406.camel@freebsd.org> References: <585066dd.1c7c630a.8fe44.4233SMTPIN_ADDED_BROKEN@mx.google.com> <CAGtf9xPQq1qGjmHci4n52uXx=E%2ByuHrNkRcuAyDDQvRt8a5rYQ@mail.gmail.com> <001101d25626$d4c71ad0$7e555070$@Kitz@xs4all.nl> <1481739755.1889.376.camel@freebsd.org> <001101d25641$0e794fe0$2b6befa0$@Kitz@xs4all.nl> <1481749803.1889.406.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian, > On Wed, 2016-12-14 at 20:34 +0100, John W. Kitz wrote: > > Gents, > >=20 > > On Wed, 2016-12-14 at 17:26 +0100, John W. Kitz wrote: > > >=20 > > > >=20 > > > > Ganbold, > > > >=20 > > > > >=20 > > > > >=20 > > > > > >=20 > > > > > >=20 > > > > > > On Wed, Dec 14, 2016 at 5:22 AM, John W. Kitz = <John.Kitz@xs4a=20 > > > > > > ll.n > > > > > > l> wrote: > > > > > > Hi, > > > > > >=20 > > > > > > When attaching a new cubieboard2 to a FreeBSD system for the = > > > > > > first time I > > > > > > get: > > > > > >=20 > > > > > > "ugen1.2: <USB Developer> at usbus1 > > > > > > umass0: <Mass Storage> on usbus1 > > > > > > umass0:=A0=A0SCSI over Bulk-Only; quirks =3D 0x4000 > > > > > > umass0:4:0: Attached to scbus4 > > > > > >=20 > > > > > > da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 > > > > > > da0: <USB 2.0 USB Flash Driver 0100> Removable Direct Access > > > > > > SCSI-2 > > > > > > device > > > > > > da0: 40.000MB/s transfers > > > > > > da0: Attempt to query device size failed: NOT READY, Medium=20 > > > > > > not present > > > > > > da0: quirks=3D0x2<NO_6_BYTE> > > > > > >=20 > > > > > > da1 at umass-sim0 bus 0 scbus4 target 0 lun 1 > > > > > > da1: <USB 2.0 USB Flash Driver 0100> Removable Direct Access > > > > > > SCSI-2 > > > > > > device > > > > > > da1: 40.000MB/s transfers > > > > > > da1: Attempt to query device size failed: NOT READY, Medium=20 > > > > > > not present > > > > > > da1: quirks=3D0x2<NO_6_BYTE> > > > > > >=20 > > > > > > da2 at umass-sim0 bus 0 scbus4 target 0 lun 2 > > > > > > da2: <USB 2.0 USB Flash Driver 0100> Removable Direct Access > > > > > > SCSI-2 > > > > > > device > > > > > > da2: 40.000MB/s transfers > > > > > > da2: Attempt to query device size failed: NOT READY, Medium=20 > > > > > > not present > > > > > > da2: quirks=3D0x2<NO_6_BYTE>" > > > > > >=20 > > > > > > While looking at the hardware schematic, am I correct in=20 > > > > > > assuming that > > > > > > da0 represents the SD card slot, and da1 and da2 represent = USB=20 > > > > > > port 1 and 2 respectively? > > > > > >=20 > > > > > > 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=20 > > > > attaching the OTG port of a new cubieboard2 (NOT in FEL mode) to = a=20 > > > > USB port on >an AMD64 / FreeBSD system. Since the messages all=20 > > > > seem to refer to removable storage devices attached to the same=20 > > > > bus on which the storage medium itself doesn't seem to be = present,=20 > > > > resulting in the devices being reported as not ready, the only=20 > > > > thing I could imagine were the SD card slot (I believe using a=20 > > > > converter it is possible to connect that to a USB port as well)=20 > > > > and the two other (i.e. non > > > > OTG) > > > > USB ports. > > > >=20 > > > > Looking into this a bit further is the difference maybe the = result=20 > > > > of a different way of enumerating devices on Linux then on=20 > > > > FreeBSD? > > > >=20 > > > > If not, what conclusion should I draw from this? > > > >=20 > > >=20 > > > Your question actually doesn't make much sense. =A0I think the = best=20 > > > answer > > > possible about what you see when you connect a running > > >=20 > > > cubieboard2 to a freebsd host is something like... > > >=20 > > > What you see is entirely dependent on what software is running on=20 > > > the > > cubieboard when you connect it, and questions about what shows up = and=20 > > why > should be addressed to whomever wrote that software. > >=20 > > I'm not referring to what I see on the cubieboard2, but as I = mentioned=20 > > to what I'm seeing on the console of an AMD64 / FreeBSD system to=20 > > which I'm attaching it. > >=20 > >=20 > > If freebsd is what's running on the board, then this is the right=20 > > 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). =A0If you're=20 > > running some linux image then the builder/distributor of that image=20 > > could answer >the questions. > >=20 > > The board is straight out of the box brand spanking new, so AFAIK=20 > > there's nothing running on it yet. > >=20 > > Jk. > What you are seeing on the freebsd console is the devices that the software running on the cubieboard provides. =A0Even fresh out of the = box, it is > running something (presumably some linux or android distro that = gets put into the nand flash at the factory). > This has nothing to do with freebsd.=A0=A0You'd see the same thing if = you plugged it into a windows system. Thanks for pointing that out; I was already aware of that, but my = question was: which storage devices on the board do da0, da1 and da2 represent = 'as seen', if you will, from and on the FreeBSD system to which it is = attached? Regards, Jk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001701d25654$111d4c20$3357e460$>