linux-kernel - Re: [PATCH v3 2/5] mfd: add viperboard 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201211201044.20970.poeschel@lemonage.de>
Date:	Tue, 20 Nov 2012 10:44:20 +0100
From:	Lars Poeschel <poeschel@...onage.de>
To:	Wolfram Sang <w.sang@...gutronix.de>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>,
	Lars Poeschel <larsi@....tu-dresden.de>,
	linus.walleij@...aro.org, linux-kernel@...r.kernel.org,
	jic23@....ac.uk, khali@...ux-fr.org, ben-linux@...ff.org,
	grant.likely@...retlab.ca, linux-iio@...r.kernel.org
Subject: Re: [PATCH v3 2/5] mfd: add viperboard driver

On Tuesday 20 November 2012 at 09:34:56, Wolfram Sang wrote:
> I'll try to have a look this week. It fell a bit off because linux-i2c
> was not in CC. I do wonder about the naming, though. VIPERBOARD is
> probably the board name, but not the IP core/SoC name?

I am sorry, that I forgot the CC.
You are right it is the board name but not a IP/SoC name. It seems this 
device is weird to kernel developers - you are not the first one asking. You 
don't have to see the term board as in kernel sense where it describes a 
specific SoC and the components connected to it. It is a circuit board, that 
connects to usb on one side and GPIO, I²C and so on on the other side. You 
can have a look at it here:
http://nanorivertech.com/viperboard-specs.html
--
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/