Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

1714 profile views
  1. This might come a few months late, but in case someone runs into the same trouble and finds this (like I did): It's probably the compiler version. Using a 4.9.x series compiler did the trick (at least for me). It didn't matter if I used gentoo's 4.9 crossdev compiler for aarch64 (gcc version 4.9.4 (Gentoo 4.9.4-r1 p1.1, pie-0.6.4) ) or the linaro compiler from the "official" amlogic toolchain (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ), both worked.
  2. Yeah, that's probably it. And I wasn't sure if I was imagining things, but it really looks like BAT. So... I guess this board actually has battery support.
  3. Actually.... that 4 pin header might actually be related to battery connection. Would explain the location. Not sure about the jumper, however.
  4. Hello, since my good friend and favorite tinkerer Olgierd wanted to run this http://www.ebay.com/itm/1-44-Red-Serial-128X128-SPI-Color-TFT-LCD-Module-Display-Replace-Nokia-5110-LCD-/262136737086?hash=item3d08912d3e%3Ag%3AwyQAAOSwoydWoYhX on his OPi, but the drivers aren't in the 3.4 kernel I did that https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/3511b0d142f4632f77cd1d82bae08bc584f54805.patch It isn't art, but it's working (or so he said). Alright, there seems to be a timing issue when loading the module for the first time.... Feel free to use it to your repo if you feel like using it. Regards Sven
  5. Good, then I think we agree very much here. Since I happily adopted most of the patches from the H3 kernel I would be a rather cynical linuxer to not pass upwards what I deem useful. That I don't do that on your repo is simply due to the fact that I think that you guys know best where to put things and if you even need them. On the other hand: I would feel "off topic" discussing, for example, Gentoo profiles and useful handling of closed source system libraries (I'm talking Mali here) with Portage on the Armbian Forums since... well... it's not even close to what Armbian works with, so I can dig people trying to get forums running that are not aimed at a specific system. That they will have a hard time working/surviving just because of a lack of "gravity" or a sustainable community with their entire contributions probably-eventually going /dev/null .... totally valid point. What I personally could dig would be a section on these forums specifically targeted at "Not-(exclusively-)Armbian-things". If that is something that makes sense, or you guys would even want.... That's something entirely up to you, of course.
  6. While I don't really see the point in yet another, probably rather sparsely populated forum, I think it's perfectly valid to do so if one wants to. Like you pointed out yourself: This is the Armbian forum. There are people, however, that don't run Armbian, don't want to run Armbian, and might even disagree on certain design choices it makes. That also is perfectly valid, and as long as improvements made are flowing back into Armbian maybe even beneficial. I think it stems from a rather narrow view on things to outright disregard people that want to try and take a different approach. As for my own Kernel repo .... that's pretty much for my very own and private use and for the not at all aimed at the general public Gentoo based rootfs builder I'm working on, mostly for work. If it is not appreciated to let things flow back into Armbian, that's something I can perfectly live happily ever after with.
  7. Dug this up in the 3.2 tree. I'm pretty sure this would also work with 3.4. Didn't test it tho. https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=243f858d7045b710a31c377112578387ead4dde1
  8. Hello, I attempted to port the dirty COW fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619) for 3.4.112, and came up with this: https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/543472582a6adcef12fae4ad11da72a62f29fb74.patch Apparently it solves the issue, but to be sure maybe some of you guys can give it a test. If it checks out please do commit it in the right places for Armbian - which I wouldn't know (Armbian has so many kernel patch folders, I don't wanna mess things up) Regards Sven
  • Create New...