On Tue, 14 Dec 1999, Alan Cox wrote:
> Taking my working list the key items seem to be
>
> About 70% of device drivers dont have the setup code fixed. In many cases that
> makes them unusable non modular
What kind of work is this? If it's pretty simple stuff, just repetitive,
I may be able to help out. Got an example of before/after? Or at least let me
know of a driver that has been 'properly' updated so I have something to work
from? I'll try and look at some of the code, I'm pretty good at C, but not too
terribly familiar w/ kernel internals (yet. :) ).
Stephen
- Re: Ok, making ready for pre-2.4 and code-freeze.. Alexander Viro
- Re: Ok, making ready for pre-2.4 and code-freeze.. Alan Cox
- Re: Ok, making ready for pre-2.4 and code-freeze.... Alexander Viro
- Re: Ok, making ready for pre-2.4 and code-fre... Alan Cox
- Re: Ok, making ready for pre-2.4 and code... Alexander Viro
- Re: Ok, making ready for pre-2.4 and... Neil Brown
- Re: Ok, making ready for pre-2.4 and code-fre... Neil Brown
- Re: Ok, making ready for pre-2.4 and code-freeze.... Stephen Frost
- Re: Ok, making ready for pre-2.4 and code-freeze.... Alexander Viro
- Re: Ok, making ready for pre-2.4 and code-freeze.... Pavel Machek
- Re: Ok, making ready for pre-2.4 and code-fre... Alan Cox
- Re: Ok, making ready for pre-2.4 and code... David Weinehall
- Re: Ok, making ready for pre-2.4 and code-freeze.... Ingo Molnar
- Re: Ok, making ready for pre-2.4 and code-freeze.. Jes Sorensen
- Re: Ok, making ready for pre-2.4 and code-freeze.... Alexander Viro
- Re: Ok, making ready for pre-2.4 and code-freeze.. Jan Kara
- Re: Ok, making ready for pre-2.4 and code-freeze.... Alexander Viro
