linux-kernel - Query on I/O accessors used by Xilinx SystemACE Driver

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-next>] [day] [month] [year] [list]

Message-ID: <50FD40B3.804@synopsys.com>
Date:	Mon, 21 Jan 2013 18:50:51 +0530
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Grant Likely <grant.likely@...retlab.ca>
CC:	Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Michal Simek <monstr@...str.eu>,
	"Geert Uytterhoeven" <geert@...ux-m68k.org>
Subject: Query on I/O accessors used by Xilinx SystemACE Driver

Synopsys has Xilinx ML50x boards with our internal FPGA workflows, which we
sometimes use for internal development and customer evaluations. In that light
Alexey has been working on getting the stock systemACE driver to work with ARC
Linux Port.
One of things that he wants me to fix is introduce the PPC/m68k/microblaze style
in_8, in_le16, .... I/O accessors in ARC port, used specifically by driver.

I'm not an expert in that driver or the specific needs of those accessors on
respective arches, but was wondering, if it would be possible to convert the
driver to use the vanilla IO accessors (read{b,w,l}. Microblaze at least,  seem to
be defining them as straight wrappers over the standard raw accessors.

Ben, Geert could you please comment ?

Thx,
-Vineet
--
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/