> On Fri, May 30, 2003 at 04:37:20PM -0700, Andrew Morton wrote:
>> o Minor interface changes are pending in cio/ when the z990 machines are
>> out.
This should be at least PRI2, as it will change the user-visible interface,
e.g. the bus_id format for CCW devices.
>> There are some more things being worked on that are either post-2.6.0 or
>> are likely to remain outside of the official kernel (i.e. not for your
>> list):
>>
>> PRI3
The 'not for your list' actually referred to the items below...
>> o Jan Glauber is working on a fix for the timer issues related to running
>> on virtualized CPUs (wall-clock vs. cpu time).
>>
>> PRI1
Keep this as PRI3. It would be really nice to have, but I don't expect
it to be stable before 2.6.0. The current code is the same as in 2.4.
>> o the qeth driver will become GPL soon
>>
>> PRI3
>>
>> o a block device driver for ramdisks shared among virtual machines
>>
>> PRI3
Ok. We're only waiting for the OK from our lawyers before these
can be submitted. The qeth driver is ugly, but is the one for
the most common hardware, so it would be nice to have it included
eventually.
>>
>> o driver for crypto hardware
>>
>> PRI2
>>
>> o 'claw' network device driver
>>
>> PRI3
>>
>> o new zfcp fibre channel driver
>>
>> PRI3
These three drivers are not fully ported to 2.5 as they are less
important and we have no plan of submitting them for either 2.4
or 2.[567]. The code is also too ugly to be accepted anyway, so you
can drop them from the list. Vendors can pick up the source
from out developerworks site, as always...
> Is there a 2.5 patch of this somewhere?
No. An official release of the zfcp driver should be available at
the end of this year for linux-2.6. If you want to look at the
code, Heiko Carstens <heiko.carstens@de.ibm.com> can probably
send you a snapshot of his current working version.
Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/