From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Memory problem with bttv driver
Date: Tue, 15 Jan 2002 00:42:05 +0100 [thread overview]
Message-ID: <20020115004205.A12407@werewolf.able.es> (raw)
In-Reply-To: <20020114210039.180c0438.skraw@ithnet.com> <E16QETz-0002yD-00@the-village.bc.nu>
In-Reply-To: <E16QETz-0002yD-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on lun, ene 14, 2002 at 22:17:31 +0100
On 20020114 Alan Cox wrote:
>> Ok. So what do we do about it? I mean there are possibly some more people out
>> there with such a problem, or - to my prediction - there will be more in the
>> future. I see to possibilities:
>> 1) simply increase it overall. I have not the slightest idea what the drawbacks
>> are. 2) make it configurable (looks like general setup to me).
>
>Making it bigger reduces that amount of ram directly mapped by the kernel
>which hits performance (nastily for 2.4 not so bad for 2.5)
(Sorry for joning so late to the thread...)
It is wokring fine for me, under 2.4.18-pre3 + NVidia. The difference is
that I am using version 0.7.87 (see http://giga.cps.unizar.es/~magallon/linux/2.4.18-pre3/)
I have just checked the bttv page (http://bytesex.org/bttv/) and there is
a newer version (0.7.88). What comes in .17 is 0.7.83. I have not
noticed anything relevant in changelog, but you can try...
lsmod:
werewolf:~# lsmod
Module Size Used by Tainted: P
tuner 8548 1 (autoclean)
tvaudio 9312 0 (autoclean) (unused)
msp3400 14768 1 (autoclean)
bttv 63424 0 (autoclean)
i2c-algo-bit 7244 1 (autoclean) [bttv]
videodev 4960 3 (autoclean) [bttv]
emu10k1 57728 1
sound 55052 0 [emu10k1]
ac97_codec 9472 0 [emu10k1]
soundcore 3524 7 [emu10k1 sound]
serial 45792 7
isa-pnp 28968 0 [serial]
w83781d 17792 0 (unused)
i2c-proc 6112 0 [w83781d]
i2c-isa 1188 0 (unused)
i2c-piix4 3908 0 (unused)
i2c-core 13408 0 [tuner tvaudio msp3400 bttv i2c-algo-bit w83781d i2c-proc i2c-isa i2c-piix4]
NVdriver 821600 14
agpgart 17024 3
ne2k-pci 4960 1
8390 6608 0 [ne2k-pci]
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre3-beo #5 SMP Sun Jan 13 02:14:04 CET 2002 i686
next prev parent reply other threads:[~2002-01-14 23:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 17:12 Memory problem with bttv driver Stephan von Krawczynski
2002-01-14 17:40 ` Alan Cox
2002-01-14 17:43 ` Stephan von Krawczynski
2002-01-14 17:56 ` Alan Cox
2002-01-14 18:38 ` Stephan von Krawczynski
2002-01-14 19:48 ` Stephan von Krawczynski
2002-01-14 20:03 ` Alan Cox
2002-01-14 20:00 ` Stephan von Krawczynski
2002-01-14 21:17 ` Alan Cox
2002-01-14 23:42 ` J.A. Magallon [this message]
2002-01-15 10:17 ` Gerd Knorr
2002-01-15 11:14 ` Stephan von Krawczynski
2002-01-15 13:20 ` Gerd Knorr
2002-01-15 13:46 ` Stephan von Krawczynski
2002-01-15 15:16 ` Gerd Knorr
2002-01-15 16:35 ` Stephan von Krawczynski
2002-01-16 9:57 ` Gerd Knorr
2002-01-16 17:24 ` Stephan von Krawczynski
[not found] <Pine.LNX.4.21.0201142245040.2118-100000@localhost.localdomain>
2002-01-15 1:55 ` Stephan von Krawczynski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020115004205.A12407@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox