For people who have am335x computers - e.g. beagle device

[summers]

Hi All,

I've just done a new kernel for the various Beagle boards - basically for am333x devices.

I've pushed it back to Arch Linux - so it will have to be accepted, and then processed before pushing it out to all of you - but its on its way!

I've remove the firmware package for two reasons:
[*] Its huge so well worth removing
[*] It has nothing in it used on this device, under other it has some mali stuff in it - but the am335x doesn't use mali - so it not need needed.

I've tested it on both a beagle board black, and a pocket beagle - and both works.

Its version 6.18.1 btw,

David.

[summers]

Minor problem in the commit, the device tree blobs compiled don't have symbols, this means that you can't apply overlays to them, Just looking how to fix as part compile ...

[summers]

I've just pushed an update to the 6.19.6 kernel for am3xx devices.

The problem with overlays was lack of symbols in the dtb. As part of the inversitagtion here - it turned out that the overlays we have been using are years out of date. So I've updated to modern overlays with symbols compiled in. As part of this I've moved the overlays into /boot/dtbs/overlays - which is a more logical location for these. So anyone using overlays will need to move their scripts to the new location.

All of the patches were examined, some didn't apply, So were not relevant to beagle devices. So this means less patches applies, and not tied to the debian patches for arm hf. This also means can just straight to latest released kernel.

This has been tested on both pocket beagle and beagle bone black.

[summers]

I've just issued a pull request to update the kernel on beagle devices to 7.0.

This config has a problem - I have been unable to compile cfg80211 module on a beagle farm, specifically it take over 0.5GB to compile, and this means the OOM killer kills the gcc. This effectively means wireless isn't enabled. So if on a beagle device with wifi - it best not to update to this kernel. I'll keep trying to compile wireless properly on a beagle, but its been tricky to find a way forward. My guess is if Arch pulls the changes, IIRC they do the armv7 compile on a more capable machine than a beagle - so they may be able to enable wireless.

Note that all the pull requests above haven't not been been accepted into archlinuxarm github - so aren't part of the main distribution. As far as I can tell arch linux arm doesn't accept any pull requests, as they are rather a lot open: [url]https://github.com/archlinuxarm/PKGBUILDs/pulls[/url]. This is sad, it means they won't have followed the changes that were made above going through the compile - so how and why the compile has changed over time.

This has been tested on a pocketbeagle and a BBB.

So people can get the updated kernel I've uploaded the kernel packages that are made by this config into [url]https://github.com/davidjohnsummers/PKGBUILDs/tree/master/core/linux-am33x[/url] so you can download the packages from there if you want to move to the 7.0 kernel.

[summers]

I've respun the 7.0 kernel including 802.11 at the request of @graysky.

This was done by enabling a swap file, I was expecting thrashing to occur - but it went through smoothly and avoided the oom killer. My guess is 802.11 was only just going over the 0.5GB limit, and probably just swapping out other processes was enough for the gcc to compile.

So now the image should be good for all beagle owners, including those with 2GB eMMC.

[graysky]

Thanks for all your help to support keeping this package up to date. I commented on your pull request. Once you complete that step, I will happily merge. Thanks again.