[Please leave me in Cc: as I'm not subscribed to this list] Alan Cox writes: > On Maw, 2005-01-11 at 14:28, Egbert Eich wrote: > > I'm fully aware that in the long run we will need to look into a new > > driver model for graphics where no two instances fight over who gets > > register access. However such a model won't be created nor will we get > > the majority of the drivers ported over night. > > Therefore we need to find an interim solution for the most pressing > > problems. > > This doesn't appear to work as a solution because the functionality > changes won't be in all the existing kernel, and also because the kernel > font save has a couple of bugs reported against it with regards to > saving the right data that might need looking at anyway.
Can you point me to these reports? I tested with a couple chipsets here and didn't find any problems. Maybe we can compare the code in X with the code in the kernel for the amount of data to save. However we don't know if the X font code is completely without problems. I remeber fixing a problem in X years ago - a case where the kernel got it right ;-) X VGA font code involves a lot of magic. Also things might differ slightly form HW vendor to vendor and it will be extremely hard to get it right for all chipset models therefore I would not even talk about 'bugs' ;-) > > It seems it would be neccessary for X to have a way to know whether the > feature is present. > We could check for the kernel version. This could be done during build time - assuming we don't ship generic binaries or during run time if we want to provide binaries that work everywhere. In reality the former would be sufficient for a lot of cases - especially for vendor supplied binaries. Once X.Org starts shipping binaries it should definitely provide a version that fits everywhere. But maybe you have a better suggestion. Anyway, would my patch be acceptable for the kernel? Cheers, Egbert. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/