Release win 1.00.95.4

[Chenxi Han (5656hcx)]

Description

Updated driver version to 1.00.95.4.
Removed more x84 entries from .inf and project files.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Hotfix (urgent fix targeted at a release/x.y branch)
• Refactor (no functional change)
• Performance improvement
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test-only change
• CI / build-pipeline change

How has this been tested?

Build and Installation on 2 setups (x64 and arm64, Windows 11 25H2)

Checklist

• All required CI checks are green on the latest commit of this PR
• Build succeeds following the steps in the README / src/linux/README.md
• My code follows the Code Style Guidelines of this project
• My branch follows the naming convention: <branch-prefix>/<area>/<description>
• PR title follows the Conventional Commits format with our full-word types (feature / bugfix / hotfix / docs)
• I have performed a self-review of my own code
• I have added code comments in areas that are complex or hard to understand
• My changes generate no new compiler warnings
• I have added tests for my fix or feature (or noted why tests are not feasible)
• New and existing tests pass locally with my changes
• My branch is rebased onto the latest develop (or release/x.y for hotfix) - no merge commits
• Every commit has Signed-off-by: (DCO) - see CONTRIBUTING.md
• I have linked the relevant issue if any (Fixes #...)
• Any dependent changes have been merged and published in downstream modules

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌

[github-actions]

PRs From the Upstream Repository Are Not Accepted

Hi Chenxi Han (@5656hcx), thank you for your interest in contributing!

This pull request was opened from a branch inside the upstream repository (qualcomm/qcom-usb-kernel-drivers) rather than from a personal fork. All external contributions must come from a personal fork.

How to contribute correctly

1. Fork the repository: https://github.com/qualcomm/qcom-usb-kernel-drivers/fork
2. Clone your fork: git clone https://github.com/5656hcx/qcom-usb-kernel-drivers.git
3. Create a branch from develop: git checkout -b fix/your-description develop
4. Commit with DCO sign-off: git commit -s -m "fix(module): describe your change"
5. Push to your fork and open a PR targeting develop.

Please review CONTRIBUTING.md for the complete guide.

This PR has been closed automatically. We look forward to your fork-based contribution! 🙌