From: Woody Suwalski on 12 Jul 2010 09:40 Lee Jones wrote: > Please find attached a patch which rectifies the following bug. > > When CUPS loads, it tries to load several drivers that it may need. > When one of these drivers, specifically parport_pc is loaded on ARM > based systems, it causes a segmentation fault as the address is not > writable on non-PC based architectures. This code prevents this > driver from being compiled on said architectures. > > Kind regards, > Lee > Not exactly true. Netwinders based on Armc4l SA110 have implemeted Parallel port hardware. It can be used for PP-CDroms and (of course) printing. I do not claim that the platform is of a great importance anymore, but blanket statements to remove RTC or PPort or KBD from ARM are not correct... Woody -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Randy Dunlap on 12 Jul 2010 14:40 On Mon, 12 Jul 2010 13:14:21 +0100 Lee Jones wrote: > Please find attached a patch which rectifies the following bug. > > When CUPS loads, it tries to load several drivers that it may need. > When one of these drivers, specifically parport_pc is loaded on ARM > based systems, it causes a segmentation fault as the address is not > writable on non-PC based architectures. This code prevents this > driver from being compiled on said architectures. Do you have any specific information on where the segfault occurs? and please read <kernel-source-tree>/Documentation/SubmittingPatches and possibly Documentation/email-clients.txt . thanks, --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: workqueue: fix locking in retry path of maybe_create_worker() Next: NOTICE! |