From robert@schwebel.de  Wed Aug  2 22:09:30 2000
Date: Wed, 2 Aug 2000 23:09:30 +0200 (CEST)
From: Robert Schwebel robert@schwebel.de
Subject: [Pxc] Problems with allocator

Hi!

Just a few words to introduce myself: I'm working for Zeutec
Opto-Elektronik, a small german company making optical measurement systems
(video and spectroscopy) for customers from chemical and other industry.

Today I finally got a PXC200 :-), so I did some first tests with this
driver. Unfortunately, there seems to be a problem with the allocator
module. I've set the LILO append variable to 126 MB (128 in system), but
the pxc_load script and the syslog claim not to find the memory.

In the beginning when I got the machine I had some problems with stability
which came from a BIOS bug. My BIOS obviously tells Linux the incorrect
memory size during the bootup sequence, so I had to add "mem=128M" to the
LILO line before. Afterwards everything was fine.

Now I had to change this line to get my two megabytes for allocator; my
only idea now is that allocator could use the same mechanisms to determine
how much RAM is available as the kernel was using before and therefore
fails. As I didn't have a closer look at the sources this could be
terribly wrong - so perhaps anyone of you does have an idea what the
reason for the failiure could be?

If it's needed I'll send more detailed log messages tomorrow.

Bye,
Robert
-- 
 +----------------------------------------------------------------------+
 I Dipl.-Ing. Robert Schwebel, Luedemannstrasse 25, 24114 Kiel, Germany I
 I Phone +49-431-6794138 Fax +49-431-6794139 email: robert@schwebel.de  I
 +----------------------------------------------------------------------+





From r.schwebel@zeutec.de  Thu Aug  3 12:12:23 2000
Date: Thu, 03 Aug 2000 13:12:23 +0200
From: Robert Schwebel r.schwebel@zeutec.de
Subject: [Pxc] Problems with allocator

Hi!

Robert Schwebel wrote:
> Unfortunately, there seems to be a problem with the allocator
> module. 

Sometimes things are so easy... I just found out I forgot to run lilo
after changing the configuration #-) Anyway, now you know I'm here and
I'm sure you'll get other stupid questions from here :-)

Cheerio,
Robert
-- 
    _
   / \     _    Dipl.-Ing. Robert Schwebel        r.schwebel@zeutec.de
--/   \   / \/--------------------------------------------------------
       \_/      ZEUTEC Opto-Elektronik GmbH              www.zeutec.de
                Kieler Str. 211, 24786 Rendsburg, Germany
                Phone: +49-4331-136-653   Fax: +49-4331-136-651

+++ Neue Adresse! +++ New Address! +++ Neue Adresse! +++ New Address!
++++




From marius@e.co.za  Thu Aug  3 12:45:22 2000
Date: Thu, 03 Aug 2000 13:45:22 +0200
From: Marius van Wyk marius@e.co.za
Subject: [Pxc] Introduction.

Hello.

Since everyone else is doing it, let me introduce myself:

My name is Marius van Wyk, I started working on the PXC-200 card on the
Windows platform, using it to capture unsynced imaged that are being
switched on a single input. The PXC-200 card garanteed to sync in two
fields (quite impressive) unlike other cards I have worked with (Matrox
Meteor and VB IE500).

I'm curently working in a corporate bank as a C++ programmer, but still =
do
part-time work for the Security firm.

I am also a Director and Shareholder of a Medium IT firm, and am =
sponsoring
a largish open-source project: A RAD GUI IDE for Python.

http://boa-constructor.sourceforge.net/

Another reason I went for the PXC-200 was the mention of the then-to-be
linux support. (I only recently ported it to Linux)

I used this in a Video Surveilance subsystem of a access-control system
which I am writing on a Dual-win32 and Linux platform.

I've written most of the server-oriented modules for Linux, and only the
user-interface (and HASP dongle support) for win32. (networked via TCP/IP
sockets)

I have completed the Video server recently, and would not mind sharing my
insights to anyone wanting to integrate the framgrabber closely with the
latest jpeg lib. (I can compress while grabbing, which is a whole lot
better than the windows mechanisms)

I have written a JPEG wrapper C++ class, and would not mind sending this =
to
anyone who would need the information. I think Allesandro has given a lot
to the open source community, and has inspired me to help as much as I =
can
to give something back.

Regards, and keep well.

Marius.




From rubini@gnu.org  Fri Aug  4 13:04:03 2000
Date: Fri, 4 Aug 2000 14:04:03 +0200
From: Alessandro Rubini rubini@gnu.org
Subject: [Pxc] Problems with allocator

Hi.

I've been away for ten days or so. Now I'm back.

> I'm sure you'll get other stupid questions from here :-)

Feel free to ask.

>From your previous message:

> In the beginning when I got the machine I had some problems with stability
> which came from a BIOS bug. My BIOS obviously tells Linux the incorrect
> memory size during the bootup sequence, so I had to add "mem=128M" to the
> LILO line before. Afterwards everything was fine.
> 
> Now I had to change this line to get my two megabytes for allocator; my
> only idea now is that allocator could use the same mechanisms to determine
> how much RAM is available as the kernel was using before and therefore
> fails.

I never looked at how the kernel does it. The allocator just tries to
write and read data after the end of memory as reported by the
kernel. So it should work (and actually it works, as reported by your
later message).

/alessandro




