EOS M100 porting

c_joerg

1251

Re: EOS M100 porting

« Reply #70 on: 02 / November / 2020, 14:00:44 »

Advertisements

Quote from: srsa_4c on 17 / September / 2020, 11:48:12

I found a related eventproc that can produce an xml file. I don't know if the content is the same, but it's worth a try.
Code: [Select]
private sub Initialize() System.Create() CamInfo_Debug(1) end sub

Should that also work with the M3?
It doesn't seem to work there

Logged

M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Caefix

947
Sorry, busy deleting test shots...

Re: EOS M100 porting

« Reply #71 on: 04 / November / 2020, 12:46:00 »

Seen in other EOS-M topics,too: some lenses avoid to write their dist_values at the expected addresses,
even Canon EF28-90 &EF70-210.
Any idea how/where to search for alternatives?
A lovely lens is 7artisans 35 1:1.2. Looks nostalgic, boots fine.
Could we have focus magnifier with manual lenses?

Logged

All lifetime is a loan from eternity.

c_joerg

1251

Re: EOS M100 porting

« Reply #72 on: 04 / November / 2020, 13:30:44 »

Quote from: Caefix on 04 / November / 2020, 12:46:00

Seen in other EOS-M topics,too: some lenses avoid to write their dist_values at the expected addresses,
even Canon EF28-90 &EF70-210.

Older lenses probably do not offer this interface...

Quote from: Caefix on 04 / November / 2020, 12:46:00

Could we have focus magnifier with manual lenses?

The M100 offers a 10x focus magnifier...
(In the touch screen in the lower left corner)

Logged

M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

srsa_4c

4451

Re: EOS M100 porting

« Reply #73 on: 09 / November / 2020, 14:35:01 »

Update. Only boot-related changes, capt_seq and other anomalies are unchanged.
Spytask is no longer started when the boot reason is one of the obscure ones (lens, card door, battery door). This may solve the boot crashes - no second blink should occur after detaching/attaching lens, closing doors.

edit:
Also sanitized the cache operations during startup.

Quote from: c_joerg on 02 / November / 2020, 14:00:44