EOS M3 porting - page 22 - DryOS Development - CHDK Forum

EOS M3 porting

  • 696 Replies
  • 301576 Views
Re: EOS M3 porting
« Reply #210 on: 03 / December / 2016, 16:44:51 »
Advertisements
I wonder if different buffer addresses could be the reason for g7x and sx60hs crashes in hybrid auto mode?
@reyalp

*

Online reyalp

  • ******
  • 13450
Re: EOS M3 porting
« Reply #211 on: 03 / December / 2016, 17:44:00 »
I wonder if different buffer addresses could be the reason for g7x and sx60hs crashes in hybrid auto mode?
@reyalp
This can't explain the G7X crash in hybrid auto when loading with firm update, because the crash happens when CHDK DNG is not enabled. CHDK only uses the address if raw is enabled, or your are using a script function like shot_histogram or rawops that accesses the raw buffer, and is only likely to crash if it modifies the buffer (DNG for byte reversing + badpixel, or rawop write)
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4426
Re: EOS M3 porting
« Reply #212 on: 03 / December / 2016, 18:32:55 »
I have mixed feelings about disabling the battery warning completely. It might make some important people angry (I'm not talking about CHDK users). Does ML do anything like that?

*

Online reyalp

  • ******
  • 13450
Re: EOS M3 porting
« Reply #213 on: 03 / December / 2016, 18:54:49 »
I have mixed feelings about disabling the battery warning completely. It might make some important people angry (I'm not talking about CHDK users). Does ML do anything like that?
I'm definitely hesitant to include this, FWIW.
Don't forget what the H stands for.


*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #214 on: 04 / December / 2016, 02:14:11 »
Does ML do anything like that?
Is RAW video recording "like that"?
There is also another way(not software) to disable the battery warning, but it's less safe.
But if CHDK comunity is afraid, I can remove this feature.

It's interesting that camera is collecting information about batteries usage(G7X too) and maybe sends it to somewhere...
« Last Edit: 04 / December / 2016, 06:21:53 by Ant »

*

Online reyalp

  • ******
  • 13450
Re: EOS M3 porting
« Reply #215 on: 04 / December / 2016, 16:21:29 »
Does ML do anything like that?
Is RAW video recording "like that"?
IMO, no.

My feeling is that it is different raw video or other features the CHDK and ML add. In general someone who was going to buy a full professional video rig isn't going to suddenly be satisfied with a mid-range DSLR because of ML. There's probably a few exceptions, but I would expect them to a small fraction of an already small user base.

The difference with the battery check is that Canon implemented it specifically to discourage the use of 3rd party batteries. I'm not fond of this kind of accessory lock-in, but bypassing it would move CHDK from a hobby project which generally encourages people to buy Canon hardware to something that encourages people to buy hardware that Canon is actively trying to stop people from using.

It is also possible that this check isn't purely motivated by copy protection. 3rd party batteries are notorious for doing things like replacing the thermistors with resistors, and otherwise ignoring best-practice engineering. If the firmware pushes "genuine" batteries to the limit assuming a particular design, it might have undesirable side effects when it does the same on a cheap clone.
Quote
It's interesting that camera is collecting information about batteries usage(G7X too) and maybe sends it to somewhere...
This would certainly be something interesting to investigate.

Also to be clear, my reluctance to is to including this hack as a standard feature in the official CHDK SVN. It's not for me to tell anyone what they should research or discuss.
Don't forget what the H stands for.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #216 on: 04 / December / 2016, 18:00:34 »
It is also possible that this check isn't purely motivated by copy protection. 3rd party batteries are notorious for doing things like replacing the thermistors with resistors, and otherwise ignoring best-practice engineering.

You are talking like Canon's employee.  :)
Considering the price of genuine batteries, I think, it's worst-practice marketing(like Apple).

Quote
If the firmware pushes "genuine" batteries to the limit assuming a particular design, it might have undesirable side effects when it does the same on a cheap clone.
I understand that the company wants to protect themselves from undesirable consequences, but one time warning is enough.

Why CHDK don't show warnings at first(every) startup?
« Last Edit: 04 / December / 2016, 18:05:51 by Ant »

Re: EOS M3 porting
« Reply #217 on: 04 / December / 2016, 18:23:48 »
It is also possible that this check isn't purely motivated by copy protection. 3rd party batteries are notorious for doing things like replacing the thermistors with resistors, and otherwise ignoring best-practice engineering.

You are talking like Canon's employee.  :)
Considering the price of genuine batteries, I think, it's worst-practice marketing(like Apple).
I own nine different Powershots - six of which use Canon proprietary batteries (i.e. not standard AA cells).  I have one genuine Canon battery for each and many low cost 3rd party batteries as well.   

All the Canon batteries still function properly, although the oldest have somewhat diminished capacity of course.  Of the 3rd party batteries (i have several per camera and many different "brands") more than half have swollen up enough that they don't fit into their camera very well, and about 20% will no longer charge.

No Canon employee or marketing here.  Simple facts.

(btw - for the little I paid for the 3rd party brands,  I just treat them as "semi-disposable" batteries).
Ported :   A1200    SD940   G10    Powershot N    G16


*

Online reyalp

  • ******
  • 13450
Re: EOS M3 porting
« Reply #218 on: 04 / December / 2016, 19:19:00 »
You are talking like Canon's employee.  :)
Considering the price of genuine batteries, I think, it's worst-practice marketing(like Apple).
I agree that they are probably doing it to boost their profits on accessories. However, it is a well documented fact that many of the cheap clones are not as well engineered as the official ones.

The trend in battery tech is to squeeze out more performance by using more sophisticated electronics to run things closer to the edge (*cough* samsung), so IMO it's not entirely out of the question that there were factors other than greed involved.

This is all speculation though, and mostly irrelevant to the question of whether bypassing the check risks pissing Canon off.
Quote
I understand that the company wants to protect themselves from undesirable consequences, but one time warning is enough.
That would certainly be my preference, but Canon didn't ask me.
Don't forget what the H stands for.

Re: EOS M3 porting
« Reply #219 on: 04 / December / 2016, 20:30:22 »
Perhaps it would be possible to include a script to disable battery compatibility checks or set them however the user likes.  Does chdk support the idea of a script executed at startup like a users profile?

 

Related Topics