buz.c of 2.4.4

buz.c of 2.4.4

[Byeong-ryeol Kim]

I met follwing erros which was workarounded by put
define KMALLOC_MAXSIZE	131072
borrowed from af_unix.c of 2.4.3-ac14. But I'm convinced of this.
below lines were wrapped by me for readabilities' sake.
....
-D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 \
-march=k6 -DMODULE -DMODVERSIONS -include \
/usr/src/linux-2.4.4/include/linux/modversions.h   -c -o buz.o buz.c
buz.c: In function `v4l_fbuffer_alloc':
buz.c:188: `KMALLOC_MAXSIZE' undeclared (first use in this function)
buz.c:188: (Each undeclared identifier is reported only once
buz.c:188: for each function it appears in.)
buz.c: In function `jpg_fbuffer_alloc':
buz.c:262: `KMALLOC_MAXSIZE' undeclared (first use in this function)
buz.c:256: warning: `alloc_contig' might be used uninitialized in this function
buz.c: In function `jpg_fbuffer_free':
buz.c:322: `KMALLOC_MAXSIZE' undeclared (first use in this function)
buz.c:316: warning: `alloc_contig' might be used uninitialized in this function
buz.c: In function `zoran_ioctl':
buz.c:2837: `KMALLOC_MAXSIZE' undeclared (first use in this function)
make[3]: *** [buz.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.4/drivers/media/video'
make[2]: *** [_modsubdir_video] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.4/drivers/media'
make[1]: *** [_modsubdir_media] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.4/drivers'
make: *** [_mod_drivers] Error 2
....

RE: buz.c of 2.4.4

[Ronald Bultje]

Hi,

>I met follwing erros which was workarounded by put
>define KMALLOC_MAXSIZE	131072
>borrowed from af_unix.c of 2.4.3-ac14. But I'm convinced of
>this.
>below lines were wrapped by me for readabilities' sake.

my fix in an earlier e-mail to the list explained that the
proper way of fixing it is indeed to add the line.
#define KMALLOC_MAXSIZE (1024*128)

But in case you're actually going to _use_ this module, i.e.
you have a buz card, then please use the unified zoran driver
by Serguei Miridonov instead.
You can find more information about this driver on:
http://www.cicese.mx/~mirsev/Linux/DC10plus or
http://mjpeg.sourceforge.net/ (also for our mailinglists)
The old driver is (doh!) old and unmaintained. Might have
some bugs slipped into it since there is no maintainance done
anymore. The new driver is actively being maintained and
capturing software from our project is optimized for the new
driver (though the old one should still work).

--
Ronald Bultje

Re: buz.c of 2.4.4

[Alan Cox]

> I met follwing erros which was workarounded by put
> define KMALLOC_MAXSIZE	131072
> borrowed from af_unix.c of 2.4.3-ac14. But I'm convinced of this.
> below lines were wrapped by me for readabilities' sake.

Buz.c doesnt work build or anything. Once the zoran merge is done it will
go away, until then I simply dont care.  At least its obviously broken right
now

Re: buz.c of 2.4.4

[Mohammad A. Haque]

On Mon, 30 Apr 2001, Alan Cox wrote:

> Buz.c doesnt work build or anything. Once the zoran merge is done it will
> go away, until then I simply dont care.  At least its obviously broken right
> now

Can't we just remove it then?

Come to think of it .. then we'd start getting "buz drivers missing"
reports.
-- 

=====================================================================
Mohammad A. Haque                              http://www.haque.net/
                                               mhaque@haque.net

  "Alcohol and calculus don't mix.             Project Lead
   Don't drink and derive." --Unknown          http://wm.themes.org/
                                               batmanppc@themes.org
=====================================================================

Re: buz.c of 2.4.4

[Ronald Bultje]

On 2001.04.30 20:37:39 +0200 Mohammad A. Haque wrote:
> On Mon, 30 Apr 2001, Alan Cox wrote:
> 
> > Buz.c doesnt work build or anything. Once the zoran merge is done it
> will
> > go away, until then I simply dont care.  At least its obviously broken
> right
> > now
> 
> Can't we just remove it then?
> 
> Come to think of it .. then we'd start getting "buz drivers missing"
> reports.

So what?
Refer them to mjpeg-users@lists.sourceforge.net and we'll explain them how
to use the new zoran driver until it's in the official kernel...
I mean, it be worse if they _used_ the old buz-thing, they'd start bugging
you with "how do I fix it?"

A broken driver in the kernel basically means a broken kernel - so it'd be
better to just remove it I guess... What do you think, Alan?

--
Ronald Bultje

Re: buz.c of 2.4.4

[Gerd Knorr]

> > Come to think of it .. then we'd start getting "buz drivers missing"
> > reports.
> 
> So what?
> Refer them to mjpeg-users@lists.sourceforge.net and we'll explain them how
> to use the new zoran driver until it's in the official kernel...

#warning "outdated, see http://whatever for current devel versions"

  Gerd

-- 
Man muß die Software wacker hüten
weil in der Welt die Hacker wüten