• Content Count

  • Joined

  • Last visited

About dhewg

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Okay, you're not even listening or trying to understand, maybe you don't want to. I don't even know WHY there's a need to argue. You're even arguing AGAINST mainline, which I consider harmful to the linux community. I'm done wasting my time on this nonsense. To anyone still willing to test: Results are very much welcome, but please post on the linked github PR, I'm out of here. Feel free to lock this derailed fail thread.
  2. You seriously must be trolling, but I'll bite: As response to my call for testers for mainline builds, you talk about "common good", "investing", "waste money" and "technically pointless problems". Honestly, what are you even talking about? Because you have a "working solution" you want me "to leave you out of this"? You seem to miss how the whole linux economy works. It works by contributing to mainline, not by sticking to buggy and unsupported vendor forks. That's how the stack improves and all users gain from it. Nobody asked you or armbian as a project for anything. There's no
  3. Right. No wait, WHAT? Anyway, if you honestly don't see the advantages of what I'm trying to archive here... just ignore it? I'm sure there're owners of this board who'd welcome a mainline firmware.
  4. I'm not sure I understand you correctly. But I didn't ask for armbian to change or support anything. This is about testing and improving a firmware based on mainline components. That helps every distro, no matter if armbian, debian, openwrt or whatever. In the end I believe we can get a more recent bootloader with many bugs fixed. And when that happens armbian can decide if or when it wants to switch from the downstream forks to mainline. So as far as I'm concerned this is distro independent and the more people chime in the better the result, so I'm confused by the distro-X-vs-Y
  5. New patches for mainline u-boot have been posted, so that espressobin should finally work now. That gives us a recent version of u-boot, compared to that old and unmaintained marvell fork. I opened a PR for OpenWRT to ship mainline u-boot/atf builds. Those also include distro boot: openwrt/openwrt#3360 And now we need testers openwrt/openwrt#3360 (comment) While this is a PR for OpenWRT, I boot vanilla debian with it. In the end the distro shouldn't matter Note: * All builds are currently CPU_800_DDR_800 only for stability reasons
  6. Sorry, I meant generic boot scripts. Now you don't have to generate FIT image, u-boot is able to load raw compressed initrd's and its trying all available boot devices (mmc1, mmc0, usb, scsi, pxe, dhcp). See http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro
  7. Realizing it's not that easy, I implemented the missing pieces for the generic distro concept. They'll be part of an upcoming release (mainline as well as marvell's). Bottom line: one can now use boot.scr to load raw kernel/initrd as with many other platforms. It works fine with plain debian and it's flash-kernel. I guess armbian could make use of it too: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/tree/u-boot-2017.03-armada-17.10
  8. Hi there, the bootloader binaries hosted here: https://dl.armbian.com/espressobin/u-boot/ Could you please enable CONFIG_DISTRO_DEFAULTS? Thanks