# aosp-m1000-kernel-prebuilt **Repository Path**: MooreThreads-AI-SOC/aosp-m1000-kernel-prebuilt ## Basic Information - **Project Name**: aosp-m1000-kernel-prebuilt - **Description**: No description available - **Primary Language**: Unknown - **License**: Not specified - **Default Branch**: common-android15-6.6-binaries - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-09-30 - **Last Updated**: 2025-12-04 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Binary Artifacts Management ## 1. Purpose of This Branch This `common-android15-6.6-binaries` branch stores pre-compiled binary artifacts (kernel, modules, DTBs) for specific project revisions. **IMPORTANT:** This branch does **not** maintain a standard Git history. It contains a single, constantly updated commit that always reflects the latest version of the binaries. The historical log of changes is manually maintained in the `CHANGELOG.md` file. --- ## 2. Key Files * **Binary Files (`modules/*.ko`, `*.dtb`, `Image`, etc.)**: The actual compiled files. These are replaced entirely with each update. * **`CHANGELOG.md`**: A manually curated log file. It records the revision history, associating each binary set with a source code commit or version number. **This file is updated with every change.** * **`README.md`**: This file. It contains the instructions for the update workflow. **This file should never be deleted.** --- ## 3. Workflow for Updating Binaries Follow these steps precisely to update the files in this branch. **Step 1: Get the Latest Version** Ensure you are on the `common-android15-6.6-binaries` branch and your local copy is synchronized with the remote. ```bash git checkout common-android15-6.6-binaries git pull origin common-android15-6.6-binaries ``` **Step 2: Clean Old Binaries** Delete **ONLY** the old binary files. Do **NOT** delete `README.md` or `CHANGELOG.md`. ```bash # Be specific to avoid deleting instruction files! rm -f modules/*.ko *.dtb Image # Add any other binary file patterns you have ``` **Step 3: Add New Binaries** Copy the new set of compiled binary files into the current directory. **Step 4: Update the Changelog** Prepend the new change information to the top of `CHANGELOG.md`. Replace the bracketed placeholders with your actual information. ```bash sed -i '2i\\\n## `date +'%Y-%m-%d'`\n- Kernel: [Kernel revision]\n- gr-kmd: [gr-kmd revision]\n---\n' CHANGELOG.md ``` **Step 5: Stage All Changes** Add all the new files and the changes to `CHANGELOG.md` to the staging area. ```bash git add . ``` **Step 6: Amend the Commit** Amend the existing commit. This replaces the old commit with a new one containing the updated files, keeping the history clean. ```bash git commit --amend -m "Kernel prebuilts for [Kernel revision/gr-kmd revision]." ``` **Step 7: Force Push to Remote** Push the amended commit to the remote repository. A force push is required because you have rewritten the branch's history. **⚠️ WARNING:** This is a destructive operation. Only perform it on this specific `common-android15-6.6-binaries` branch. ```bash git push --force origin common-android15-6.6-binaries ``` --- ## 4. Workflow for Using These Binaries If you are a user of these files, **DO NOT `git pull`** this branch if you already have it. To get the latest version, do one of the following: * **Recommended Method (Reset):** ```bash git fetch origin git checkout common-android15-6.6-binaries git reset --hard origin/common-android15-6.6-binaries ``` * **Simple Method (Re-clone):** ```bash # Clone just this single branch git clone --branch common-android15-6.6-binaries ```