Re: Zoran-0.7a vs Linux Kernel Source Tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Mon, Mar 05, 2001 at 09:09:30AM +0100, Pauline Middelink wrote:
> On Sat, 03 Mar 2001 around 18:05:18 -0800, Jon Pennington wrote:
> 
> The problem is that those saa7110 and prob. adv7175 are generic encoder/decoder
> chips which are used in more than one driver (my own zr36120 zoran driver for
> example). Just binding them tight to some driver and just forgetting about
> the other drivers is not very nice...

That's not what I mean at all.  You would not bind the saa and adv modules to a particular zoran driver; if the zoran driver(s) were selected, each of them would be built.  That way, each and every one would be availale at load-time, and the `master' module (dc10, buz, zr36120, etc) would load any other module it wanted automagically.
 
> And, to be honest, doing a few post-install's in the conf.modules file
> will help you do just that, 'modprobe buz' and be done with it. Yes, i
> know, somebody would need to put it in the conf.modules file, but that
> why there are README's and INSTALL's :)

This goes beyond the modules.conf file; with that file, the user (admin) still needs to know which modules to load, what order to load them in, and other such things.  My (half-cocked ;) idea would mean that you'd have all necesessary modules built at compile-time:

adv7175.o  bt856.o    saa7110.o  saa7185.o
bt819.o    i2c-old.o  saa7111.o  zoran.o

And you'd have several virtual modules:

buz.o      zr36057.o  zr36120.o
dc10.o     lml33.o    (etc.)

When dc10.o is loaded, the only code that module actually contains is a list of modules needed to /actually/ operate a dc10:

Module                  Size  Used by
dc10			1024   0
zoran                  81200   1  [dc10]
adv7175                 2496   1  [dc10]
saa7110                 2752   1  [dc10]
i2c-old                 3936   4  [dc10 zoran adv7175 saa7110]
videodev                4512   1  [dc10 zoran]

Does this make sense?  Yes, modules.conf /can/ do the work, but that's cumbersome.  It breeds a broader/deeper knowlege of the system into a hobbyist like myself, but it's also intimidating and frustrating.

Anyway, this thread has gone on too far.  Wolfgang is getting the Unified driver into shape now, and it may be merged some time in this Millenia ;).  By the way, Pauline, how's your 36120 driver coming along?  I still have that Genious board sitting next to my desk, but I don't have fast enough disks to capture full framerate from it.  I'm still interested in seeing it work with Linux ;).

-- 
-=|JP|=-    "This space intentionally left blank."
Jon Pennington          | Debian 2.4                 -o)
dren@xxxxxxxxxxxxxxxxxx | Auto Enthusiast            /\\
Kansas City, MO, USA    | Proud Husband and Father  _\_V





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux