From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Igor M. Liplianin" <liplianin@me.by>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
aospan@netup.ru
Subject: Re: [PATCH 01/18] Altera FPGA firmware download module.
Date: Fri, 31 Dec 2010 09:27:38 -0200 [thread overview]
Message-ID: <4D1DBE2A.5080003@infradead.org> (raw)
In-Reply-To: <201012311212.19715.laurent.pinchart@ideasonboard.com>
Em 31-12-2010 09:12, Laurent Pinchart escreveu:
> Hi Igor,
>
> On Friday 31 December 2010 06:26:31 Igor M. Liplianin wrote:
>> It uses STAPL files and programs Altera FPGA through JTAG.
>> Interface to JTAG must be provided from main device module,
>> for example through cx23885 GPIO.
>
> It might be a bit late for this comment (sorry for not having noticed the
> patch set earlier), but...
>
> Do we really need a complete JTAG implementation in the kernel ? Wouldn't it
> better to handle this in userspace with a tiny kernel driver to access the
> JTAG signals ?
>
Laurent,
Igor already explained it. From what I understood, the device he is
working has a firmware that needs to be loaded via JTAG/FPGA.
Actually, I liked the idea, as the FPGA programming driver could be
useful if other drivers have similar usecases.
Cheers,
Mauro
next prev parent reply other threads:[~2010-12-31 11:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 5:26 [PATCH 01/18] Altera FPGA firmware download module Igor M. Liplianin
2010-12-31 5:39 ` Randy Dunlap
2010-12-31 10:53 ` Mauro Carvalho Chehab
2011-01-01 0:39 ` Igor M. Liplianin
2010-12-31 11:12 ` Laurent Pinchart
2010-12-31 11:27 ` Mauro Carvalho Chehab [this message]
2010-12-31 11:30 ` Laurent Pinchart
2010-12-31 11:47 ` Mauro Carvalho Chehab
2010-12-31 15:04 ` Ben Gamari
2011-01-05 10:26 ` Laurent Pinchart
2011-01-10 20:10 ` Igor M. Liplianin
2011-01-07 19:31 ` Ben Gamari
2011-01-16 17:04 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2010-12-31 11:37 Igor M. Liplianin
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=4D1DBE2A.5080003@infradead.org \
--to=mchehab@infradead.org \
--cc=aospan@netup.ru \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
/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