Date: Fri, 20 Mar 2009 15:37:13 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel =?ISO-8859-14?B?S3L8Z2Vy?= 
	<daniel.krueger@systec-electronic.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>, Greg KH <greg@kroah.com>,
       linux-kernel@vger.kernel.org, Michael Olbrich <mol@pengutronix.de>,
       Wolfram Sang <wsa@pengutronix.de>,
       Marc Kleine-Budde <mkl@pengutronix.de>,
       Thomas Gleixner <tglx@linutronix.de>
Subject: Re: The Linux Staging tree, what it is and is not.
Message-ID: <20090320153713.65bf8e2d@lxorguk.ukuu.org.uk>
In-Reply-To: <49C3B33F.1020905@systec-electronic.com>
References: <20090318183232.GA11594@kroah.com>
	<20090320005808.GM5367@pengutronix.de>
	<20090320100146.6599f671@lxorguk.ukuu.org.uk>
	<20090320103545.GQ5367@pengutronix.de>
	<20090320105556.4375176d@lxorguk.ukuu.org.uk>
	<20090320111552.GS5367@pengutronix.de>
	<49C3B33F.1020905@systec-electronic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1563
Lines: 30

> My understanding of an object dictionary is that it is only a structured 
> view to a set of configuration variables, process variables and 
> diagnostic information. It could also be an XML file or a simple C 
> struct. In our implementation the object dictionary is not necessarily 
> the backing store of the data. The process variables for example are 

It's also possible I think to look at the object dictionary as no
different from port numbers. The object identifiers tell you who owns the
data and thus who needs to be told. I admit to being a bit rusty on this.
My last near encounters with fieldbus type systems were some years ago
when I?IT was involved in EMUG and OLCHFA and I managed to keep out of
the blast radius of those ;)

> information of what to copy to where comes from the object dictionary. 
> But it is possible to extract this information from the objdict and pass 
> it via generic structures (e.g. something like IO vectors) to the PDO 
> module in kernel. The information flow of the configuration data is 
> one-way only, from userspace to kernel. This is what I plan to implement 
> in openPOWERLINK, because the copy information can also be passed to a 
> special hardware like a DMA controller.

Ok so your hardware in fact really is oriented around an mmap type
interface ?

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