search

UpstreamDataInc / goosebit

A simplistic, opinionated remote update server implementing hawkBit™'s DDI API.
https://goosebit.rtfd.io
Apache License 2.0
12 stars 2 forks source link

Firmware vs Software #74

Closed easybe closed 2 weeks ago

easybe commented 4 weeks ago

Throughout gooseBit the term firmware is used, whereas the Linux counterpart, SWUpdate uses the term software. Another "problem" I see is that in the Linux world firmware is normally what is written/flashed to peripherals or chips on the board.

Would it be an option to use "software" instead?

b-rowan commented 4 weeks ago

Throughout gooseBit the term firmware is used, whereas the Linux counterpart, SWUpdate uses the term software. Another "problem" I see is that in the Linux world firmware is normally what is written/flashed to peripherals or chips on the board.

Would it be an option to use "software" instead?

No opposition, I'm just very used to anything flashed onto an embedded device being called "firmware", but that might be a very niche viewpoint.

easybe commented 4 weeks ago

In the embedded field that is not uncommon. However, technically gooseBit could be used with any system running Linux (with a network connection).

easybe commented 3 weeks ago

OK. So maybe achieve some stability first? Preferably have some tests. Then do a big find & replace?

b-rowan commented 3 weeks ago

OK. So maybe achieve some stability first? Preferably have some tests. Then do a big find & replace?

Sounds good. Are we going to aim for 100% test coverage of the project on this note?

tsagadar commented 2 weeks ago

100% test coverage IMHO rarely makes sense. I'd focus on the DDI parts to have this covered as much as possible - here things could go wrong and in the worst case brick devices (or not detecting, that a new software bricks them).

On the UI side it is annoying to have bugs, but not much harm done.