> > Ultimatly this is the goal. That is what the struct xxx_par is for in > > struct fb_info. It is the core driver private data that can be shared by > > everyone. Ben would you mind if I reworked your code to have this "core". > > It will take me some time but I can have it working. I need to do some > > fixes for multiple monitor handling anyways. > > Wait, wait ... there is already Jon working on the driver, and I plan to > include part of his recent work along with some initial dual head > support soon, let's avoid having too many people working at the same > time on it.
I have seen his patches. He post them:-) The way it is being done is not according to the fbev api spec. I like to see it done right. Alot of drivers never where ported properly to the new api. People ported as fast as they could instead of properly. > Also, with the merge DRM/fbdev, this will become a non-issue, wether the > ioctl comes from DRM or fbdev, we'll be able to do the right thing. Ture but that is down the road. The idea is to share the par between the two different systems. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
