camera_list.csv (was Re: G7X II - need help finding led details.) - General Discussion and Assistance - CHDK Forum

camera_list.csv (was Re: G7X II - need help finding led details.)

  • 16 Replies
  • 349 Views
Advertisements
I noticed g7x2 is in trunk. I believe an update to camera_list.csv is in order...
Author of CHIMP, Canon Hack Installation and Management Platform

Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #1 on: 28 / August / 2019, 08:25:19 »
I believe this line is missing from camera_list.csv:
Quote
g7x2,101a,PREALPHA,,SKIP_AUTOBUILD
Author of CHIMP, Canon Hack Installation and Management Platform

*

Offline reyalp

  • ******
  • 12153
Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #2 on: 28 / August / 2019, 12:17:19 »
I believe this line is missing from camera_list.csv:
Quote
g7x2,101a,PREALPHA,,SKIP_AUTOBUILD
It's not really a port at this point, just some early test code that blinks an LED.
Don't forget what the H stands for.

Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #3 on: 29 / August / 2019, 05:09:29 »
Now, I'm confused. Shouldn't camera_list.csv reflect the platform/ directory structure?
Author of CHIMP, Canon Hack Installation and Management Platform


Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #4 on: 29 / August / 2019, 09:31:42 »
Shouldn't camera_list.csv reflect the platform/ directory structure?
Why would it?  Right now, early work on ports can be shared and archived in the svn repository with no requirement that they actually build or work?  The ports in camera_list.csv are the ones that the autobuild uses to build released versions ( alpha, beta, stable).

Edit :  I suppose an argument could be made for the use of SKIP_AUTOBUILD in the camera_list.csv file ...
 
« Last Edit: 29 / August / 2019, 09:36:25 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12153
Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #5 on: 29 / August / 2019, 12:57:57 »
Edit :  I suppose an argument could be made for the use of SKIP_AUTOBUILD in the camera_list.csv file ...
That would put it in the batch operations that use -noskip. The main one is batch stubs builds, which would be fine including the partial G7X II code.

Doesn't matter to me one way or the other.

Now, I'm confused. Shouldn't camera_list.csv reflect the platform/ directory structure?
It defines how the batch builds are done. Does this matter to you for some reason, or are you just pointing out a possible mistake?
Don't forget what the H stands for.

Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #6 on: 29 / August / 2019, 14:30:45 »
It defines how the batch builds are done. Does this matter to you for some reason, or are you just pointing out a possible mistake?

Any inconsistency between the source tree and camera_list.csv causes the CHIMP camera metadata generator tool to fail.

Edit: I just noticed that the Wifi button is called "WiFi" in g7x2 (as well as in sx700hs, sx60hs, g5x), whereas it's "Wifi" in g7x (and in six others). In addition, s95 has a "Play" button (should be "Playback").
Edit 2: There are also "VIDEO" and "Disp"... starting to look like a lost battle.
« Last Edit: 29 / August / 2019, 14:56:19 by dmitrys »
Author of CHIMP, Canon Hack Installation and Management Platform

Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #7 on: 29 / August / 2019, 15:30:25 »
Full list:

a1200DispDisplay
a2200DispDisplay
a3100DispDisplay
a3200DispDisplay
a3300DispDisplay
d20VIDEOVideo
g10DispDisplay
g11DispDisplay
g12DispDisplay
g16ShortcutShrtcut
g5xWiFiWifi
g7x2WiFiWifi
s95PlayPlayback
s95DispDisplay
sx170isDispDisplay
sx400isDispDisplay
sx410isDispDisplay
sx510hsDispDisplay
sx60hsWiFiWifi
sx700hsWiFiWifi
Author of CHIMP, Canon Hack Installation and Management Platform


*

Offline srsa_4c

  • ******
  • 4031
Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #8 on: 29 / August / 2019, 16:24:55 »
@reyalp
I guess this needs to be moved to a separate thread.
Any inconsistency between the source tree and camera_list.csv causes the CHIMP camera metadata generator tool to fail.
Sounds like you need to fix your tool then. The CHDK batch (build) operations are working, and they are parsing the csv. It is even possible to make a custom csv (a small subset of the original) and the batch will continue to work just fine.

Re: camera_list.csv (was Re: G7X II - need help finding led details.)
« Reply #9 on: 29 / August / 2019, 16:48:26 »
Any inconsistency between the source tree and camera_list.csv causes the CHIMP camera metadata generator tool to fail.
Sounds like you need to fix your tool then. The CHDK batch (build) operations are working, and they are parsing the csv.
The tool was specifically designed to fail in such a case, so there's nothing to *fix* there. I suppose I could change it to produce a warning and proceed, although IMHO adding a LED test to trunk wasn't such a great idea.
Author of CHIMP, Canon Hack Installation and Management Platform