[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4aecef30-0d64-c5f7-c4de-43b0754e2fdd@metux.net>
Date: Tue, 16 Apr 2019 19:06:45 +0200
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: Sven Van Asbroeck <thesven73@...il.com>, robh+dt@...nel.org,
linus.walleij@...aro.org
Cc: lee.jones@...aro.org, mark.rutland@....com, afaerber@...e.de,
treding@...dia.com, david@...hnology.com, noralf@...nnes.org,
johan@...nel.org, monstr@...str.eu, michal.vokac@...ft.com,
arnd@...db.de, gregkh@...uxfoundation.org, john.garry@...wei.com,
geert+renesas@...der.be, robin.murphy@....com,
paul.gortmaker@...driver.com,
sebastien.bourdelin@...oirfairelinux.com, icenowy@...c.io,
stuyoder@...il.com, jan.kiszka@...mens.com,
maxime.ripard@...tlin.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus
On 16.04.19 17:56, Sven Van Asbroeck wrote:
Hi,
> The Anybus-S/Anybus-M is a series of interchangeable fieldbus communication
> modules featuring on board memory and processing power. All software and
> hardware functionality required to communicate on the fieldbus is
> incorporated in the module itself, allowing the application to focus on
> other tasks.
I'm a bit confused, what this anybus stuff actually does.
Is it some proprietary backplane bus, where things like eg. fieldbus
adapters are attached to ?
I see some struct bus_type field declaration - is that going to be some
subsystem, similar to those for other bus'es (eg. pci, usb, ...) ?
Maybe that deserves a bit more documentation :p
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists