From: Greg KH <greg@wirex.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Pifko Krisztian <pifko@kirowski.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] philips rush usb support
Date: Mon, 26 Feb 2001 16:23:54 -0800 [thread overview]
Message-ID: <20010226162354.F5492@wirex.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102241730370.19866-100000@pifko.kirowski.com> <20010224121312.S16341@sventech.com> <20010225192454.A1697@bug.ucw.cz>
In-Reply-To: <20010225192454.A1697@bug.ucw.cz>; from pavel@suse.cz on Sun, Feb 25, 2001 at 07:24:54PM +0100
On Sun, Feb 25, 2001 at 07:24:54PM +0100, Pavel Machek wrote:
> > > Userspace stuff should be found at http://openrush.sourceforge.net
> > > if you have a rush. It works for me on ia32 with the model sa125.
> >
> > Why can't the entire driver be in userspace? It appears it uses a
> > completely proprietary protocol and you've created a completely
> > proprietary interface to the kernel.
>
> Would not making it "usb-serial" device do the trick?
That would work if you don't want to use a new minor number for the
device. But all of the current usb-serial drivers are there because
userspace tools expect the device to act just like a serial port. Since
the userspace tools for this device is closely tied to the driver, that
restriction isn't really there.
I also agree with Johannes, this would probably be better off as a
userspace program.
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg
prev parent reply other threads:[~2001-02-27 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 16:39 [PATCH] philips rush usb support Pifko Krisztian
2001-02-24 17:13 ` Johannes Erdfelt
2001-02-25 18:24 ` Pavel Machek
2001-02-27 0:23 ` Greg KH [this message]
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=20010226162354.F5492@wirex.com \
--to=greg@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=pifko@kirowski.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 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.