mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 0/5] JUST-FOR-FUN: run barebox on Canon digital camera
Date: Tue, 6 Aug 2013 13:42:08 +0400	[thread overview]
Message-ID: <20130806134208.03ab93928d53b987226adb1d@gmail.com> (raw)
In-Reply-To: <20130806071353.GZ26614@pengutronix.de>

On Tue, 6 Aug 2013 09:13:53 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:

> On Mon, Aug 05, 2013 at 12:25:22AM +0400, Antony Pavlov wrote:
> > Please don't commit the patches!
> > 
> > This patch series introduce minimal support
> > for Canon DIGIC4-based cameras.
> > 
> > Supported cameras:
> > 
> >  * Canon PowerShot A1100;
> >  * Canon EOS 600D;
> >  * Canon EOS Magic Lantern qemu-based emulator.
> > 
> > After booting barebox starts compiled-in script
> > that use 'mw' command to blink camera's LED.
> > 
> > Just now barebox for Canon cameras is a demo
> > but after some improvements it can become very
> > handy tool for CHDK and Magic Lantern development.
> 
> Very cool stuff.
> 
> I'll have to have a look what model my wifes camera is ;)

To tell the truth there is no big difference in Canon cameras
for barebox developer. You can see, that there are no differences
in a1100 and 600d code in barebox (just memory size, but it can
be moved into device tree file). Moreover AFAIR there are no significant
software model differences between the chips in the DIGIC family.

To blink the LED of your PowerShot camera you only need to know 
the led-related GPIO address and canon binary file encode algorithm.
Both of this things can be obtained in the CHDK sources.

For DSRL cameras the situation is even less difficult.

> I'd be amazed if barebox could be used to help the magic lantern
> project.

If you want to help the Magic Lantern project please briefly describe
your mode of operation with incoming patches. AFAIR you have some
scripts to check all boards build after every single commit.
The Magic Lantern developers have some problems as they use
very different mode of operation:
 1. commit the change to the repo;
 2. fix build or functional error some time later.

I have adapted MAKEALL script from barebox for Magic Lantern,
but I have not not yet finished the script to check every new
mercurial commit (as Magic Lantern developers use mercurial).

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2013-08-06  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 20:25 Antony Pavlov
2013-08-04 20:25 ` [RFC 1/5] ARM: add very initial support for Canon DIGIC chips Antony Pavlov
2013-08-04 20:25 ` [RFC 2/5] ARM: DIGIC: add Canon EOS 600D support Antony Pavlov
2013-08-04 20:25 ` [RFC 3/5] ARM: DIGIC: add Canon PowerShot A1100 IS support Antony Pavlov
2013-08-04 20:25 ` [RFC 4/5] ARM: DIGIC: add canon-600d_defconfig Antony Pavlov
2013-08-04 20:25 ` [RFC 5/5] ARM: DIGIC: add canon-a1100_defconfig Antony Pavlov
2013-08-06  7:13 ` [RFC 0/5] JUST-FOR-FUN: run barebox on Canon digital camera Sascha Hauer
2013-08-06  9:42   ` Antony Pavlov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130806134208.03ab93928d53b987226adb1d@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox