SX280 / 275 / 270 porting - page 37 - DryOS Development - CHDK Forum

SX280 / 275 / 270 porting

  • 365 Replies
  • 197638 Views
*

Offline srsa_4c

  • ******
  • 4442
Re: SX280 / 275 / 270 porting
« Reply #360 on: 18 / April / 2021, 14:01:25 »
Advertisements
I tested the SX280 today with the latest stable German CHDK build, CHDK_DE_sx280hs-102b-1.5.1-5835. I thought this included commit 5816 with the GPS data in the DNGs, but the DNGs still don't have the GPS data while the corresponding JPGs have them. Do I have to wait for a later build for this to work?
At the moment, the changes are only present in the "unstable" development version (1.6). I'll consider backporting the DNG fix.

edit:
I added the DNG fix to the 1.5 branch in r5841.
« Last Edit: 18 / April / 2021, 14:22:06 by srsa_4c »

*

Offline Vydra

  • *
  • 10
Re: SX280 / 275 / 270 porting
« Reply #361 on: 18 / April / 2021, 16:00:22 »
At the moment, the changes are only present in the "unstable" development version (1.6). I'll consider backporting the DNG fix.

edit:
I added the DNG fix to the 1.5 branch in r5841.

I see. Thank you for the backport, I guess that'll land in a 1.5.1 build in a month or so.

Will the other addition (new URL for AGPS) eventually be added to the 1.5 branch as well, or do I have to switch to the 1.6 branch for that? Looking around a bit I saw that the 1.5 branch took about 5 years to become the stable branch at the end of 2020. I didn't really want to run the "unstable" version, but as it might take 1.6 several years to become the stable branch, I'll consider it. How unstable is the "unstable" branch actually? Can I expect frequent crashes or malfunctions? Sorry for all those basic questions, but I'm still rather new to CHDK.

*

Offline reyalp

  • ******
  • 13664
Re: SX280 / 275 / 270 porting
« Reply #362 on: 18 / April / 2021, 16:07:28 »
I see. Thank you for the backport, I guess that'll land in a 1.5.1 build in a month or so.
No, the autobuild should update within an hour of a commit or so.

Quote
I didn't really want to run the "unstable" version, but as it might take 1.6 several years to become the stable branch, I'll consider it. How unstable is the "unstable" branch actually? Can I expect frequent crashes or malfunctions? Sorry for all those basic questions, but I'm still rather new to CHDK.
At the moment, there is very little in the 1.6 branch that is different from 1.5, so current 1.6 builds should be pretty much as stable / safe (or otherwise) as 1.5.

I would probably not favor backporting the URL override.
Don't forget what the H stands for.

*

Offline Vydra

  • *
  • 10
Re: SX280 / 275 / 270 porting
« Reply #363 on: 19 / April / 2021, 13:57:44 »
No, the autobuild should update within an hour of a commit or so.


Oh, very nice. For some reason I thought this was updated once a month, but obviously I got that wrong.

Quote
At the moment, there is very little in the 1.6 branch that is different from 1.5, so current 1.6 builds should be pretty much as stable / safe (or otherwise) as 1.5.

Thank you, that is a statement I appreciate. I'll try the 1.6 branch then.


*

Offline Caefix

  • *****
  • 828
  • Sorry, busy deleting test shots...
Re: SX280 / 275 / 270 porting
« Reply #364 on: 14 / January / 2022, 16:27:35 »
Researched for another context ...  :-[
Code: [Select]
int vid_get_viewport_fullscreen_height()        { return camera_screen.height; } // may not be always ok
int vid_get_viewport_buffer_width_proper()      { return camera_screen.buffer_width; } // may not be always ok
int vid_get_viewport_byte_width()               { return camera_screen.buffer_width * 2; } // may not be always ok
replaced the // ***  Viewport buffer handling *** block with G16 lines, still missing upper border in (not vga) video. (seems only "issue".) Found missing lines at Sx710, now looks all right...
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 4442
Re: SX280 / 275 / 270 porting
« Reply #365 on: 15 / January / 2022, 16:24:31 »
Researched for another context ...  :-[
Code: [Select]
int vid_get_viewport_fullscreen_height()        { return camera_screen.height; } // may not be always ok
int vid_get_viewport_buffer_width_proper()      { return camera_screen.buffer_width; } // may not be always ok
int vid_get_viewport_byte_width()               { return camera_screen.buffer_width * 2; } // may not be always ok
replaced the // ***  Viewport buffer handling *** block with G16 lines, still missing upper border in (not vga) video. (seems only "issue".) Found missing lines at Sx710, now looks all right...
I extracted the real changes and committed the viewport offset stuff in r6049.
If you really want your work to reach the official source, I'd suggest taking the time to make a _patch_ with minimal noise (avoid changing unrelated code and comments). When you publish a patch, please describe what your changes are supposed to fix. Files, code snippets and patches posted in various threads will likely get forgotten. Once you made a proper patch with description, post it in the request thread.

 

Related Topics