Update README.md and CONTRIBUTING.md

Author: 5656hcx

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-## Contributing to Qualcomm Test Automation Controller (QTAC)
+## Contributing to Qualcomm USB Kernel Drivers
 
 Hi there!
 
@@ -9,19 +9,19 @@ Your help is essential for keeping this project great and for making it better.
 In general, contributors should develop on branches based off of `develop` and pull requests should be made against `develop`.
 
 ## Submitting a pull request
-1. Please read our [code of conduct](CODE-OF-CONDUCT.md) and [license](LICENSE).
+1. Please read our [code of conduct](CODE-OF-CONDUCT.md) and [license](LICENSE.txt).
 
-2. [Fork](https://github.com/qualcomm/qcom-test-automation-controller/fork) and clone the repository.
+2. [Fork](https://github.com/qualcomm/qcom-usb-kernel-drivers/fork) and clone the repository.
     ```bash
-    git clone https://github.com/<username>/qcom-test-automation-controller.git
+    git clone https://github.com/<username>/qcom-usb-kernel-drivers.git
     ```
 3. Create a new branch based on `develop`:
     ```bash
     git checkout -b <my-branch-name> develop
     ```
 4. Create an upstream `remote` to make it easier to keep your branches up-to-date:
     ```bash
-    git remote add upstream https://github.com/qualcomm/qcom-test-automation-controller.git
+    git remote add upstream https://github.com/qualcomm/qcom-usb-kernel-drivers.git
     ```
 
 5. Make your changes, add tests, and make sure tests passes.
@@ -43,7 +43,7 @@ In general, contributors should develop on branches based off of `develop` and p
 
     The `-u` is shorthand for `--set-upstream`. This will set up the tracking reference so subsequent runs of `git push` or `git pull` can omit the remote and branch.
 
-9. [Submit a pull request](https://github.com/qualcomm/qcom-test-automation-controller/pulls) from your branch to `develop`.
+9. [Submit a pull request](https://github.com/qualcomm/qcom-usb-kernel-drivers/pulls) from your branch to `develop`.
 
 10. Pat yourself on the back and wait for your pull request to be reviewed.
 

README.md

@@ -3,10 +3,11 @@ Qualcomm kernel drivers provide logical representations of Qualcomm chipset-enab
 The project is organized to facilitate easy compilation, testing, and integration into custom hardware solutions.
 
 ## Key Features
-  - Supports Both Windows and Linux platforms.
-  - Supports Windows on Snapdragon hosts and both X64/X86/ARM64 devices.
-  - WHQL-certified and optimized for the latest Windows 11 operating systems.
-  - Compatible with existing tools like QUTS, QDL, Qualcomm Device Launcher, and more.
+  - Supports Windows and Linux platforms.
+  - Supports X64/X86/ARM64 architectures.
+  - WHQL-certified on the latest Windows operating systems.
+  - Compatible with Qualcomm tools like QUTS, QXDM, PCAT, and more.
+  - Compatible with terminal emulators like PuTTY and Tera Term.
 
 ## Repository Structure
 
@@ -19,55 +20,72 @@ The project is organized to facilitate easy compilation, testing, and integratio
 └─ ...                    # Other files and directories
 ```
 
-## Software install guide
+## Build Instructions
 
 ### Prerequisites
 
 #### Windows
 
 - Visual Studio 2019 (or later) with **Desktop development with C++** workload.
-- Windows Driver Kit for Windows 10, version 1809 or later
-- Administrator rights for driver installation.
-- Perl v5.26.3 or later
+- Windows Driver Kit for Windows 10, version 1903 (18362.1) or later.
 
 #### Linux
 
 - GNU Make, GCC/Clang.
 - Kernel headers for the target kernel version (`linux-headers-$(uname -r)`).
 
-### Building the Drivers
+### Build Steps
 
 #### Windows
-Clone the repository
-    
-```bash
-git clone https://github.com/microsoft/vcpkg.git
-```
-Navigate to directory where the code was cloned `src\windows`
-
-From the project root, open the .sln file with Visual Studio
-
-In Visual Studio, select `Build` > `Build Solution` from the top menu.
-
-Compiled binaries will be located in a path based on build configuration, for example:
-```bash    
-<ProjectRootDir>\x64\Debug\
-<ProjectRootDir>\x64\Release\
-```
+1. Clone the repository
+   ```bash
+   git clone https://github.com/qualcomm/qcom-usb-kernel-drivers.git
+   ```
+2. Navigate to directory where the code was cloned
+   ```bash
+   cd /src/windows/<project-name>
+   ```
+3. From the project root, open the .vcxproj file in Visual Studio.
+
+4. In Visual Studio, select `Build` > `Build Solution` from the top menu.
+
+The output binaries are generated in a path depends on the chosen build configuration. For example:
+
+    <ProjectRootDir>\x64\Debug\
+    <ProjectRootDir>\x64\Release\
       
 #### Linux
 ```bash
 cd src/linux
 make
 ```
 
-#### Windows command:
+## Install / Uninstall
+
+#### Windows
 - Installation
+
+  Right click the `.inf` file in output folder and select **Install**.
+  Or install via `pnputil`:
 ```bash
-<ProjectRoot>\install\install.bat
+pnputil /add-driver <build_path/driver_name.inf> /install
 ```
-- Uninstallation
-
+- Uninstallation (Device Manager)
+1. Open **Device Manager**.
+2. Right click the target device and select **Uninstall device**.
+3. Check **Attempt to remove the driver for this device**.
+4. Click **Uninstall**.
+
+- Uninstallation (Command Line)
+
+1. Locate the **Published Name** of the installed driver package:
+  ```bash
+  pnputil /enum-drivers
+  ```
+2. Delete the driver from system
+  ```bash
+  pnputil /delete-driver oemxx.inf /uninstall /force
+  ```
 #### Linux command:
   Navigate to folder `src/linux`
 
@@ -91,11 +109,11 @@ Please follow the existing coding style and run the appropriate static analysis
 
 ## Bug & Vulnerability reporting
 
-Please review the [SECURITY.md](./.github/SECURITY.md) before reporting vulnerabilities with the project
+Please review the [security](./.github/SECURITY.md) before reporting vulnerabilities with the project
 
 ## Contributor's License Agreement
 
-Please review the Qualcomm product [license](./LICENSE), [code of conduct](./CODE-OF-CONDUCT.md) & terms
+Please review the Qualcomm product [license](./LICENSE.txt), [code of conduct](./CODE-OF-CONDUCT.md) & terms
 and conditions before contributing.
 
 ## Contact