From: Ben Gamari <bgamari.foss@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>,
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 10:04:13 -0500 [thread overview]
Message-ID: <8739pec7bm.fsf@gmail.com> (raw)
In-Reply-To: <4D1DC2DD.6050400@infradead.org>
On Fri, 31 Dec 2010 09:47:41 -0200, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> > I understand this. However, a complete JTAG state machine in the kernel, plus
> > an Altera firmware parser, seems to be a lot of code that could live in
> > userspace.
>
> Moving it to userspace would mean a kernel driver that would depend on an
> userspace daemon^Wfirmware loader to work. I would NAK such designs.
>
Why? I agree that JTAG is a lot to place in the kernel and is much
better suited to be in user space. What exactly is your objection to
depending on a userspace utility? There is no shortage of precedent for
loading firmware in userspace (e.g. fx2 usb devices).
> > If I understand it correctly the driver assumes the firmware is in an Altera
> > proprietary format. If we really want JTAG code in the kernel we should at
> > least split the file parser and the TAP access code.
> >
>
> Agreed, but I don't think this would be a good reason to block the code merge
> for .38.
>
I agree with the above isn't good reason to block it but if there is
still debate about the general architecture of the code (see above),
then it seems aren't ready yet. The code looks very nice, but I'm not at
all convinced that it needs to be in the kernel. Just my two-tenths of a
cent.
Cheers,
- Ben
next prev parent reply other threads:[~2010-12-31 15:04 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
2010-12-31 11:30 ` Laurent Pinchart
2010-12-31 11:47 ` Mauro Carvalho Chehab
2010-12-31 15:04 ` Ben Gamari [this message]
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=8739pec7bm.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--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 \
--cc=mchehab@infradead.org \
/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