Monthly Archives: April 2019

Source Code

Cisco 8811 chip : Broadcom Cygnus Soc

Mailing list: https://lore.kernel.org/lkml/1410897497-27527-1-git-send-email-jonathar@broadcom.com/

Linux/Kernel -> Android-> Qualcomm -> LineageOS

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/

https://android.googlesource.com/

https://source.codeaurora.org/quic/la/

https://github.com/LineageOS/android

Some:

https://github.com/aosp-mirror/platform_build/blob/android-p-preview-5/envsetup.sh 

https://source.codeaurora.org/quic/la/platform/build/tree/envsetup.sh?h=LA.UM.6.4.r4

https://source.codeaurora.org/quic/la/platform/build/tree/envsetup.sh?h=ks-aosp.lnx.1.0.r4-rel&id=b7f1eff7eb6d94b32936f791936b3d7821cf26df

https://github.com/LineageOS/android_device_xiaomi_msm8953-common/blob/lineage-15.1/extract-files.sh

https://github.com/LineageOS/android_vendor_lineage/blob/lineage-15.1/build/tools/extract_utils.sh

https://wiki.codeaurora.org/xwiki/bin/QAEP

Review:

https://android-review.googlesource.com/q/status:open

Openwrt:

https://git.openwrt.org/?p=openwrt/openwrt.git;a=summary

 

再说USB

USB-C (USB Type-c) 一定是USB 3.1吗?

USB Type-C isn’t the same thing as USB 3.1, though. USB Type-C is just a connector shape, and the underlying technology could just be USB 2 or USB 3.0. In fact, Nokia’s N1 Android tablet uses a USB Type-C connector, but underneath it’s all USB 2.0—not even USB 3.0. However, these technologies are closely related. When buying devices, you’ll just need to keep your eye on the details and make sure you’re buying devices (and cables) that support USB 3.1.

From: https://www.howtogeek.com/211843/usb-type-c-explained-what-it-is-and-why-youll-want-it/ 

为什么有的USB3.0不是蓝色的接口? 

只是建议,不一定必须是.

SinceUSB 2.0 and USB 3.0 ports may coexist on the same machine and they look similar, the USB 3.0 specification recommends that the Standard-A USB3.0 receptacle have a blue insert (Pantone 300C color).

From: Google

SATA Some

 

from: https://superuser.com/questions/1028231/what-sata-version-do-i-have 

Model Family:     HGST Travelstar 7K1000
Device Model:     HGST HTS721010A9E630
Serial Number:    JG40006PGJL7XC
LU WWN Device Id: 5 000cca 6acc78a77
Firmware Version: JB0OA3B0
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 18 00:01:09 2016 JST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

The signaling speeds and the sata versions supported are indicated by different bits of the data return by the IDENTIFY DEVICE command. You can see that with smartctl --identify=wb /dev/sdX | grep -i sata.

As you can see, the signal speeds supported are stored in word 76 and the versions are stored in word 222. It’s documented in ACS-3 rev 5, Table 45 — IDENTIFY DEVICE data (http://www.t13.org/Documents/UploadedDocuments/docs2013/d2161r5-ATAATAPI_Command_Set_-_3.pdf).

These are the capabilities reported by the drive itself, so don’t mix it up with what is supported by your motherboard, which is CAN BE indicated by “current:” in the smartctl output (and dmesg as told in the other answer from @Jonno)

EDIT: Here is the exact spec file your drive claim to conform with: http://www.t13.org/documents/uploadeddocuments/docs2008/d1699r6-ata8-acs.pdf (ATA8-ACS T13/1699-D revision 6). You can see the two words in Table 29 — IDENTIFY DEVICE data. As you can see, SATA 2.6 and 3.0Gb/s are the latest/maximum defined as of this revision of ACS. So I guess your drive simply doesn’t completely conform with the spec and set the 6.0Gb/s bit, which is defined later, to 1 instead of 0.