Jump to content

SteeMan

Moderators
  • Posts

    1453
  • Joined

  • Last visited

Posts posted by SteeMan

  1. @mcb777 Please note that posting such resources (i.e. the ophub build "amlogic-s9xxx-armbian" above) in this forum can be insulting towards Armbian developers since the developers behind ophub do not participate in the Armbian development effort nor these forums.  In fact they use the Armbian name for their fork without permission.  The concern being that users of these other code bases will turn to these forums for support not knowing the code they are running is not Armbian and burden our already scarce resources. I would ask you not to post such links in the Armbian forums in the future.

  2. Moved post to TV box forum.

    Armbian doesn't support TV Boxes.  See the info on this FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

     

    Also note that this is a new soc by allwinner, and it often takes years for the open source world to support new socs. The h616 soc that came out a couple years ago is still not well supported.  And I suspect that this new soc is a 32bit soc, which means it may never be well supported, as it seems most work these days is focussed on 64bit CPUs.

     

  3. 13 hours ago, Sigma7 said:

    want to virtualize Armbian images created for TV Box

    What exactly do you mean by this?  If you are looking to run the exact image you deploy to a SBC in a virtual environment, you can't really do that.  If you are looking to run an armbian build that has the same linux kernel and user space environment as an SBC/TV Box build, that you should be able to do.  A virtualized environment is really a specific virtualized set of hardware which will be different than the hardware for any specific SBC/TV Box.  So the low level uboot and hardware environment (i.e. dtb files) will be different between the SBC build and the virtual environment build.  But from that level up (kernel and user space) everything can be the same.  Armbian has a build target for the QEMU environment (Virtual QEMU) and automated builds for that here: https://github.com/armbian/community/releases

     

  4. 54 minutes ago, MBB said:

    Currently, our plan was to keep updating our patches (and add other boxes such as the work being done by @jock), but if there is interest in making this a CSC build, I am more than happy to discuss how you'd like us to proceed.  It is certainly our intent to handle all support and not place any burden on Armbian folks.  Is there a good way to discuss in real time?  You can reach me here:  mike at inovato.com.  I am US West Coast.

    @MBB I would recommend that reach out to @Igor via irc or discord for that discussion.

     

  5. On 8/16/2022 at 12:13 AM, MBB said:

    For anyone wanting to build from mainline, we have posted an article with our patches.  These include AC200 Ethernet and XR819 wifi support in kernel 5.15.y.  For edge builds, AC200 Ethernet is supported.  To support the XR819, we'll have to create more patches for the changes in kernel 5.19.  The link is https://www.inovato.com/article/building-armbian.

    @MBB Are you working to get your patches submitted back to base Armbian?  The reason I'm asking is given your current instructions (pull armbian source, apply your zip of patches) you will run into problems over time as the armbian codebase changes, since you aren't tied to a specific git commit or label.  Also long term where do your end users turn for software support?  Armbian certainly isn't setup to provide end user support for projects like this.  Just wondering about how you envision long term support working as it relates to the armbian code you are building on top of.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines