Re: [GATOS]AIW Radeon 7500 - no capture support

[Matt H. <mat...@my...>]

One additional comment.  If instead of clicking the record button in avview, 
if I instead just cat /dev/video>video.raw, I see the same symptoms -- very 
little data gets captures, and the same messages about the queue being full 
show up in the syslog.

-Matt

On Saturday 27 September 2003 21:42, Matt Hamilton wrote:
> I have changed the order to have km load at boot time, so it comes before
> DRM; and I have disabled DRM completely.  Here is the /proc/interrupts with
> DRM disabled...
>            CPU0
>   0:      22268          XT-PIC  timer
>   1:        609          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   5:          0          XT-PIC  ehci-hcd
>   8:          1          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  10:      74265          XT-PIC  usb-uhci, VIA8233
>  11:        260          XT-PIC  usb-uhci, usb-uhci, eth0, km_ati (Radeon)
>  12:       3429          XT-PIC  PS/2 Mouse
>  14:      15688          XT-PIC  ide0
>  15:         61          XT-PIC  ide1
> NMI:          0
> LOC:      22228
> ERR:         22
> MIS:          0
>
> ... and with km loaded at boot time, before DRM ...
>            CPU0
>   0:       9960          XT-PIC  timer
>   1:        163          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   5:          0          XT-PIC  ehci-hcd
>   8:          1          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  10:       1026          XT-PIC  usb-uhci, VIA8233
>  11:        247          XT-PIC  usb-uhci, usb-uhci, km_ati (Radeon), eth0,
> radeon@PCI:1:0:0
>  12:        399          XT-PIC  PS/2 Mouse
>  14:      14799          XT-PIC  ide0
>  15:         61          XT-PIC  ide1
> NMI:          0
> LOC:       9921
> ERR:          2
> MIS:          0
>
> Both cases yield same results.  This is km from CVS, and I get no video
> frames recorded at all or very few.  When I had km loaded before DRM, I did
> manage to get about 6 frames captured in 30-60 seconds.  I was monitoring
> the syslog during that time, and I saw several messages such as the
> following:
>
> Sep 27 21:35:19 hamilton kernel: km: GUI_DMA queue (size=10) is full
> first=4 last=3 flag=0x80000001
>
> The first & last values varied, but there were many of those messages. 
> Also, upon startup of avview, I found the following messages curious -- do
> these have anything to do with it or is that just a standard scan of the
> most commonly used video channels?  Obviously /dev/video0 exists, but
> video[1-7] do not.
>
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-1
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-2
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-3
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-4
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-5
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-6
> Sep 27 21:34:28 hamilton modprobe: modprobe: Can't locate module
> char-major-81-7
>
> -Matt
>
> On Thursday 25 September 2003 06:36, Vladimir Dergachev wrote:
> > Well, it should be no problem for km to share interrupts, except for
> > another driver accessing the same hardware. Try to change the order in
> > which drivers are loaded, i.e. try to load km after DRM driver or vice
> > versa or simply try to prevent DRM driver from loading.
> >
> >                          best
> >
> >                             Vladimir Dergachev