compatible firmware (CHDK) versions of the same hardware - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: [1] 2 3   Go Down

compatible firmware (CHDK) versions of the same hardware

  • 23 Replies
  • 13265 Views
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
compatible firmware (CHDK) versions of the same hardware
« on: 28 / August / 2008, 09:30:07 »
Advertisements
Hey y'all,

do we have a list of cameras that can use the the same chdk version on different firmwares? i know there are at least two cams. i'm wondering if we should somehow reflect this in the makefiles, so the autobuilds are built like for example:

a620_100e_100f (just an example, really!)

This will help avoid confusion. imo.

thoughts?
Logged
*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #1 on: 28 / August / 2008, 11:43:01 »
On main Wiki page we can see six such models :)
A610 - 1.00d with CHDK version for 1.00e
S2IS - 1.00i with CHDK version for 1.00g
SD700(IXUS800) - 1.01a with CHDK version for 1.01b
SD750(IXUS75) - 1.01b with CHDK version for 1.01a
SD800(IXUS850) - 1.00d with CHDK version for 1.00e
SD1000(IXUS70) - 1.01a with CHDK version for 1.01b
« Last Edit: 28 / August / 2008, 11:46:31 by ewavr »
Logged
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #2 on: 28 / August / 2008, 16:08:05 »
thanks ewavr :)

hm, funny, the ixus75 isnt even in trunk yet. always thought so :D (they seem to have some bugs, but we *could* integrate it anyway, eh?)

ok, so for example i rename the sub dir
s2is\sub\100g to s2is\sub\100g_100i
And also change the top makefiles.
Any sideeffects?
Question for Hacki & Whim: Will this renaming somehow interfere with the autobuild and/or the CHDK Shell? I will wait with the committ until you give me an answer, i don't wanna break anything :)

Logged
*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #3 on: 28 / August / 2008, 18:04:41 »
@PhyrePhox


My first thought: is having a couple of identical directories really that costly, spacewise ? Let's say for ixus70_sd1000
the CHDK versions for 101a and 101b are exchangeable, what would it take to add 101a ?

1) copy /platform/ixus70_sd1000/sub/101b/*.*  --> /platform/ixus70_sd1000/sub/101a/*.*

2) insert:
   $(MAKE) -s --no-print-directory PLATFORM=ixus70_sd1000   PLATFORMSUB=101a NO_INC_BUILD=1 firzipsub
and
   $(MAKE) -s --no-print-directory PLATFORM=ixus70_sd1000   PLATFORMSUB=101a NO_INC_BUILD=1 firzipsubcomplete
and
   $(MAKE) -s --no-print-directory PLATFORM=ixus70_sd1000   PLATFORMSUB=101b NO_INC_BUILD=1 clean

to the root Makefile

3) Done, filespace cost ~ 40 -70 kB (according to filesystem/cluster size) per firmware version, so from ewavr's info
    less than 300-500 kB for the lot.


If filespace is he reason for this suggestion, how about:

hardlinks (Hard link - Wikipedia, the free encyclopedia) ,
symbolic links (Symbolic link - Wikipedia, the free encyclopedia)
or aliases (http://en.wikipedia.org/wiki/Aliasing_(computing))

If it was implemented as you suggest I don't think it would break any functionality in CHDK-Shell,
but it would wreak some havoc in the GUI (firmware selection boxes)
I'd probably build in a filter to create the 2 identical subdirs after unpacking anyway...

I'll think about it some more, but as you can tell my vote goes to total symmetry for all firmwares, I think that
it's part of the beauty of the CHDK source tree (why would a firm that happens to be almost identical to it's
cousin have less right to it's measly 50 kB than 1 that is substantially different ?)

later,

wim



« Last Edit: 28 / August / 2008, 19:06:12 by whim »
Logged
*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #4 on: 28 / August / 2008, 19:01:15 »
Quote from: whim on 28 / August / 2008, 18:04:41
1) copy /platform/ixus70_sd1000/sub/101b/*.*  --> /platform/ixus70_sd1000/sub/101b/*.*

And then modify both 101a and 101b if necessary? Not too good idea, IMHO...
Another idea: in /platform/ixus70_sd1000/sub/101a/ all files must contain only one line, like:

#include "../101b/name_of_this_file"
Logged
*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #5 on: 28 / August / 2008, 19:39:04 »
no need to modify, just recopy ...

but: your solution is much more elegant, and saves space  :)

when i talked about symmetry, i was mostly referring to the directory structure anyway.


wim
Logged
*

Offline dzsemx

  • ****
  • 302
  • [SX40HS][A650][A630]
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #6 on: 29 / August / 2008, 01:02:14 »
Quote
#include "../101b/name_of_this_file"
nice solution ;)
Logged
*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #7 on: 29 / August / 2008, 04:19:54 »
Couldn't it be easier to change only the makefile to generate an additional zip file with the "new" fw version number in the filename for these identical builds ?
Logged
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #8 on: 29 / August / 2008, 04:32:01 »
this would also be a possible solution. just tell me how and i'll do it ;)
Logged
*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: compatible firmware (CHDK) versions of the same hardware
« Reply #9 on: 29 / August / 2008, 08:39:19 »
@ewavr
Played around a bit cloning  101a out of 101b for ixus70 with your method, but this caused
trouble with 'Makefile' and 'makefile.inc' - even after adapting the include syntax.
Ended up copying them to get it to work

Quote from: fe50 on 29 / August / 2008, 04:19:54
Couldn't it be easier to change only the makefile to generate an additional zip file with the "new" fw version number in the filename for these identical builds ?

Wouldn't the splash screen then display the 'parent' FW version in the build name ?

wim
« Last Edit: 29 / August / 2008, 08:45:03 by whim »
Logged
Pages: [1] 2 3   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal