From: Greg KH <greg@kroah.com>
To: martin f krafft <madduck@madduck.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: restarting a kernel thread
Date: Mon, 30 Jun 2003 14:43:19 -0700 [thread overview]
Message-ID: <20030630214319.GA27246@kroah.com> (raw)
In-Reply-To: <20030630213604.GA3974@piper.madduck.net> <20030630213957.GB3974@piper.madduck.net>
On Mon, Jun 30, 2003 at 11:39:57PM +0200, martin f krafft wrote:
> also sprach Greg KH <greg@kroah.com> [2003.06.30.2239 +0200]:
> > Any reason for not sticking with userspace programs using
> > libusb/usbfs? Much easier to write than kernel drivers, and you
> > get portibility across a wider range of OSs
>
> One question: will this have performance issues? We are dealing with
> high-resolution motors and sensors, and want to go real-time anyhow
> somewhen.
Don't know, you will have to test to see if it meets your latency
requirements.
On Mon, Jun 30, 2003 at 11:36:04PM +0200, martin f krafft wrote:
>
> Well, that's a good idea. Problem is that the drivers are actually
> written by someone else. I just developing with them, and them
> a little on the side.
>
> But I'll pass the word on to the developers. Is this an easy
> transition?
The interface is quite different from writing a kernel driver, but in
the end, simpler, as you can just debug from userspace and not worry
about kernel problems.
thanks,
greg k-h
next prev parent reply other threads:[~2003-06-30 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 17:10 restarting a kernel thread martin f krafft
2003-06-30 18:00 ` Greg KH
2003-06-30 19:48 ` martin f krafft
2003-06-30 20:39 ` Greg KH
2003-06-30 21:36 ` martin f krafft
2003-06-30 21:39 ` martin f krafft
2003-06-30 21:43 ` Greg KH [this message]
2003-07-01 6:31 ` Oleg Drokin
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=20030630214319.GA27246@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.