From: "Randy.Dunlap" <rddunlap@osdl.org>
To: jmerkey@comcast.net
Cc: alan@lxorguk.ukuu.org.uk, wli@holomorphy.com, roland@topspin.com,
linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Sun, 29 Aug 2004 21:35:00 -0700 [thread overview]
Message-ID: <20040829213500.7f029513.rddunlap@osdl.org> (raw)
In-Reply-To: <083020040401.15279.4132A6990005360E00003BAF2200758942970A059D0A0306@comcast.net>
On Mon, 30 Aug 2004 04:01:29 +0000 jmerkey@comcast.net wrote:
|
|
|
| > On Sul, 2004-08-29 at 17:42, William Lee Irwin III wrote:
|
| > Ok so I can compile with a.out support. End of problem, that makes the
| > patch useful and "spec compliant", although the spec compliance is
| > irrelevant anyway. The spec doesn't determine what Linux is it's a
| > useful reference for normality. Special cases are special cases and you
| > harm the system by seeking to stop stuff that works purely for pieces of
| > paper.
| >
|
| Amen. USB 2.0 orinoco wireless drivers seems to have problems when user space
| is set to 1GB. Works grat with 2GB ad 3GB user space settings. Problem occurs during
| any acces to usb_read_device(). This doesn't look like a ABI problem, looks like
| a problem with the USB subsystem. The serialize semaphore gets stuck for some
| reason.
What kernel version? I can't even find usb_read_device() in 2.6.9-rc1.
BTW, as someone else requested, please teach your mail client to wrap
lines around column 70-72. Thanks.
| On the other topic, ABI compliance sounds a little restrictive since this is after all, an
| open source OS. Most apps get recompiled and I always download open source
| components for Linux.
--
~Randy
next prev parent reply other threads:[~2004-08-30 4:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 4:01 jmerkey
2004-08-30 4:35 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 22:50 jmerkey
2004-08-30 5:56 jmerkey
2004-08-30 18:10 ` Randy.Dunlap
2004-08-30 18:28 ` Roland Dreier
2004-09-22 18:52 ` Timothy Miller
2004-09-22 18:51 ` Roland Dreier
2004-09-22 20:22 ` Timothy Miller
2004-09-27 14:55 ` Roland Dreier
2004-08-26 23:47 linux
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26 20:24 jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones
2004-08-26 4:21 jmerkey
2004-08-26 4:33 ` William Lee Irwin III
2004-08-26 4:46 ` Roland Dreier
2004-08-26 4:49 ` William Lee Irwin III
2004-08-26 8:40 ` Ryan Cumming
2004-08-29 12:48 ` Alan Cox
2004-08-29 16:42 ` William Lee Irwin III
2004-08-29 15:45 ` Alan Cox
2004-08-29 17:00 ` William Lee Irwin III
2004-08-26 4:38 ` Martin J. Bligh
2004-08-26 4:42 ` Roland Dreier
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=20040829213500.7f029513.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®