From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Userpace serial port
Date: Thu, 11 Jun 2015 07:31:12 -0700 [thread overview]
Message-ID: <20150611143112.GD17984@kroah.com> (raw)
In-Reply-To: <CAPybu_2mGUS4_ibU0fLrbA7JNDXPBvYhWCrkcVA+yari9pcAxg@mail.gmail.com>
On Thu, Jun 11, 2015 at 08:39:39AM +0200, Ricardo Ribalda Delgado wrote:
> Hello Greg
>
> On Thu, Jun 11, 2015 at 5:52 AM, Greg KH <greg@kroah.com> wrote:
> > On Wed, Jun 10, 2015 at 02:39:35PM +0200, Ricardo Ribalda Delgado wrote:
>
> >> Nowadays there is a kernel land implementation of ethercat master, but
> >> it is not merged (and it is definately not an easy job). And a
> >> software implementation http://fh-soft.de/src/ethercat-userspace.html
> >
> > Why not attempt to merge it?
>
> I have my doubts that this is the best option. If you need real time
> performance you need to run it in kernel-space where you need a
> ethercat protocol driver, a patch for your network card and an kernel
> module for your application.
real-time performance does not mean it has to be in the kernel at all.
And almost no one needs "real" real-time performance, that's a horrible
check-box that people love to claim is needed and yet, almost no one
really needs in the end.
> By looking at our applications, The userspace sollution is more than
> enough for our requirements.
>
> The problem appears when we want to use the serial adapter. I want to
> keep using the serial API, but I cannot achieve this from userspace.
I don't understand what type of API you are talking about here. What
exactly does ethercat do? What are you doing that does not work today
from userspace with the existing serial apis?
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-11 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 12:39 Userpace serial port Ricardo Ribalda Delgado
2015-06-11 3:52 ` Greg KH
2015-06-11 6:39 ` Ricardo Ribalda Delgado
2015-06-11 8:20 ` Bjørn Mork
2015-06-11 14:31 ` Greg KH [this message]
2015-06-11 15:16 ` Ricardo Ribalda Delgado
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=20150611143112.GD17984@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).