Am 25.01.2013 19:00, schrieb Paul Brook:
1. It's not point-to-point, has an arbitrary nr of connection points.
QoM currently only does asymmetric 1-1 connections between objects. However
I
don't think this is a fatal problem. We can still retain an asymmetric API
(effectively
On Fri, Jan 25, 2013 at 06:00:36PM +, Paul Brook wrote:
To be able to create generic GPIO devices or other devices that have GPIO
like pins (e.g MDIO), and hook those up to external buses through common
frameworks, we need agreement on how to model tristate pins.
A tristate pin model,
To be able to create generic GPIO devices or other devices that have GPIO
like pins (e.g MDIO), and hook those up to external buses through common
frameworks, we need agreement on how to model tristate pins.
A tristate pin model, or at least agreement on how to model these with
multiple
Sorry for reposting,
My email client freaked out when posting the first reply...
- Forwarded message from Edgar E. Iglesias edgar.igles...@gmail.com
-
Return-Path: edgar.igles...@gmail.com
Received: from localhost (rocksteady.se.axis.com. [195.60.68.156])
by mx.google.com with
It also worries me that there isn't a clean separation between the MDIO
bus and the bitbang interface. IMO the bitbang interface should be a
separate device, and if we're wiring up bitbang interfaces then it
really should be via standard GPIO pins (aka qemu_irq).
Only the bitbang
On Thu, Jan 24, 2013 at 02:21:09PM +, Paul Brook wrote:
It also worries me that there isn't a clean separation between the MDIO
bus and the bitbang interface. IMO the bitbang interface should be a
separate device, and if we're wiring up bitbang interfaces then it
really should
