IXUS160/ELPH160 Porting attempt - page 33 - DryOS Development - CHDK Forum

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 173881 Views
Re: IXUS160/ELPH160 Porting attempt
« Reply #320 on: 04 / December / 2015, 11:21:07 »
Advertisements
I also would like to test it, I asume the risks. Could you send me the link?

Thank you and congrats for your work!

*

Online reyalp

  • ******
  • 13438
Re: IXUS160/ELPH160 Porting attempt
« Reply #321 on: 04 / December / 2015, 15:35:06 »
I also would like to test it, I asume the risks. Could you send me the link?
Sent.
Don't forget what the H stands for.

Re: IXUS160/ELPH160 Porting attempt
« Reply #322 on: 12 / December / 2015, 03:47:21 »
Hi, Could you send me the latest CHDK version for canon ixus 160?
thanks so much

*

Online reyalp

  • ******
  • 13438
Re: IXUS160/ELPH160 Porting attempt
« Reply #323 on: 12 / December / 2015, 14:25:39 »
Hi, Could you send me the latest CHDK version for canon ixus 160?
thanks so much
Sent
Don't forget what the H stands for.


*

Offline c_joerg

  • *****
  • 1157
Re: IXUS160/ELPH160 Porting attempt
« Reply #324 on: 12 / December / 2015, 14:48:09 »
Are the hookutil /rawoplib implemented on the IXUS160?
Did somebody try to run rawopint on  the IXUS160?
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Online reyalp

  • ******
  • 13438
Re: IXUS160/ELPH160 Porting attempt
« Reply #325 on: 12 / December / 2015, 15:03:16 »
Are the hookutil /rawoplib implemented on the IXUS160?
This should work, the raw hook is implemented.
Don't forget what the H stands for.

Re: IXUS160/ELPH160 Porting attempt
« Reply #326 on: 13 / December / 2015, 10:22:19 »
hello reyalp!
thanks for your hard job with the ixus160! could you be so nice and send me the latest CHDK version for this camera? thank you!

*

Online reyalp

  • ******
  • 13438
Re: IXUS160/ELPH160 Porting attempt
« Reply #327 on: 13 / December / 2015, 15:09:05 »
hello reyalp!
thanks for your hard job with the ixus160!
To be clear, the hard work was mostly done by adong.
Quote
could you be so nice and send me the latest CHDK version for this camera? thank you!
Sent.

On the future of this port:
I've shared builds with over a dozen people, and heard virtually nothing back from anyone. Presumably that means it's working, or at least that no one else has bricked there camera.

I don't see any practical way to put a visible warning on the build, but at some point it's probably time to say enough is enough and enable it in the auto-build.

Thoughts?

There is still an possible issue with the zebra that needs to be investigated:
http://chdk.setepontos.com/index.php?topic=12321.msg125750#msg125750
Don't forget what the H stands for.


Re: IXUS160/ELPH160 Porting attempt
« Reply #328 on: 13 / December / 2015, 15:42:11 »
I don't see any practical way to put a visible warning on the build, but at some point it's probably time to say enough is enough and enable it in the auto-build.  Thoughts?
Another choice might be to just attach a stable build to a post here with a suitable warning as part of the post.  When the stable version is bumped for a major bug fix, someone just needs to remember to update here.  Not a great solution but it saves you (& others) from having to constantly respond to requests?

Something like :
WARNING : the CHDK port for the ixus160/elph160 posted here is believed to be stable but one camera was "bricked" during the completion of this port.  As with any CHDK port, use with caution as there are no guarantees.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #329 on: 13 / December / 2015, 18:25:56 »
I've shared builds with over a dozen people, and heard virtually nothing back from anyone. Presumably that means it's working, or at least that no one else has bricked there camera.
Same here.
Quote
at some point it's probably time to say enough is enough and enable it in the auto-build.
I agree.
Quote
There is still an possible issue with the zebra that needs to be investigated:
I believe that no framebuffers (= those we're using) have a height over 240 pixels, so the 480 in the source is not correct. (but that's probably not all)

Another choice might be to just attach a stable build to a post here
The firmware update boot can be useful sometimes (I usually use that to make a card bootable). Due to our unwritten rules, we don't publish those files here.

 

Related Topics