Missing kernel headers/images, how can I build my own?

GoogleGroups
1

I’ve successfully compiled a wifi module against 4.4.9-ti-r25, however having confirmed this is working I’d like to go back to an earlier image which uses 4.1.6-bone15

Unfortunately, while I see the patches here: http://rcn-ee.net/deb/jessie-armhf/v4.1.6-bone15/

I do not see the image or headers here: http://repos.rcn-ee.com/debian/pool/main/l/linux-upstream/

So far as I knew, the process is roughly this:

  1. Robert checks out the mainline
  2. Patches and builds the kernels, deploying to his repos, I think using https://github.com/RobertCNelson/linux-dev
  3. Builds the images with https://github.com/RobertCNelson/omap-image-builder , which uses the previous compiled kernels according to config.

What I can’t see is a 4.1.6-bone15 tag or branch in https://github.com/RobertCNelson/linux-dev ?

2

I've successfully compiled a wifi module against 4.4.9-ti-r25, however
having confirmed this is working I'd like to go back to an earlier image
which uses 4.1.6-bone15

Unfortunately, while I see the patches here:
Index of /deb/jessie-armhf/v4.1.6-bone15

I do not see the image or headers here:
http://repos.rcn-ee.com/debian/pool/main/l/linux-upstream/

That package has now been manually added back.. "sudo apt-get update"...

I'm constantly juggling space on that server (only have 192GB), i'm hoping
linode will implement some kinda of block storage option in the near future
like digitalocean is currently testing in beta. (before i upgrade to
Linode 16GB)

So far as I knew, the process is roughly this:

1) Robert checks out the mainline
2) Patches and builds the kernels, deploying to his repos, I *think* using
GitHub - RobertCNelson/linux-dev
3) Builds the images with
GitHub - RobertCNelson/omap-image-builder: omap image builder , which uses the
previous compiled kernels according to config.

What I can't see is a 4.1.6-bone15 tag or branch in
GitHub - RobertCNelson/linux-dev ?

So there are a number of repo's, the "bone" comes from,

But just use:

Follow the readme.md

and set:
kernel_tag="4.1.6-bone15"
and
toolchain="gcc_linaro_gnueabihf_4_9"

Regards,

3

Ah… thanks for adding that back Robert!

And also providing some further details on what repos to use - it’s great you’ve put so much effort into all these various tools and builds, but it can be a bit tricky piecing it all together as an outsider.

Marcos

4

Incidentally, regarding space, don’t know if you’ve considered Artifactory? We use it where I work: https://www.jfrog.com/artifactory/

5

Sorry, really I meant BinTray (there’s a free tier for OSS project, which this is obviously. You don’t really need Artifactory per se)

6

They'd probably kick me off pretty quick, right now on average i'm pushing
1.5 TB a month to our users.

I should just pull the trigger and upgrade it, but i'll need to find a 3
hour down time slot.. :wink:

Regards,

7

One other thing for posterity - the significance of version 4.1.6-bone15 is that’s the kernel the current Kamikaze image uses.

8

At the risk of sounding like a sales agent, they serve some pretty large OSS projects: https://bintray.com/