From greis@sel.eesc.usp.br  Fri May 28 22:41:54 2004
From: greis@sel.eesc.usp.br (Gilson Reis)
Date: Fri May 28 22:59:39 2004
Subject: [pxc] pxc debian
Message-ID: <001101c444f4$3b748ee0$70eb6b8f@karmina02>


Hi.

               I use Linux (Debian)  and I want use pxc200f, but don't know begin. If you can help me, I would like know with acquire the packages, install and use.

 

Thank you.



Gilson Reis

%%%%%%%%%%%%%%%%%%%%%%%%%
     LASI - Laborat?rio de Sistemas Inteligentes
         Departamento de Engenharia El?trica
         Escola de Engenharia de S?o Carlos
           UNIVERSIDADE DE S?O PAULO
                          SP - BRASIL
%%%%%%%%%%%%%%%%%%%%%%%%%

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux.it/pipermail/pxc/attachments/20040528/07cfef17/attachment.html
From rubini@ar.linux.it  Sat May 29 08:18:37 2004
From: rubini@ar.linux.it (Alessandro Rubini)
Date: Sat May 29 08:05:04 2004
Subject: [pxc] pxc debian
In-Reply-To: <001101c444f4$3b748ee0$70eb6b8f@karmina02>
References: <001101c444f4$3b748ee0$70eb6b8f@karmina02>
Message-ID: <20040529061837.GA22152@mail.gnudd.com>


Hello.

>                I use Linux (Debian)  and I want use pxc200f, but don't 
> know begin. If you can help me, I would like know with acquire the 
> packages, install and use.

Get the pxc package from ftp.linux.it/pub/People/rubini/pxc . Please
get the latest CVS snapshot, as I've now been able to finalize a release
in a while. Hope to to that soon, though, as I've some new material
to add to the package.

The full release includes a ps and pdf manual, the snapshot only the
source code (if you have TeX installed, running "make" will compile the
documentation to ps and pdf).

Hope this helps
/alessndro
-- 
Alessandro Rubini, free software specialist.
Device drivers, embedded systems, courses.
http://ar.linux.it/
From Michael.Belisle@asu.edu  Sun May 30 12:33:33 2004
From: Michael.Belisle@asu.edu (Michael Belisle)
Date: Sun May 30 12:33:39 2004
Subject: [pxc] A couple issues.
Message-ID: <32263B5BB965354B9FA486F9D4BC745D04DD23B5@ex3.asurite.ad.asu.edu>

I installed the PXC200 snapshot 040303 driver on RedHat 8.0 running Linux kernel 2.4.20-20.8 and gcc 3.2.  I'm not going to claim not I understand the steps I took to get to the point I'm at.

I first encountered a compilation problem in the dma.c file:

	dma.c:348: too few arguments to function `remap_page_range'

Searching around on google found a similar problem and patch at: http://www.cs.helsinki.fi/linux/linux-kernel/2002-03/1263.html.

I changed line 358 of dma.c from
	if (remap_page_range(vma->vm_start, physical, vsize, vma->vm_page_prot))
to
	if (remap_page_range(vma, vma->vm_start, physical, vsize, vma->vm_page_prot))

based on the aforementioned patch.  The compilation then managed to finish. I also noticed that on another linux machine running Linux 2.4.7-10 and RedHat 7.3, remap_page_range in mm.h does indeed have one fewer argument:

2.4.7-10, mm.h.440: extern int remap_page_range(unsigned long from, unsigned long to, unsigned long size, pgprot_t prot);

2.4.20, mm.h:577: extern int remap_page_range(struct vm_area_struct *vma, unsigned long from, unsigned long to, unsigned long size, pgprot_t prot);

After configuring my kernel's memory usage to open 5MB of memory and loading the module, I tried to run pxc_xgrab.  The produced video image is only horizontal lines of gibberish.  The steps I took to try to fix this are:

1.) Verified IRQ correlation between /proc/pci and /proc/interrupts.  Initially, the PXC200 was sharing an IRQ with the USB bus, and didn't show up in /proc/interrupts.  I tried moving it to a different PCI slot and it then showed up on its own interrupt in /proc/interrupts.  The PXC200 now shows up in /proc/interrupts, and has the same IRQ in each file.

2.) Tried a different PXC200.

3.) Tried using pxc_control to change the video format, and the mux.

4.) Tried it with and without the camera connected.

5.) Compiled, installed, and susequently uninstalled pacco.

None of these had any effect.  Any further ideas?

Thanks,

Michael J. Belisle
Arizona State University
Flight Research Center
Michael.Belisle@asu.edu
http://frc.asu.edu/
From rubini@ar.linux.it  Sun May 30 16:23:19 2004
From: rubini@ar.linux.it (Alessandro Rubini)
Date: Sun May 30 16:09:32 2004
Subject: [pxc] A couple issues.
In-Reply-To: <32263B5BB965354B9FA486F9D4BC745D04DD23B5@ex3.asurite.ad.asu.edu>
References: <32263B5BB965354B9FA486F9D4BC745D04DD23B5@ex3.asurite.ad.asu.edu>
Message-ID: <20040530142319.GA11158@mail.gnudd.com>


Hello

> 	dma.c:348: too few arguments to function `remap_page_range'

This is a redhat-specific issue. While looking in the 2.4 patches (and
not finding the extra argument anywhere) I found sis_main.c that
explicitly mentions it.

But this is an issue with 2.6 too, so I'll need to add a hack there.
Meanwhile, I'd better not support the redhat variant. If you want
to suggest a not for the manual, I'll gladly apply your patch.

> After configuring my kernel's memory usage to open 5MB of memory and
> loading the module, I tried to run pxc_xgrab.  The produced video
> image is only horizontal lines of gibberish.

According to the pattern you get, you can see whether DMA takes place
or not. If you try "cat /dev/pxc0pgm | od -t x1" you can see that. If
no DMA happens, you'll see a repeating test string (as defined
in allocator.c).

> 1.) Verified IRQ correlation between /proc/pci and /proc/interrupts.
> Initially, the PXC200 was sharing an IRQ with the USB bus, and
> didn't show up in /proc/interrupts.

It should show up only then the device is in use (for example, try
sleep 10000 < /dev/pxc0). And sharing should not be a problem (i.e.,
I think it's supported fine).

> I tried moving it to a different PCI slot and it then showed up on
> its own interrupt in /proc/interrupts.  The PXC200 now shows up in
> /proc/interrupts, and has the same IRQ in each file.

Ok
 
> 2.) Tried a different PXC200.

They usually work. But good you tried it; last year I got a bugged
board and lost a few months trying to find the bug in my driver,
before I finally got my hands on another identical card and found the
bug was in the hardware (then I had to wait another few months before
the italian dealer got it replaced).

> 3.) Tried using pxc_control to change the video format, and the mux.

When the video format is wrong, you see the image moving on the
screen but line length is wrong. About the mux, you can use the "More"
button in pxc_live.

> 4.) Tried it with and without the camera connected.
> 
> 5.) Compiled, installed, and susequently uninstalled pacco.

Not an issue, really.

I'm interested in whether interrupts flow in or not. Is the counter 
in /proc/interrupts increasing? (yes, avoiding a shared IRQ line is good
to this aim) -- but I suppose it does, or the read() system call will
block.

Another idea is compiling with DEBUG=y in the environment (or "make"
command line), and seeing in the kernel messages if something interesting
shows up.

/alessandro
