Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
CISTPL_CONFIG
Configuration Tuple is stored in the cf card header and ispLStorage=0x685504
is the reg on the card as seen in the start up log I've posted , & the mode it run at t0 -Cycle time (min)
t1 -Address Valid to -IORD/-IOWR setup(min) (Mode3= 180ns Mode4= 120ns)
t2 -IORD/-IOWR (min)(Mode3= 30ns Mode4= 25ns)
t2 -IORD/-IOWR (min) Register (8 bit)(Mode3= 80ns Mode4= 70ns)
t2i -IORD/-IOWR recovery time (min) (Mode3= 80ns Mode4= 70ns)
t3 -IOWR data setup (min) (Mode3= 30ns Mode4= 20ns)
t4 -IOWR data hold (min) (Mode3= 10ns Mode4= 10ns)
t5 -IORD data setup (min) (Mode3= 20ns Mode4= 20ns)
t6 -IORD data hold (min) (Mode3= 5ns Mode4= 5ns)
t6Z -IORD data tristate (max)(Mode3= 30ns Mode4= 30ns)
t7 Address valid to -IOCS16 assertion (max) (Mode3= n/a ns Mode4= n/a ns)
t8 Address valid to -IOCS16 released (max) (Mode3= n/a ns Mode4= n/a ns)
t9 -IORD/-IOWR to address valid hold (Mode3= 10ns Mode4= 10ns)
tRD Read Data Valid to IORDY active (min), if IORDY initially low after tA (Mode3= 0ns Mode4= 0ns)
tA IORDY Setup time (Mode3= 35ns Mode4= 35ns)
tB IORDY Pulse Width (max) (Mode3= 1250ns Mode4= 1250ns)
tC IORDY assertion to release (max)(Mode3= 5ns Mode4= 5ns)
mv=1 res=0 crop=0 task=? pc=ff986cc4 addr=82d0 HEAD1 timer (start?).c0f0713c: 476 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8328 HEAD3 timer (ticks?).c0f07134: 4 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8330 HEAD3 timer (start?).c0f07150: 49c ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1844 addr=8370 HEAD4 timer (ticks?).c0f15084: 10000 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
Right now we use (this is crop mode) c0f0713c (offset)475
c0f07150 (offset)49c
c0f07134
c0f15084
are not being modified , could be causing more overhead ? in write speed .Quote from: kitor on April 30, 2024, 10:11:42 PMWho said that?
Quote from: papajo on April 28, 2024, 08:22:05 PMSo I went to discord and asked about it and they told me that there never will be a 80D version of magic lantern
Quote from: papajo on April 28, 2024, 08:22:05 PMCould you please update us of your intentions about the 80D firmware ?There are no intentions. Digic 6 is just hard to get working due to its unique design. It is just easier in later models running Digic 7 and 8.
Quote from: papajo on April 28, 2024, 08:22:05 PMI think quite a few models got magic lantern a lot sooner than 80D
Quote from: kitor on April 27, 2023, 08:16:41 AM
After a quick test I have a bad stub or two (tasks view doesn't display names properly[1], inLV our menu closes almost instantly[2]), other than that seems on par with 750D.
That was a quick (< 3 hour) job after i learned how to use Ghidra Version Tracking, thanks to @reyalp.
Ok, it took a week prior to that as I took the opportunity to create a proper loader script for Ghidra that should improve ghidra project quality a lot. More on that later.
E:
[1] Turns out one of task related structs is different.
[2] Fixed, wrong Canon dialog used in background.
Page created in 0.048 seconds with 12 queries.