linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alaganraj Sandhanam <alaganraj.sandhanam@gmail.com>
To: Sakari Ailus <sakari.ailus@iki.fi>, linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com
Subject: Re: omap3isp Device Tree support status
Date: Tue, 07 Oct 2014 02:37:37 +0530	[thread overview]
Message-ID: <54330499.50905@gmail.com> (raw)
In-Reply-To: <20140928221341.GQ2939@valkosipuli.retiisi.org.uk>

Hi Sakari,

Thanks for the patches.
On Monday 29 September 2014 03:43 AM, Sakari Ailus wrote:
> Hi,
> 
> I managed to find some time for debugging my original omap3isp DT support
> patchset (which includes smiapp DT support as well), and found a few small
> but important bugs.
> 
> The status is now that images can be captured using the Nokia N9 camera, in
> which the sensor is connected to the CSI-2 interface. Laurent confirmed that
> the parallel interface worked for him (Beagleboard, mt9p031 sensor on
> Leopard imaging's li-5m03 board).
Good news!
> 
> These patches (on top of the smiapp patches I recently sent for review which
> are in much better shape) are still experimental and not ready for review. I
> continue to clean them up and post them to the list when that is done. For
> now they can be found here:
> 
> <URL:http://git.linuxtv.org/cgit.cgi/sailus/media_tree.git/log/?h=rm696-043-dt>
> 
I couldn't clone the repo, getting "remote corrupt" error.

$ git remote -v
media-sakari	git://linuxtv.org/sailus/media_tree.git (fetch)
media-sakari	git://linuxtv.org/sailus/media_tree.git (push)
origin	git://linuxtv.org/media_tree.git (fetch)
origin	git://linuxtv.org/media_tree.git (push)
sakari	git://vihersipuli.retiisi.org.uk/~sailus/linux.git (fetch)
sakari	git://vihersipuli.retiisi.org.uk/~sailus/linux.git (push)

$ git fetch media-sakari
warning: cannot parse SRV response: Message too long
remote: error: Could not read 5ea878796f0a1d9649fe43a6a09df53d3915c0ef
remote: fatal: revision walk setup failed
remote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header

Can you please guide me?

Thanks&Regards,
Alaganraj

  reply	other threads:[~2014-10-06 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28 22:13 omap3isp Device Tree support status Sakari Ailus
2014-10-06 21:07 ` Alaganraj Sandhanam [this message]
2014-10-08 11:33   ` Sakari Ailus
2014-10-09 20:38     ` Alaganraj Sandhanam
2014-10-10  7:51       ` Sakari Ailus
2015-01-06  9:11         ` Alaganraj Sandhanam

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=54330499.50905@gmail.com \
    --to=alaganraj.sandhanam@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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;
as well as URLs for NNTP newsgroup(s).