From: Michael R. <re...@eu...> - 2002-03-18 06:23:24
|
kifo schrieb: > > I think a kernel module offering a chardevice is much more flexible, > because it can be accessed by a simple perl- or shellscript. There is no > need of big programs around. You simply write on the device to display. > > Am Sam, 2002-03-16 um 19.30 schrieb Herbert Rosmanith: > > > We developed a nice chardriver for M50530 controlled displays leaned on > > > Michael McLellan's lcdmod (which is for HD44780). It is quite compatible > > > > just a question, but why would one want to have a kernel-module if one > > can do it in user-space? or is there something particular about the > > m50530? I agree with both of you. There are several reaons for and against a kernel module. Each approach has is advantages and disadvantages. We decided to do user-space programming with lcd4linux because of - you'd need a kernel module for each display - kernel modules must mach the running kernel (lcd4linux needs not) - linux offers lots of low-level access methods to the parallel port (the ppdev interface), so the display programming within lcd4linux is quite "high-level" bye, Michael -- netWorks Vox: +43 316 698260 Michael Reinelt Fax: +43 316 692343 Geisslergasse 4 GSM: +43 676 3079941 A-8045 Graz, Austria e-mail: re...@eu... |