From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Sven Van Asbroeck <thesven73@gmail.com>,
robh+dt@kernel.org, linus.walleij@linaro.org
Cc: lee.jones@linaro.org, mark.rutland@arm.com, afaerber@suse.de,
treding@nvidia.com, david@lechnology.com, noralf@tronnes.org,
johan@kernel.org, monstr@monstr.eu, michal.vokac@ysoft.com,
arnd@arndb.de, gregkh@linuxfoundation.org, john.garry@huawei.com,
geert+renesas@glider.be, robin.murphy@arm.com,
paul.gortmaker@windriver.com,
sebastien.bourdelin@savoirfairelinux.com, icenowy@aosc.io,
stuyoder@gmail.com, jan.kiszka@siemens.com,
maxime.ripard@bootlin.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card
Date: Mon, 15 Apr 2019 19:41:02 +0200 [thread overview]
Message-ID: <982e69c6-4e68-6f62-8bed-cd5a1802272b@metux.net> (raw)
In-Reply-To: <20190409144250.7237-1-TheSven73@gmail.com>
On 09.04.19 16:42, Sven Van Asbroeck wrote:
Hi,
> Fieldbus device (client) adapters allow data exchange with a PLC aka.
> "Fieldbus Controller" over a fieldbus (Profinet, FLNet, etc.)
AFAIK, "fieldbus" is a bit broader term than just the typical IEC61158-
style remote memory stuff. At least that's the terminology my clients
tend to use (eg. they also call some homebbrewn rs485-based protocols
"fieldbus").
Maybe it would be better calling it "IEC-61158" instead of "fieldbus" ?
By the way: can this device be opened/used by several processes
simultaniously ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-04-15 17:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:42 [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 1/7] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-04-16 11:13 ` Greg KH
2019-04-09 14:42 ` [PATCH v10 2/7] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 3/7] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 4/7] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-04-09 15:50 ` Rob Herring
2019-04-09 17:16 ` Sven Van Asbroeck
2019-04-09 17:31 ` Sven Van Asbroeck
2019-04-09 21:09 ` Rob Herring
2019-04-10 13:11 ` Sven Van Asbroeck
2019-04-16 11:11 ` Greg KH
2019-04-09 14:42 ` [PATCH v10 5/7] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 6/7] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 7/7] staging: fieldbus_dev: add TODO Sven Van Asbroeck
2019-04-15 17:41 ` Enrico Weigelt, metux IT consult [this message]
2019-04-15 18:31 ` [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-04-16 16:49 ` Enrico Weigelt, metux IT consult
2019-04-16 18:56 ` Sven Van Asbroeck
2019-04-16 21:18 ` Enrico Weigelt, metux IT consult
2019-04-16 21:49 ` Sven Van Asbroeck
2019-04-16 22:12 ` Sven Van Asbroeck
2019-04-18 8:32 ` Enrico Weigelt, metux IT consult
2019-04-18 17:34 ` Sven Van Asbroeck
2019-04-24 9:40 ` Enrico Weigelt, metux IT consult
2019-04-24 10:26 ` Oliver Hartkopp
2019-04-24 11:00 ` Andreas Färber
2019-04-24 11:48 ` Oliver Hartkopp
2019-04-24 15:10 ` Sven Van Asbroeck
2019-04-29 13:54 ` Enrico Weigelt, metux IT consult
2019-04-17 14:37 ` Sven Van Asbroeck
2019-04-17 17:04 ` Andreas Färber
2019-04-17 20:13 ` Enrico Weigelt, metux IT consult
2019-04-25 8:26 ` Lee Jones
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=982e69c6-4e68-6f62-8bed-cd5a1802272b@metux.net \
--to=lkml@metux.net \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.io \
--cc=jan.kiszka@siemens.com \
--cc=johan@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=michal.vokac@ysoft.com \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=stuyoder@gmail.com \
--cc=thesven73@gmail.com \
--cc=treding@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).