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]
Date:	Tue, 03 May 2011 15:29:58 -0400
From:	Valdis.Kletnieks@...edu
To:	Andrew Lunn <andrew@...n.ch>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Grant Likely <grant.likely@...retlab.ca>,
	Martin Persson <martin.persson@...ricsson.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH 0/4] Pinmux subsystem

On Tue, 03 May 2011 19:27:12 +0200, Andrew Lunn said:

> I can think of two different solutions: 
> 
> 1) Three functions: uart-3wire, uart-hw-flow, uart-hw-flow-modem.  The
>    first just has 2 pins, the second 4 and the last 8. The board code
>    selects one of these for the serial driver to use.
> 
> 2) Three functions: uart-core, uart-hw-flow, uart-mode.  The first has
>    2 pins, the second has 2 pins and the last 4 pins. The board code tells
>    the driver to use uart-core, plus say uart-hw-flow.

For this second solution, what happens if some bozo selects *only* uart-modem
but not uart-core?  If there's a strict ordering (hw-flow requires core, modem
requires both hw-flow and core), it's essentially the same thing as the first
solution.  If there's not a strict ordering (i.e you can select uart-modem
without uart-core), you need to come up with sane semantics.


Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ