From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: adam@yggdrasil.com, steve@steve-parker.org, linux-kernel@vger.kernel.org
Subject: Re: PWC issue
Date: Sat, 28 Aug 2004 10:26:20 -0700 [thread overview]
Message-ID: <20040828102620.25a934a2.rddunlap@osdl.org> (raw)
In-Reply-To: <20040828161242.GA14308@kroah.com>
On Sat, 28 Aug 2004 09:12:42 -0700 Greg KH wrote:
| On Sat, Aug 28, 2004 at 08:11:00AM -0700, Randy.Dunlap wrote:
| > On Fri, 27 Aug 2004 22:19:19 -0700 Greg KH wrote:
| >
| > | On Sat, Aug 28, 2004 at 10:50:05AM -0700, Adam J. Richter wrote:
| > | >
| > | > By the way, I have a long running dispute with Greg K-H
| > | > about his refusal so far to remove replace the GPL incompatible
| > | > firmware in certain USB serial drivers with such a user level
| > | > loading mechanism. Go figure.
| > |
| > | Send me a patch to do so, and I will apply it (must include userspace
| > | files so that hotplug can load them properly.)
| > |
| > | The last time we went around about this I rejected it as we were in a
| > | stable kernel series. As that is now not true, I'm open to the patch.
| >
| > Which part is now not true?
|
| The "stable" part.
I guess I'm still confused by some of what I consider contradictory
remarks by Linus at the kernel summit, and the lack of a summary of
that particular kernel summit session (other than on lwn.net).
I think that we have only a stable kernel and not a development
kernel series now, and that's a loss. But it's a loss either way
that we toss & turn it...
| Actually in thinking about it some more, we should offer up both options
| for at least 6 months, with a warning that the in-kernel stuff is going
| to be deleted on a specific date. That gives everyone time to convert
| their userspace utilities to use the new firmware download code.
|
| Sound good?
Some bounded time would be good, yes. Would have been good for pwc also,
although Nemosoft has had 4 years to move the kernel decompression to
userspace afaik, so it seems that he has taken way too long to get
that done.
--
~Randy
next prev parent reply other threads:[~2004-08-28 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 17:50 Adam J. Richter
2004-08-28 5:19 ` Greg KH
2004-08-28 15:11 ` Randy.Dunlap
2004-08-28 15:33 ` Kasper Sandberg
2004-08-28 16:12 ` Greg KH
2004-08-28 17:26 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-29 4:25 Adam J. Richter
2004-08-29 2:06 Adam J. Richter
2004-08-29 5:01 ` Greg KH
2004-08-29 0:20 Adam J. Richter
2004-08-28 0:57 Steve Parker
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=20040828102620.25a934a2.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=adam@yggdrasil.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@steve-parker.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
all inboxes | Powered by JetHome®