linux-kernel - Re: The Linux Staging tree, what it is and is not.

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:	Fri, 20 Mar 2009 15:37:13 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Daniel Krüger 
	<daniel.krueger@...tec-electronic.com>
Cc:	Robert Schwebel <r.schwebel@...gutronix.de>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	Michael Olbrich <mol@...gutronix.de>,
	Wolfram Sang <wsa@...gutronix.de>,
	Marc Kleine-Budde <mkl@...gutronix.de>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: The Linux Staging tree, what it is and is not.

> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/