Author Topic: Canon EOS 1300D / Rebel T6  (Read 44118 times)

vwdeiu

  • New to the forum
  • *
  • Posts: 4
Re: Canon EOS 1300D / Rebel T6
« Reply #175 on: March 31, 2018, 08:51:19 PM »
I'm looking forward to see a finished version of ML on this model.
Keep up the good work devs :P

vwdeiu

  • New to the forum
  • *
  • Posts: 4
Re: Canon EOS 1300D / Rebel T6
« Reply #176 on: April 05, 2018, 02:39:13 PM »
I am ready to test any version of ML on my EOS T6 even though its buggy.

PS: Isn;t T5 similar to the T6 coding?

Teanut

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS 1300D / Rebel T6
« Reply #177 on: April 05, 2018, 05:35:45 PM »
I am ready to test any version of ML on my EOS T6 even though its buggy.

PS: Isn;t T5 similar to the T6 coding?

My understanding from following this forum post is that the DIGIC 4+ processor in the EOS-1300D/Rebel T6 (and forthcoming 2000D/T7 and 4000D/T100) is mostly a DIGIC 4, with some DIGIC 5 and 6 improvements. So it's not a straight shot from the 1200D/T5 (which used a DIGIC 4 and not a 4+), but it's not completely unfamiliar territory either.

vwdeiu

  • New to the forum
  • *
  • Posts: 4
Re: Canon EOS 1300D / Rebel T6
« Reply #178 on: April 08, 2018, 10:21:09 PM »
My understanding from following this forum post is that the DIGIC 4+ processor in the EOS-1300D/Rebel T6 (and forthcoming 2000D/T7 and 4000D/T100) is mostly a DIGIC 4, with some DIGIC 5 and 6 improvements. So it's not a straight shot from the 1200D/T5 (which used a DIGIC 4 and not a 4+), but it's not completely unfamiliar territory either.

Oh.. that means we/re pretty far away from ML on T6 if reverse engeneering isn/t ready yet.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 11218
  • 5D Mark Free
Re: Canon EOS 1300D / Rebel T6
« Reply #179 on: April 09, 2018, 06:57:30 AM »
On the contrary - it can be already tested and debugged in QEMU!

When all else fails... read previous posts ;)

For the impatient: QEMU guide, RE guide, installation video for Ubuntu, for Mac, guide for Windows and... next steps.

Teanut

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS 1300D / Rebel T6
« Reply #180 on: April 09, 2018, 05:28:07 PM »
Oh.. that means we/re pretty far away from ML on T6 if reverse engeneering isn/t ready yet.

See below:

On the contrary - it can be already tested and debugged in QEMU!

When all else fails... read previous posts ;)

For the impatient: QEMU guide, RE guide, installation video for Ubuntu, for Mac, guide for Windows and... next steps.

This thread has a lot of good information if you read the previous posts. I don't have the free time to do a lot of testing right now, but if you do, and want to contribute to ML's progress, give it a shot. It doesn't sound like it's too far off, and I suspect a lot of the hurdles here will also help with the 2000D/T7 and 4000D/T100 (since they're also on DIGIC 4+.) Who knows, maybe it'll even help with DIGIC 6 and above!

vwdeiu

  • New to the forum
  • *
  • Posts: 4
Re: Canon EOS 1300D / Rebel T6
« Reply #181 on: April 13, 2018, 02:26:47 PM »
See below:

This thread has a lot of good information if you read the previous posts. I don't have the free time to do a lot of testing right now, but if you do, and want to contribute to ML's progress, give it a shot. It doesn't sound like it's too far off, and I suspect a lot of the hurdles here will also help with the 2000D/T7 and 4000D/T100 (since they're also on DIGIC 4+.) Who knows, maybe it'll even help with DIGIC 6 and above!
Well I'm glad to help...but in terms of coding I dont know anything so if you could tell me the steps I should follow to test the software I'll be gratefull

Teanut

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS 1300D / Rebel T6
« Reply #182 on: April 13, 2018, 04:21:58 PM »
Well I'm glad to help...but in terms of coding I dont know anything so if you could tell me the steps I should follow to test the software I'll be gratefull

You don't need to know how to code. Look at a1ex's reply from April 9, 2018. He already told you the steps. At the bottom he listed links for you to follow on:

Focus on steps 1, 2, and 4 to start. Document anything that doesn't seem to work right (keep a journal/logbook) by describing what you did and what isn't working correctly, then report it back in this thread. Step 3 seems to require more understanding of code.