> -----Original Message-----
> From: Adam J. Richter [mailto:[email protected]]
> o dpt_i2o - I need to understand the i2o system a little
more
> to determine whether all of the similar looking code in
> drivers/messages/i2o and dpt_i2o is redundant or
necessary.
>
This code is very similar to the i2o subsystem, yet it is not the same.
When I get free of my current project I will work on updating this module
(unless someone beats me to it).
Deanna
> This code is very similar to the i2o subsystem, yet it is not the same.
> When I get free of my current project I will work on updating this module
> (unless someone beats me to it).
I'm doing the main i2o code. The main i2o code has lots of problems on non
32bit little endian systems and won't work on 2.5 without a major rework. I'm
doing that work in 2.4 since with 2.4 I at least know that when it dies it
was probably my fault. Until 2.4 is sorted please don't bother with the i2o/*
directory.
The dpt is seperate because it speaks a slightly odd dialect of i2o and the
native driver works nicely. The same is also true for the i2o code hiding
in the Red Creek vpn driver.
Alan