[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-tr] Linux Kernel 2.4 Feature Freeze?
The following note was sent to me from the kernel mailing list. It seems that
Linus wants developers and people with "final" changes to get them in RIGHT NOW.
What this means for the Token-Ring developers is that now is the time to get any
changes to the tr.c / 802 code as well as any enhancements that have been on
wish lists, into the kernel for 2.4!
I beleive there are a few things out on the table:
-- whatever is left to do with the olympic driver (it looks good to me, albeit a
bit slow and "bursty" in my experience)
-- enhanced / shallow mode support for Shared RAM ISA/PCMCIA (ibmtr.c)
-- changes to tr.c / 802 as suggested/coded by some guy from Slashdot
-- Full Duplex support for all supported adapters (not sure if this is already
-- RAM paging for Shared RAM ISA/PCMCIA (ibmtr.c)
-- LANStreamer support (should be the lowest of low priorities, mainly since
PIT/Olympic based cards are infinitely better, anyways)
Anyways, I'm just trying to provide a friendly reminder here. The activity on
the mailing list has decreased significantly lately, too -- what's up with that?
Is everyone content with the way things are? :)
===== [forwarded note starts here] =====
Re: no driver change for 2.4?
Linus Torvalds (email@example.com)
Tue, 3 Aug 1999 13:50:34 -0700 (PDT)
On Tue, 3 Aug 1999, Jens Axboe wrote:
> >What do you think about cleaning up the other ugly part (aimed at 2.6, the
> >no driver changes mandate for 2.4 conflicts with it of course):
> I have a lot in the works wrt DVD and CD-R(W) media (the latter with
> the UDF people) that will require some updates to the ATAPI/SCSI drivers
> and Uniform CD-ROM layer. Is that a no-no for 2.3?
Feature freeze in about two weeks is the current plan.
In short, people who think they have major requirements had better get
their act together. That means that if ISDN people actually want to try to
get into a real release one of these years, they don't have all that much
time to futz around any more.
And it does mean that if it's not in working order already, it probably
won't make it into 2.4.