Bug 11740

Summary: DAFT: Enable BeagleBone OTG Ethernet interface on genericx86 images.
Product: [Build System, Metadata & Runtime] BSPs Reporter: Jair Gonzalez <jair.de.jesus.gonzalez.plascencia>
Component: bsps-configurationAssignee: Alejandro Hernandez <alejandro.hernandez>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: yp.bsp.watcher, yp.watcher
Version: 2.4   
Target Milestone: 2.5   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 11642    
Attachments:
Description Flags
MI_2.3_M3_rc1_dmesg
none
MI_2.3_M3_rc1_lsmod
none
rk_build212_dmesg
none
rk_build212_lsmod
none
genericx86-64_2.4_M1_rc1_dmesg
none
genericx86-64_2.4_M1_rc1_lsmod none

Description Jair Gonzalez 2017-06-30 17:24:04 UTC 
In order to implement bug 11642, it's necessary that the On the Go USB Ethernet interface that the BeagleBone Black provides to the DUT is detected and brought up in genericx86 images. This interface is used to communicate with the DUT after it is booted using the image to test. According to this, there is no way to communicate with the DUT if the Ethernet device is not operational.

The referred interface is working on meta-intel and Reference Kit images. I compared the kernel output in both, meta-intel and genericx86 images, and these lines are not present on the genericx86 one:

[    9.927678] cdc_ether 1-1:1.2 usb0: register 'cdc_ether' at usb-0000:00:14.0-1, CDC Ethernet Device, 82:bc:8d:d3:16:db
[    9.927755] usbcore: registered new interface driver cdc_ether
[   12.486317] cdc_ether 1-1:1.2 usb0: kevent 12 may have been dropped
Comment 1 Jair Gonzalez 2017-06-30 22:21:04 UTC 
Created attachment 3852 [details]
MI_2.3_M3_rc1_dmesg
Comment 2 Jair Gonzalez 2017-06-30 22:21:34 UTC 
Created attachment 3853 [details]
MI_2.3_M3_rc1_lsmod
Comment 3 Jair Gonzalez 2017-06-30 22:21:50 UTC 
For more reference, DAFT is using libcomposite to emulate a keyboard, a mass storage device and an ethernet device. I have also attached the output of dmesg and lsmod from a working Meta Intel 2.3 M3 rc1 image.
Comment 4 Jair Gonzalez 2017-07-11 18:13:33 UTC 
Created attachment 3865 [details]
rk_build212_dmesg
Comment 5 Jair Gonzalez 2017-07-11 18:14:56 UTC 
Created attachment 3866 [details]
rk_build212_lsmod
Comment 6 Jair Gonzalez 2017-07-11 18:16:36 UTC 
I have attached additional files with output from dmesg and lsmod on a Refkit image (build 212) running on a Minnowboard Turbot 64 bit.
Comment 7 Jair Gonzalez 2017-07-11 19:06:03 UTC 
Created attachment 3867 [details]
genericx86-64_2.4_M1_rc1_dmesg
Comment 8 Jair Gonzalez 2017-07-11 19:06:36 UTC 
Created attachment 3868 [details]
genericx86-64_2.4_M1_rc1_lsmod
Comment 9 Jair Gonzalez 2017-07-11 19:08:30 UTC 
I have attached additional files with output from dmesg and lsmod on a core-image-sato-sdk-genericx86-64.wic image (2.4 M1 rc1) running on a Minnowboard Turbot 64 bit.