From: antirez <antirez@invece.org>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: "'antirez@invece.org'" <antirez@invece.org>,
Greg KH <greg@wirex.com>, Heitzso <xxh1@cdc.gov>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'Johannes Erdfelt'" <johannes@erdfelt.com>
Subject: Re: USB broken in 2.4.0
Date: Sat, 6 Jan 2001 04:50:50 +0100 [thread overview]
Message-ID: <20010106045050.C1748@prosa.it> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDEBE@orsmsx31.jf.intel.com>
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDEBE@orsmsx31.jf.intel.com>; from randy.dunlap@intel.com on Fri, Jan 05, 2001 at 04:48:00PM -0800
On Fri, Jan 05, 2001 at 04:48:00PM -0800, Dunlap, Randy wrote:
> This rings a small bell with me.
> There was a change by Dan Streetman IIRC to limit
> usbdevfs bulk transfers to PAGE_SIZE (4 KB for x86,
> or 0x1000). Anything larger than that returns
> an error (-EINVAL).
Yes, devio.c, proc_bulk():
if (len1 > PAGE_SIZE)
return -EINVAL;
Actually it is the max transfer size I can reach.
I guess that to limit the page size can be an impementation
advantage but it may slow-down a bit some userspace driver.
I feel that even if the linux way is to implement the USB
drivers in kernel space a full-featured USB user space access
should be allowed.
antirez
(please cc me)
--
Salvatore Sanfilippo | <antirez@invece.org>
http://www.kyuzz.org/antirez | PGP: finger antirez@tella.alicom.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 0:48 USB broken in 2.4.0 Dunlap, Randy
2001-01-06 3:50 ` antirez [this message]
2001-01-06 1:53 ` Johannes Erdfelt
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:38 Heitzso
2001-01-08 17:54 ` antirez
2001-01-05 17:38 Heitzso
2001-01-05 18:00 ` Greg KH
2001-01-05 23:04 ` antirez
2001-01-06 2:39 ` antirez
2001-01-06 3:40 ` antirez
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=20010106045050.C1748@prosa.it \
--to=antirez@invece.org \
--cc=greg@wirex.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.com \
--cc=xxh1@cdc.gov \
/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.