Igor
-
Posts
14497 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Igor
-
Giving us more work is pointless as we are years behind. Scope of desired changes from users side exceeds developers capacity for quite a lot. This is all what we can do in order to start moving this project (improving this application in all aspects, including UX) forward:
-
Make lowest download speed limit configurable
Igor replied to atone's topic in Framework and userspace feature requests
This download function certainly needs to be addressed in some way. On a side note - with upgrading to NEXT, all external compilers are go away. We would like to keep those things in Jira (invite was sent to your email, feel free to tackle/improve info on any other issue) -
Doesn't boot with 3A images?
-
Event -> Video (with transcripts and comments) 1. Merging NEXT (updated slides) We discussed progress made in past week (Jira Epic) and set limited expectations for following week due to holidays season. We will try to enable rootfs caching CI at first (which has to be compatible with master) and Docker image creation next (which probably isn't?) 2. Unifying boot process Most single board computers needs good overlay handling so moving them to complete generic image is likely / in short term not possible. We still can not count on DTBless or DT from u-boot only, well support from vendor SPI. If we want to move like everything to UEFI and keep things operation / loose no feature, its a lot of work. Sorting out u-boots and going extlinux way with support for multiple kernels (NEXT/CURRENT) might be the best mid-way. 3. When 6.2 and 6.1, current / edge Keeping and stabilising 6.1 at EDGE for few months, waiting that it will be tagged as LTS for sure. Keeping new things like 3588 / 3568 at their own kernel branches, CURRENT = 6.1, EDGE = 6.2 (at once) @rpardini @JetHomeDid I forget to mention something important?
-
This weeks meeting topics: Merging NEXT Unifying boot process When 6.2 and 6.1, current / edge General goal of weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers.
-
Recording
-
Event | Recording This weeks meeting topics: Merging of next generation build framework Primary goal is to understand benefits it is bringing as we all will need to sacrifice some time in order to review it, then merge and fix remaining bug. Despite our current system produces images, we have many bugs and dirty workarounds that this upgrade is addressing. The future of rockchip64 family Main goal is to make it maintainable again. GitHub development and review process Main goal is to motivate people to take more responsibility for reviewing and merging. Define clear rules. Conclusions: Everyone interested should watch a recording (~1h) and place a comment below. Comments will be discussed here and / or at next meeting. Before we can do anything in real regarding merging NEXT, we need to clean patches but also address several things, starting with those: Making a tool / module for patch generation (@rpardini) Preparing guidelines for review and contribution (@giddy) Move repo management from the build system (@igor) How to help? Cleaning the patches! (helper is here) armbian-next_-_meeting_21.dec.2022.pdf
-
Coordinating development of armbian-config refactoring: https://github.com/armbian/configng @joekhoobyar
-
Donations are very rare so I am happy, but they don't give you any service. This is your free willing contribution to cover small % of things that we already fixed for you. Remember that you are not paying for software in any way. If you want that research is done you need to become at least a gold partner. For your 5$ I can't hire anyone to look into your problem. Especially not myself. Welcome to the custom hardware world. Trick that works with Allwinner devices, doesn't work with Amlogic ... just wait, perhaps someone knows, I don't.
-
Workaround? yes (armbian-config, alternative kernels, choose previous one - 5.10.something), fix? With this, there is nothing we can do but wait like you that Hardkernel fix it.
-
Current only working software for this HW is very old stuff anyway Vendors objectives are different than ours. They want to sell hardware and they want to have control over software. By doing on their own, they control it and they don't help their competitors. It this aspect it makes sense. But yes, I totally agree. Research has been done on the topic, we know many pros and cons and I think we do agree to some point. https://forum.armbian.com/topic/20847-the-boot-process-and-various-devices/ A good topic to discuss it next week - how to proceed from current stage? @ManoftheSea Too early? If preparation and transition is not done well, we also have a lottery. It is nice that you experiment with all this, I know others also did some. We found some issues and we need to make some decisions ...
-
Not saying its good idea. This is all what was possible back then. Odoroids are still on boot.ini which is textual interpretation of boot.scr ... I agree that some old junk has to be remove. But this has to be done together and systematically or we made one step forward, two back. Upgrades / downgrades has to work. Install tools has to work. Build tools has to work and everything has to be checked twice. And again - what do we sacrifice?
-
Aha, that I haven't try. So we would need to change priorities in the boot script or proceeding into some other method?
-
I have successfully installed to SPI / NVME from official Armbian builds. Without any hacks, regular armbian-install.
-
Keeping kernel bootsplash is getting out of control ... it was disabled while we anyway moved to plymouth. Check here: https://github.com/armbian/build/pulls?q=is%3Apr+plymouth+
-
Armbian automated testings shows no problems with WiFi https://paste.armbian.com/yaqokonipe But this image is little further then released, made from latest sources (nightly). You can switch to the same firmware via armbian-config.
-
script Fail to recognize armbian root and on boot Bullseye CLI Nov 30, 2022
Igor replied to SoSie's topic in Banana Pi M5
Use different SD card. Standard Amlogic issue. It can't init SD card properly. Try test images if they are better ... fix coming soon. Hopefully. -
I expect we will shuffle this time around a bit in the future or even split into two teams.
-
And we don't have needed capacity as you and vendor are exploiting community software development. What we do is very hard work which needs to be compensated. Support is hard work which needs to be compensated. Those who tells you otherwise are either stealing value from someone (open source piracy is also adding to the bill) / lying or is just a Dunning–Kruger enhanced newbie. Its not all dark. Instead of waiting, perhaps you can check how you can help? Serving project as a coordinator? Evangelist? Graphics designer? Ordinary soldier? Project needs many positions and hard cash just to cover basic needs. Since we are non-profit, we can't enhance our capacity ... Why do you expect we have to give you software for free and keep investing our private money so you will get more free stuff? Welcome and thank you!
-
Armbian is more advanced then Rpi OS. It resizes SD card automatic on 1st boot.
-
This is community forum, welcome! If you want to contact team, check here. But without becoming a partner nobody will be doing any research for you. In custom hardware, team doesn't know to answer without a research.
-
Of course. 1. Research which driver is needed, enable it or bring a tested code as external kernel driver. Make a PR to the code and make sure to stick around since it will need maintaining. 2. Hire someone to do that for you and support him to do the maintaining work for you. Its not much of work, but right enough that you need someone. 3. Support Armbian developers to do that for you.
-
This weeks meeting topics: Merging of next generation build framework Primary goal is to understand benefits it is bringing as we all will need to sacrifice some time in order to review it, then merge and fix remaining bug. Despite our current system produces images, we have many bugs and dirty workarounds that this upgrade is addressing. The future of rockchip64 family Main goal is to make it maintainable again. GitHub development and review process Main goal is to motivate people to take more responsibility for reviewing and merging. Define clear rules. Goal of the weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting Conclusions: Everyone interested should watch a recording (~1h) and place a comment below. Comments will be discussed here or at next meeting. Before we can do anything in real regarding merging NEXT, we need to clean patches but also address several things, starting with those: Making a tool / module for patch generation (@rpardini) Preparing guidelines for review and contribution (@giddy) Move repo management from the build system (@igor) How can anyone help? Cleaning the patches! The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. armbian-next_-_meeting_21.dec.2022.pdf
-
Those are developers preview builds, where you can check what works and at some point it will be good enough for some uses cases. In a couple of years, it will be functional on the level of kernel 5.10.y. Download is possible from CI pipeline: https://github.com/armbian/build/releases Boot log: This board is looking for maintainer(s) and (this) forum moderator (contact @Werner).
-
https://www.armbian.com/radxa-zero2/
