lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201012311230.51903.laurent.pinchart@ideasonboard.com>
Date:	Fri, 31 Dec 2010 12:30:51 +0100
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	"Igor M. Liplianin" <liplianin@...by>, linux-media@...r.kernel.org,
	linux-kernel@...r.kernel.org, aospan@...up.ru
Subject: Re: [PATCH 01/18] Altera FPGA firmware download module.

Hi Mauro,

On Friday 31 December 2010 12:27:38 Mauro Carvalho Chehab wrote:
> 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.

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.

> Actually, I liked the idea, as the FPGA programming driver could be
> useful if other drivers have similar usecases.

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.

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ