Device Information
Product: Lenovo Legion Tab (8.8", Gen 3)
Model Number: TB321FU
SoC: Qualcomm Snapdragon 8 Gen 3
Operating System: Android 14 with Lenovo ZUI 16.1
Current Firmware: TB321FU_ROW_OPEN_USER_Q00040.0_U_ZUI_16.1.10.059
Issue Description
The Lenovo Legion Tab (TB321FU) is currently being distributed without complete GPL-compliant source code availability. Specifically:
Kernel source code is available on the Lenovo Open Source Portal (https://support.lenovo.com/us/en/solutions/ht511330-lenovo-open-source-portal) for this model but incomplete
Device tree source files (.dts/.dtsi) are completely missing
This device runs a modified Linux kernel under GPLv2, and according to the license terms, complete corresponding source code must be made available to users.
GPL Compliance Requirements
Under GPLv2 Section 3, distributors must provide:
Complete source code for all GPL-licensed software components
All scripts and build tools necessary to compile and install the executable
Device tree sources that are compiled as part of the kernel build process
Lenovo has committed to the GPL Cooperation Commitment (as documented in this repository), which demonstrates your company's dedication to open source compliance. I'm raising this issue in the spirit of that commitment, hoping for a collaborative resolution.
Request
I respectfully request that Lenovo:
Publish the complete kernel source code for the TB321FU model, including all Lenovo modifications
Include all device tree source files (.dts and .dtsi files) for this device
Provide build instructions and configuration files necessary to compile a bootable kernel
Update the source code when firmware updates are released, ensuring ongoing compliance
Additional Context
This appears to be part of a broader pattern with Lenovo Android devices. Similar issues have been reported for other models:
Lenovo P11 (TB-J606F) - Issue #1 in this repository
Other Lenovo tablets have incomplete or outdated kernel sources on the portal
The development community greatly values Lenovo's participation in the GPL Cooperation Commitment. Publishing these sources would not only fulfill GPL obligations but also:
Enable custom ROM development
Allow security researchers to audit the code
Help users who want to exercise their software freedom rights
Foster goodwill in the open source community
Current Status on Open Source Portal
I have checked the Lenovo Open Source Portal and confirmed:
✗ Incomplete kernel source code for TB321FU
✗ No device tree sources
Suggested Timeline
Given that this device is actively being sold and marketed, I would appreciate:
An acknowledgment of this issue within 30 days
Publication of the source code within 60 days
Establishment of a process to ensure ongoing compliance for future firmware updates
Contact
I'm happy to provide additional information or clarification as needed. I appreciate Lenovo's commitment to the GPL Cooperation Commitment and look forward to a collaborative resolution of this compliance gap.
Thank you for your attention to this matter.
Note: This issue is being raised in accordance with Lenovo's GPL Cooperation Commitment, which provides a cure period for compliance issues. I recognize that Lenovo has committed to good faith efforts in GPL compliance, and I'm approaching this matter constructively.
Device Information
Product: Lenovo Legion Tab (8.8", Gen 3)
Model Number: TB321FU
SoC: Qualcomm Snapdragon 8 Gen 3
Operating System: Android 14 with Lenovo ZUI 16.1
Current Firmware: TB321FU_ROW_OPEN_USER_Q00040.0_U_ZUI_16.1.10.059
Issue Description
The Lenovo Legion Tab (TB321FU) is currently being distributed without complete GPL-compliant source code availability. Specifically:
Kernel source code is available on the Lenovo Open Source Portal (https://support.lenovo.com/us/en/solutions/ht511330-lenovo-open-source-portal) for this model but incomplete
Device tree source files (.dts/.dtsi) are completely missing
This device runs a modified Linux kernel under GPLv2, and according to the license terms, complete corresponding source code must be made available to users.
GPL Compliance Requirements
Under GPLv2 Section 3, distributors must provide:
Complete source code for all GPL-licensed software components
All scripts and build tools necessary to compile and install the executable
Device tree sources that are compiled as part of the kernel build process
Lenovo has committed to the GPL Cooperation Commitment (as documented in this repository), which demonstrates your company's dedication to open source compliance. I'm raising this issue in the spirit of that commitment, hoping for a collaborative resolution.
Request
I respectfully request that Lenovo:
Publish the complete kernel source code for the TB321FU model, including all Lenovo modifications
Include all device tree source files (.dts and .dtsi files) for this device
Provide build instructions and configuration files necessary to compile a bootable kernel
Update the source code when firmware updates are released, ensuring ongoing compliance
Additional Context
This appears to be part of a broader pattern with Lenovo Android devices. Similar issues have been reported for other models:
Lenovo P11 (TB-J606F) - Issue #1 in this repository
Other Lenovo tablets have incomplete or outdated kernel sources on the portal
The development community greatly values Lenovo's participation in the GPL Cooperation Commitment. Publishing these sources would not only fulfill GPL obligations but also:
Enable custom ROM development
Allow security researchers to audit the code
Help users who want to exercise their software freedom rights
Foster goodwill in the open source community
Current Status on Open Source Portal
I have checked the Lenovo Open Source Portal and confirmed:
✗ Incomplete kernel source code for TB321FU
✗ No device tree sources
Suggested Timeline
Given that this device is actively being sold and marketed, I would appreciate:
An acknowledgment of this issue within 30 days
Publication of the source code within 60 days
Establishment of a process to ensure ongoing compliance for future firmware updates
Contact
I'm happy to provide additional information or clarification as needed. I appreciate Lenovo's commitment to the GPL Cooperation Commitment and look forward to a collaborative resolution of this compliance gap.
Thank you for your attention to this matter.
Note: This issue is being raised in accordance with Lenovo's GPL Cooperation Commitment, which provides a cure period for compliance issues. I recognize that Lenovo has committed to good faith efforts in GPL compliance, and I'm approaching this matter constructively.