search

networkimprov / arch-packages

1 stars 0 forks source link

submit our kernel to archlinuxarm.org #13

Open networkimprov opened 10 years ago

networkimprov commented 10 years ago

o.013. submit our kernel (config and patches) to archlinuxarm.org They're willing to support our board as soon as we send one. Package should include Tony's forthcoming linux-anvl test suite.

networkimprov commented 10 years ago

Pasted from #24:

Liam:

I believe they will support an anvl kernel if we provide an upstream for the config etc. I assume they'll maintain the pkgbuild, but I imagine they'll accept ours as a starting point. They automatically build each kernel release, and presumably test it on a board we give them. I prefer a dedicated anvl kernel since the generic armv7 build is loaded with irrelevant stuff.

Tom:

One thing to note is that we have packages which are required for the anvl to work. Namely anvl-usb so if we push the kernel we might want to push all required packages otherwise it doesnt make sense to push only the kernel in my opinion.

networkimprov commented 10 years ago

I'm not sure how ALARM handles rootfs differences among supported devices. I found this; not sure if it's still in use: https://github.com/archlinuxarm/PKGBUILDs/blob/master/scripts/chroot-builder

thomasdziedzic commented 10 years ago

Last updated 3 years ago and the scripts looks pretty bare. It also doesnt use the latest methods of installing a chroot namely arch-install-scripts, which leads me to believe it isnt used.

tmlind commented 10 years ago

For the kernel, I don't think we can use generic kernels yet because they don't yet work with PM. At least having USB EHCI compiled in would break PM. If EHCI is compiled in as modules, it might work as long as we blacklist them. Also, the armv7_defconfig contains several MB of extra stuff that will just waste memory. So generic kernels are certainly doable, but maybe let's wait on this for a while.