On Wed, Jun 23, 2010 at 03:54:56PM -0700, StephanT wrote: > > > >What type of "devfs driver"? > character > > > 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 :) > > Do you have a pointer to the driver you need to have ported? > No. If there is interest I can make them public. Please do. > > People will do this work for you, have you seen the linuxdriverproject.org site? > No I haven't seen this site. This would be very nice :-) , but I don't think is > doable. > > Short story: We are using linux 2.4.18 on SH4 architecture. Very specific H/W > and very different from PC. Linux is used as configuration manager and user > interface (web). All linux drivers are simple char drivers - mainly to get access > to FPGA and DSP. Most of them provide a "mmap" interface to user applications. > The original port was done by Montavista. They should have made it public > years ago. Yeah, we all know about how well Montavista does when it comes to hiding source, they are wonderful at that :( > We are looking what would cost to migrate to 2.6. Boss asked for an effort > estimation and I had to start from some point. The pointer I got from Arun > cleared the way for me to get some numbers. Most of the migration cost is > not in driver port but in how we are going to handle a mixed installed > base. > > Related the the "Linux Driver Project". This is a very nice and generous idea ! > Not for us - unfortunately. Our work is driven by a schedule. Very tight! We do > not have spare H/W and we are not so rich to pay a person to do interface work. > It is cheaper to do the work by ourselves and we need to learn to be able to > maintain/modify/enhance. Ok, feel free to ask questions. But your drivers can get merged, there's no reason to keep them out of the tree anymore, we'll take anything :) > For cases like ours would be very, very useful if you, guys would update and > print LDD V4. I can guarantee we will buy at least five copies. The wheels on this are slowly moving, but it will be a long time. So, feel free to post the code and we can see how hard it would be to get it up and working on the latest 2.6 kernel? If it's just a char device, it shouldnt' be very hard. 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
