On Thu, Jun 24, 2010 at 02:54:18PM -0700, StephanT wrote: > > > > > You shouldn't need to do anything other than the "normal" 2.4 to 2.6 porting. > > > > I don't know what this "normal" implies. Hence my question. > > I don't know what problems you are having, hence my question :) > > Yet is clearly stated in the subject line. Specifics please. Error messages? Lines you are having problems with? Your Subject is very generic. Depending on your code, you might just have to delete a single line and that's it. Or you might have to create a whole class and/or bus subsystem and add devices to it. It all depends on your code. > --------------------------------------------------- > > > Ok, feel free to ask questions. > > Here it is: Besides the pointer Arun already sent me do you know of another > guide "How to port linux drivers from 2.4 to 2.6." ? It all depends on the code and what you are doing. You are trying to get a simple summary for updating some unknown code, to a codebase that has evolved by many hundreds of thousands of changes, contributed by many thousands of different people, for over 8 years. That's pretty hard to guess at :) > > But your drivers can get merged, there's no reason to keep them out of > > the tree anymore, we'll take anything :) > > Knowing that: > > 1. If we migrate to 2.6.xx we are going to stay with this 2.6.xx for the next > 10 years as we stuck to 2.4.18 for the last 10. This is one shot action. We > just cannot afford to keep up to date with linux kernel. Then get it in the kernel tree and they will be updated automatically as stuff changes. > 2. The drivers have no practical interest for anyone as they are targeted to > embedded H/W. Ah, so you are thinking you are unique and special, just like everyone else, right? Hint, there's not many "unique" things out there, odds are your code is useful to others, or perhaps, it could be merged with existing drivers. > 3. The merge process is not free for us - we'll have to invest an undetermined > amount of man-hours. Sure, and again, I, and many others, are willing to help out with this for free. > Give me one good reason we would be interested having our stuff in the tree. See above, and the many other places this is documented in much more detail. > --------------------------------------------------- > > > > For cases like ours would be very, very useful if you, guys would update > > > and print LDD V4. > > > The wheels on this are slowly moving, but it will be a long time. > > Could you, please give a rough estimate ? And I reiterate the affirmation > I made above. Nope, sorry, I can not give any specifics at this time, they are just too unknown. Again, just post your code please. Many more questions can be answered then. thanks, greg k-h -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
