Build current and edge releases on Odroid C1

[juanlufont]

Not sure if there is any link between the DietPi and Armbian building process, but the current DietPi Bookworm image for Odroid C1(+) is working fine, including

• reboot
• HDMI output (I have not tested X11, not sure if it is even possible)
• USB support (I did not check hotplug, but it was a HUGE improvement over previous releases)

 

[Igor]

1 hour ago, juanlufont said:

Not sure if there is any link between the DietPi and Armbian building process

 

Dietpi is group of people (one scripting guy and two support for forums) that download images and resell under different name. There is no build process of Dietpi, there is no development. Its mainly repacking / sales of our & others work for their gain. Dietpi is a group that in 10 years of existence managed to return less then 5 fixes they found (every line is a fix of something. This is just a work into common code for past 3 months). 

 

They never contributed in common efforts, they never return anything to people they are taking from, from us and from you. We are not alone, but hey, they compete with us, they say Debian and our work is trash, while they use numbers manipulation (kilobytes of packages on images, processes at start and similar BS) to support selling their scam. Its a shame that such projects are held accountable and being compared. We don't compare with them, but here you can see some insight https://docs.armbian.com/#key-advantages (dietpi is one of armbian downstream projects)

If our image doesn't work and theirs works, is certainly a work of randomness. How they made their image? They developed a bash script, that they use to convert / rebrand any Debian based image into Dietpi. In this process it is impossible to improve what is already broken. That is hard work, and they never did any of it. Since kernel updates are directly linked to, a copy of our packages, they are not bringing any changes ...

 

Images are untested, but I am sure it can't be worse then a copycat:
https://www.armbian.com/odroidc1/

 

Quote

but it was a HUGE improvement over previous releases

Thank you. Dietpi did little to nothing. Not here and not with other devices they "support".

[juanlufont]

🤷‍♂️

 

I know nothing about any feud or bad blood between the projects, thanks for all the background. I have no part in it and my message was not intended to laud anyone, just confirming the state of things with their latest image. Whatever DietPi packaged recently, it works. Which probably means that newer kernels have better support for Odroid C1.

 

 

[Igor]

36 minutes ago, juanlufont said:

bad blood between the projects

Point of community open source development is sharing the load between projects.
 

They choose a policy to steal from open source developers. This wording can be used when they contribute nothing to commons, nothing what they do can anyone reuse. Which is a big steal in custom arm hardware world, where kernel maintenance is everything, not unlike PC world, where distros mainly represent and artistic added value. We have to loose thousands of hours to get a device up, they run a script "and support it". This type of scam only exists in open source world, as nothing is hidden. Just a moral standards or absence of them prevents people to play bad.

All our code is open and anyone can do whatever ... and there is little we can do about except informing you what is their MO. And telling you this is not something we would like to do. We would rather code, do fun stuff, cooperate, share our burdens. As sharing burden is must have in community development. The more value we generate, the better OS we make, the more they profit. By telling users how cheap hard work is, they are damaging interests and motivation of all open source developers that contribute to common efforts. Not just to Armbian. They count that you don't understand this perspective, they don't care and you will anyway forget about on day. If you invest little to nothing, little you can loose. If one have no R&D costs, if you don't maintain any infrastructure, ... Sales of somebody else work = tl;dr; diet-pi. On top of that, they were trying to offload their users complains to us. This only tells what is the level of corruption. Again you don't care who deals with the frustration you have ... Let everything hard and time consuming be pinned to the Armbian is their MO. Since ever. How one can accept such sick play?

 

36 minutes ago, juanlufont said:

I know nothing about

I am sure you don't. For end users its always the same - its free stuff. And you don't care who developed it or who maintains it / keep it operational.

 

Its complicated to understand how Linux support for such a complex world is made. Certainly not as simple as they think and sale.

 

48 minutes ago, juanlufont said:

Which probably means that newer kernels have better support for Odroid C1.

Probably, but that has nothing to do with them. All the work (on top of mainline) is inside those folders: https://github.com/armbian/build/tree/main/patch/kernel/archive 

[torz77]

@Igor

Quote

Interested perhaps in becoming official maintainer?

I wish I could, however, sadly between my other Open Source commitments and trying to earn a living, I do not have the time. If this ever changes in future, though, I'll be sure to let you know.

 

Ultimately, I guess the point of my original post is that Armbian on the Odroid C1+ is currently in a good state, so great work Armbian devs! Your work is appreciated.

Edited December 2 by torz77

[Igor]

2 hours ago, torz77 said:

I wish I could, however, sadly between my other Open Source commitments and trying to earn a living, I do not have the time.

 

I think those are our common defaults
 

2 hours ago, torz77 said:

Odroid C1+ is currently in a good state

 

We made maintaining process as simple as possible. Build system takes care of most problems already and there is even automation that prepare images for release, and once those are confirmed in good shape - USB, HDMI, .... https://docs.armbian.com/Process_CI/#prepare-standard-support-images-for-release with report similar as here https://www.armbian.com/tinkerboard/ few times per year ... that's about it. Leave your contacts https://www.armbian.com/maintainer-registry/ so we can try to contact you prior to release. if you don't have time, not a problem, perhaps someone else will cover, all this work can only be at best effort principle. Board is simply taken down from supported if status is unknown. Goal is to provide best images that build system throws out - current or edge kernel. 

 

2 hours ago, torz77 said:

and trying to earn a living

 

Small jobs always comes around and inner circle is first to know that, so its good to be around, even with this tiny role, small obligations.

[Javelin]

I've submitted fixes to DietPi for certain boards because it seems once they become unsupported here they no longer receive bug fixes.

 

I know the lead guy (Michealng) has made attempts to share patches. Is there a particular process for submitting patches for Armbian?

[SteeMan]

2 hours ago, Javelin said:

Is there a particular process for submitting patches for Armbian?

https://docs.armbian.com/Process_Contribute

[Igor]

5 hours ago, Javelin said:

because it seems once they become unsupported

 

He supports "everyting", while a team of 50 people, is unable. Who do you think is cheating here?

https://docs.armbian.com/#comparison

 

This is how he supports it: He download everything that is valuable from us https://docs.armbian.com/Release_Changelog/#v24111-2024-11-281000 while fixes that somehow finds the way there, they never gets here. Talking about years of work, not this particular fix.

 

We take support serious as we can't steal the bulk of work from someone to mitigate all sorts of troubles related to hard work (burnout, lack of food, etc.), while when you just for fun sale someone else work, this is not a problem.

 

https://docs.armbian.com/User-Guide_Board-Support-Rules/ A small team can only support few boards, the rest is "community supported". By you. Or by nobody.

 

tl;dr; If you add a fix to Armbian, he gets it, we get it. If you sent a fix to him, we don't get it.

 

5 hours ago, Javelin said:

become unsupported here they no longer receive bug fixes.

Image for Odroid C1 is identical to ours with your fix. He doesn't add any fixes to it, besides what you provided. But its "supported" by dietpi  Actually all important fixes in this platform was done by us https://github.com/armbian/build/commits/main/patch/kernel/archive/meson-6.1 which means we provide bug fixes even we don't declare hardware as supported.

 

All fixes that gets to Armbian are integrated at once and update is auto generated within few hours, images once per week.

https://github.com/armbian/community

This is exactly the same support level as other distros, including Dietpi.

[Javelin]

21 minutes ago, Igor said:

tl;dr; If you add a fix to Armbian, he gets it, we get it. If you sent a fix to him, we don't get it.

 

There must be some level of confusion because I did submit a fix for the C4/HC4 reboot problems that had been reported for years. I probably should have sent it directly to you.

[Igor]

3 minutes ago, Javelin said:

There must be some level of confusion because I did submit a fix for the C4/HC4 reboot problems that had been reported for years. I probably should have sent it directly to you.

Many bugs remain unresolved for years and we, by any means, are unable to have complete bug-fix overview in such a complex world.

 

We can only try to keep some tracking:

https://armbian.atlassian.net/jira/software/c/projects/AR/boards/1/backlog 

https://github.com/armbian/build/issues

and resolve when possible.

[Javelin]

Thanks.

Edited December 9 by Javelin

[Tomasz Grzegurzko]

Thanks to torz77, I just resurrected my odroidc1 with the Debian image (which is more than good enough for me!). Thank you!!