On 7/14/14, 7:41 PM, "David Lambert" <[email protected]> wrote:
>I don't see any mention of 3.14. I have been using 3.14.8-bone5 for >quite a few weeks now. I could never get USB to work on 3.15.x. Should I >revert to 3.13.x?? USB is working fine for me on V3.15.4-bone4. What is it that you are trying to do that does not work? Here is an example of USB working on V3.15: I have a Ortek Wireless keyboard and mouse connected to a powered USB Hub. root@arm:~# lsusb Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 05a4:2000 Ortek Technology, Inc. WKB-2000 Wireless Keyboard with Touchpad Now I insert a SanDisk USB flash drive: root@arm:~# [23389.316005] usb 2-1.2: new high-speed USB device number 4 using musb-hdrc [23389.416641] usb 2-1.2: device v0781 p5575 is not supported [23389.422448] usb 2-1.2: New USB device found, idVendor=0781, idProduct=5575 [23389.429756] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [23389.437477] usb 2-1.2: Product: Cruzer Glide [23389.441974] usb 2-1.2: Manufacturer: SanDisk [23389.446499] usb 2-1.2: SerialNumber: 20043515931AE20186C5 [23389.454569] usb-storage 2-1.2:1.0: USB Mass Storage device detected [23389.462767] scsi0 : usb-storage 2-1.2:1.0 [23390.467381] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 [23390.481964] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) [23390.502368] sd 0:0:0:0: [sda] Write Protect is off [23390.515109] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [23390.551041] sda: sda1 sda2 [23390.565653] sd 0:0:0:0: [sda] Attached SCSI removable disk So plug&play works fine. Confirm the SanDisk drive was recognized correctly: root@arm:~# lsusb Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0781:5575 SanDisk Corp. Bus 002 Device 003: ID 05a4:2000 Ortek Technology, Inc. WKB-2000 Wireless Keyboard with Touchpad Mount the Drive: root@arm:/media# mount /dev/sda1 diska mount: block device /dev/sda1 is write-protected, mounting read-only Display drive contents: root@arm:/media# ls diska autorun.inf doc install pool README.txt boot efi install.amd README.html setup.exe css firmware isolinux README.mirrors.html tools debian g2ldr md5sum.txt README.mirrors.txt win32-loader.ini dists g2ldr.mbr pics README.source Regards, John > >Dave. > >On 07/14/2014 04:39 PM, Robert Nelson wrote: >> On Mon, Jul 14, 2014 at 4:34 PM, Maxim Podbereznyy <[email protected]> >>wrote: >>> Hi guys! >>> >>> I can see Robert offers 3 kernel vesions for bbb: >>> 1) v3.8.x >>> 2) v3.13.x >>> 3) v3.15.x >>> >>> who can tell pros and cons for each of them? I need one to prepare >>>something >>> stable/reliable for my client. >> v3.8.x = capemgr >> v3.13.x = working sgx >> v3.15.x = it's going to be short lived, planing to moving to v3.16.x >> pretty soon, as that'll have a "rt" and it should be the default for >> "jessie" >> >> Regards, >> > >-- >For more options, visit http://beagleboard.org/discuss >--- >You received this message because you are subscribed to the Google Groups >"BeagleBoard" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
