From: Serguei M. <mi...@ci...> - 2001-06-26 18:23:36
|
Alan Cox wrote: > > That's OK with me. However, for consistency reasons, I would prefer to see current > > zoran.o as zr36120.o ;-) > > That would confuse zoran.o users somewhat 8) Hmm... Shall we count how many of users have zr36120 and zr36067? ;-) Anyway, making names more specific will prevent future confusing... We already changed buz.c to dc10.c, then to zoran.c. Now, in your kernel series it is zr36067.c, though, I would call it as zr360x7, since it covers zr36057 and zr36067 chips. However, this is also wrong, because current driver supports combination of zr36060 and zr360x7. If Wolfgang Scherr includes support for DC30(plus) then it will also cover zr36050+zr36015 with zr360x7... Wolfgang, any success for now? So, probably, the best name for the module is something like zrmjpeg or zr360XX_mjpeg or zr_mjpeg... Any other ideas? I hope next major driver release will have modular (OO?) design and some parts (like buffer allocation, hardware abstraction layer, different API layers for V4L, V4L2, and may be some other streaming API - who knows?) may be imported or exported from/to other drivers. Well, I'm just dreaming ;-) Nevertheless, the main module name should remain. So, I would like to see some ideas in that respect. Serguei. |