The first version will have audio meters, lens data and maybe manual
audio gain plus monitoring on the A/V jack. I haven't found the
video ram device yet (vram_get_number() returns -1 on all devices),
so zebra stripes and histograms won't work for a little while.
There might also not be a menuing system initially since there are
no "spare" buttons on the 550D in movie mode and we still do not
have a way to integrate with Canon's menus.
The initial testing version will be available to those brave enough
to test it and with a spare SD card that they can dedicate to the
project. It will come in two pieces: an installation firmware file
that will set the autoboot flag and write the boot block to the SD
card, and an AUTOEXEC.BIN that the camera will load automatically
when that card is in the camera. Unlike the 5D Mark II, it will
only be possible to build unsigned AUTOEXEC.BIN files for the
firmware image.
Please send me an email if you want to participate in the alpha tests.
--
Trammell
--
http://magiclantern.wikia.com/
To post to this group, send email to ml-d...@googlegroups.com
To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
Happy to test on my 550d
Dan
Sent from my iPhone
Sent from my iPhone
Does this mean that there is any hope for a backport to 500D?
With people upgrading to 550D they should be available cheaper now, and
if ML were available, that would make a great beginner's device...
Or are there any radical hardware changes on the 550D?
--
pascal
There was an overwhelming amount of interest in testing this, so I
have posted the current build and written some installation
instructions on the wiki:
http://magiclantern.wikia.com/wiki/550D
The usual caveats apply even more in this case than the 5D code.
Unlike the 5D, this does write to the camera's NVRAM to set the
DISKBOOT flag.
Good luck!
--
Trammell
Or I might have commented out the call("EnableBootDisk") in bootflags.c when I was stubbing out the sd->readblock() calls. I'll check when I get home.
Sent from my iPhone
I've confirmed this behaviour. It appears that the properties for
the exposure settings are only updated in manual exposure mode.
There must be a different property for the auto-program modes.
> Autoboot alone (without upgrade each time) does not work. I have
> "Done" in bug letters as expected, just before booting the
> autoexec.bin.
Rather than using call-by-name, I switched to a direct function call
to bootdisk_enable() and toggled it off on my camera to confirm that
it would be correctly set. I've uploaded -rc1 to bitbucket with the
fix.
Do be sure that your SD card is correctly marked for autoboot; I use
dd (or bvi) to do it:
echo EOS_DEVELOP | dd of="$dev" bs=1 seek=71 count=11
echo BOOTDISK | dd of="$dev" bs=1 seek=92 count=8
> Trammel, thanks for this great work in such a short time!
It wouldn't have happened with out your (and other parties')
assistance!
--
Trammell
I've made a little tool to write and remove the labels.
It works with FAT32 cards.
You can download from here: http://pel.hu/down/bootCF.exe
Regards,
pel
I believe that is correct. The structures in sounddev_task()
appears to have changed, so we are never getting the wakeup
to do the reconfigure.
That is also why the headphone out isn't working yet.
I'm not sure why the hotplug is broken, however; we should be
overriding the hotplug_task(), but it still shuts down the LCD when
I plug in the A/V cable. That will be a project for this weekend.
--
Trammell
I've "fixed" the hotplug problem on the 550D by replacing the
hotplug task with an empty function. It returns immediately,
disabling any hot plug functionality.
I'm not sure if we need to understand the structure; to enable
or disable the USB port, or to switch output monitors we can call
the interrupt routines directly and allow them to update the struct.
--
Trammell
-deke