From: "Daniel Krüger" <daniel.krueger@systec-electronic.com>
To: david@lang.hm
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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.
Date: Mon, 23 Mar 2009 10:03:23 +0100 [thread overview]
Message-ID: <49C7505B.2010205@systec-electronic.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0903201332130.16753@asgard.lang.hm>
david@lang.hm schrieb:
> On Fri, 20 Mar 2009, Alan Cox wrote:
>
>>> 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 ?
>
> what I understand from this thread is that the hardware is a standard
> ethernet card.
It may be a standard Ethernet controller. But it could also be a
controller with a special hardware acceleration.
cu,
Daniel
--
SYS TEC electronic GmbH
August-Bebel-Str. 29
D-07973 Greiz
Telefon : +49 (0) 3661 6279 0
Fax : +49 (0) 3661 6279 99
Email : daniel.krueger@systec-electronic.com
Internet : http://www.systec-electronic.com
Managing Director : Dipl.-Phys. Siegmar Schmidt
Commercial registry : Amtsgericht Jena, HRB 205563
next prev parent reply other threads:[~2009-03-23 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 18:32 The Linux Staging tree, what it is and is not Greg KH
2009-03-20 0:58 ` Robert Schwebel
2009-03-20 2:48 ` Greg KH
2009-03-20 8:34 ` Daniel Krüger
2009-03-20 8:46 ` Robert Schwebel
2009-03-20 17:25 ` Greg KH
2009-03-20 10:01 ` Alan Cox
2009-03-20 10:35 ` Robert Schwebel
2009-03-20 10:55 ` Alan Cox
2009-03-20 11:15 ` Robert Schwebel
2009-03-20 15:16 ` Daniel Krüger
2009-03-20 15:37 ` Alan Cox
2009-03-20 20:32 ` david
2009-03-23 9:03 ` Daniel Krüger [this message]
2009-03-23 9:16 ` Robert Schwebel
2009-03-20 4:26 ` Dave Airlie
2009-03-20 4:46 ` Greg KH
2009-03-20 16:05 ` Lubomir Rintel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C7505B.2010205@systec-electronic.com \
--to=daniel.krueger@systec-electronic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@lang.hm \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=mol@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
--cc=tglx@linutronix.de \
--cc=wsa@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox