# Where's the source?

**URL:** <https://forum.clockworkpi.com/t/wheres-the-source/7689>\
**Category:** DevTerm\
**Created:** [December 19, 2021, 8:27pm UTC](https://forum.clockworkpi.com/t/wheres-the-source/7689 "2021-12-19T20:27:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rde1024](https://avatars.discourse-cdn.com/v4/letter/r/8dc957/32.png) [@rde1024](https://forum.clockworkpi.com/u/rde1024)\
**Post date:** [December 19, 2021, 8:27pm UTC](https://forum.clockworkpi.com/t/wheres-the-source/7689/1 "2021-12-19T20:27:08Z")

</div>

I know about the GitHub repo, but it seems woefully incomplete. At first glance, none of the Debian packaging is present for any package (except for wiringpi, which is an external project). The patches for the armbian kernel don’t seem to be relevant because the current image build process discards the armbian-built kernel package (after patching it, wtf) and installs a completely different package (devterm-kernel-current-cpi-a06). There’s another kernel patch just sitting around, but it’s not clear that it’s actually used for anything.

I can probably put together my own packaging for the non-kernel packages based on the source code present in the GitHub repo, but for the kernel, I need to at least have the kernel source (in version control, please) and any patches that are being used to produce devterm-kernel-current-cpi-a06\_0.2\_arm64.deb .

@guu I think this is your rodeo?

---

<div class="post-metadata">

**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\
**Post date:** [December 20, 2021, 2:38am UTC](https://forum.clockworkpi.com/t/wheres-the-source/7689/2 "2021-12-20T02:38:52Z")

</div>

it is not a redeo

in fact we wont keep any source in our hands

checkout the wiki

I append the reson for devterm-kernel-current-cpi-a06\_0.2\_arm64.deb

```auto
after image done
unzip linux-dtb-current-rockchip64.db, linux-image-current-rockchip64.dtb
and then combine all files ,all the postinst, preinst,prerm,postrm
to be one devterm-kernel-current-cpi-a06.dtb
the reason is if not doing this , apt-get upgrade will replace the linux-dto,linux-image* in future, which will cause boot failed
so to keep a06 linux kernel in safe , I made devterm-kernel-current-cpi-a06

```

and there is an issue days ago metioned this

> <https://github.com/clockworkpi/DevTerm/issues/10>
>
> I'm following along the instructions described in \`Create DevTerm A06 OS image f…rom scratch\` wiki page and there's something I don't quite understand. It seems that first we carefully apply kernel and u-boot patches and then build the image that's going to contain these patched kernel and u-boot; okay, makes sense so far. However, further down the lines in chroot we execute this
> \`\`\`bash
> sudo apt remove linux-image\*
> sudo apt install devterm-kernel-current-cpi-a06 devterm-fan-daemon-cpi-a06 devterm-thermal-printer devterm-thermal-printer-cups devterm-wiringpi-cpi devterm-first-start-a06
> \`\`\`
> which to me looks like we completely remove our carefully patched and compiled kernel - perhaps of the exact version we wanted - and replace it with a precompiled binary from DevTerm repository.
> 
> Why do we do that?

---

<div class="post-metadata">

**Author:** ![rde1024](https://avatars.discourse-cdn.com/v4/letter/r/8dc957/32.png) [@rde1024](https://forum.clockworkpi.com/u/rde1024)\
**Post date:** [December 20, 2021, 3:39am UTC](https://forum.clockworkpi.com/t/wheres-the-source/7689/3 "2021-12-20T03:39:56Z")

</div>

Thanks for your reply and wiki update. I’m much less confused now. I probably should have checked the closed issues in addition to just the open ones.

I didn’t mean to confuse you by using the term “rodeo”. That’s just an English idiom. In this case it means “area of expertise and responsibility”. I saw that you were performing most of the commits, so I guessed you might be the best person to ask.

In any case, I intend to do some repackaging of the kernel/dtb package(s) based on a simple fork of the Debian project’s kernel packaging. That should be a pretty good jumping-off point for eventual attempts to get the A06 DevTerm to work with the mainline kernel and a vanilla arm64 kernel package (i.e. foisting it off on Ben Hutchings et. al.). It should also simplify or eliminate that combination step. I’ll let you know when I have something useful.