gatos-devel Mailing List for GATOS
Status: Beta
Brought to you by:
volodya
Menu
▾
▴
gatos-devel — Technical discussions about GATOS drivers and applications
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(229) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(744) |
Feb
(481) |
Mar
(400) |
Apr
(309) |
May
(290) |
Jun
(266) |
Jul
(403) |
Aug
(434) |
Sep
(546) |
Oct
(392) |
Nov
(309) |
Dec
(350) |
| 2003 |
Jan
(318) |
Feb
(339) |
Mar
(436) |
Apr
(269) |
May
(326) |
Jun
(293) |
Jul
(332) |
Aug
(131) |
Sep
(126) |
Oct
(216) |
Nov
(140) |
Dec
(167) |
| 2004 |
Jan
(367) |
Feb
(141) |
Mar
(77) |
Apr
(85) |
May
(100) |
Jun
(98) |
Jul
(79) |
Aug
(87) |
Sep
(96) |
Oct
(185) |
Nov
(105) |
Dec
(112) |
| 2005 |
Jan
(156) |
Feb
(60) |
Mar
(35) |
Apr
(57) |
May
(43) |
Jun
(49) |
Jul
(30) |
Aug
(60) |
Sep
(24) |
Oct
(55) |
Nov
(13) |
Dec
(35) |
| 2006 |
Jan
(50) |
Feb
(22) |
Mar
(24) |
Apr
(35) |
May
(44) |
Jun
(20) |
Jul
(21) |
Aug
(15) |
Sep
(9) |
Oct
(21) |
Nov
(31) |
Dec
(32) |
| 2007 |
Jan
(4) |
Feb
(3) |
Mar
(6) |
Apr
(9) |
May
(15) |
Jun
(15) |
Jul
(14) |
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
(4) |
Dec
(1) |
| 2008 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
(11) |
2
(8) |
3
(14) |
4
(10) |
|
5
(23) |
6
(20) |
7
(10) |
8
(17) |
9
(18) |
10
(16) |
11
(14) |
|
12
(3) |
13
(6) |
14
(9) |
15
(5) |
16
(10) |
17
(4) |
18
(7) |
|
19
(4) |
20
(14) |
21
(21) |
22
(17) |
23
(5) |
24
|
25
(3) |
|
26
(7) |
27
(2) |
28
(11) |
29
(13) |
30
(5) |
31
(11) |
|
|
From: Svetoslav S. <ga...@st...> - 2003-01-31 19:16:00
|
On Fri, 2003-01-31 at 19:27, Svetoslav Slavtchev wrote: > On Fri, 2003-01-31 at 19:11, Vladimir Dergachev wrote: > > On Fri, 31 Jan 2003, Svetoslav Slavtchev wrote: > > > > > Hi , > > > wanted to ask you to take a look at these oopses, > > > > > > dmesg @ http://varna.demon.co.uk/~svetlio/ati.2/RadeonOoopsesDmesg.txt > > > > > > dmesg | ksymoops @ > > > http://varna.demon.co.uk/~svetlio/ati.2/RadeonOopsesKsymoops.txt > > > > > > i was having 2 concurrent X users on my PC > > > until i changed my AGP Matrox G550-DH against Radeon AIW 7500 > > > see http://varna.demon.co.uk/~svetlio/aivils/ > > > or the original site @ http://startx.times.lv > > > > > > but now with the radeon i can not get it working. > > > > > > if both X servers are started at the same time i get the oopses and no > > > DRI on the radeon. > > > > > > if i try to start the second X server later, the Nvidia driver can not > > > start > > > > First of all, it looks like you are using a binary driver.. > > i know, but that's the only way to start nvidia card > in case it slave( selected as primary in the BIOS is the AGP radeon ) > > > > Secondly, the ksymoops output shows that the error was someplace in > > radeon_do_cp_idle. However I do not think the code is wrong there - and it > > is pretty simple so it must be that the argument dev_priv is screwed up. > > > > So you have memory corruption coming from someplace. > > could it be related to high mem - i have here 1024 Mb DDR RAM, could this be related ( see attachment : drm-kernel compile messages) best , svetljo |
|
From: Svetoslav S. <ga...@st...> - 2003-01-31 18:31:30
|
On Fri, 2003-01-31 at 19:11, Vladimir Dergachev wrote: > On Fri, 31 Jan 2003, Svetoslav Slavtchev wrote: > > > Hi , > > wanted to ask you to take a look at these oopses, > > > > dmesg @ http://varna.demon.co.uk/~svetlio/ati.2/RadeonOoopsesDmesg.txt > > > > dmesg | ksymoops @ > > http://varna.demon.co.uk/~svetlio/ati.2/RadeonOopsesKsymoops.txt > > > > i was having 2 concurrent X users on my PC > > until i changed my AGP Matrox G550-DH against Radeon AIW 7500 > > see http://varna.demon.co.uk/~svetlio/aivils/ > > or the original site @ http://startx.times.lv > > > > but now with the radeon i can not get it working. > > > > if both X servers are started at the same time i get the oopses and no > > DRI on the radeon. > > > > if i try to start the second X server later, the Nvidia driver can not > > start > > First of all, it looks like you are using a binary driver.. i know, but that's the only way to start nvidia card in case it slave( selected as primary in the BIOS is the AGP radeon ) > Secondly, the ksymoops output shows that the error was someplace in > radeon_do_cp_idle. However I do not think the code is wrong there - and it > is pretty simple so it must be that the argument dev_priv is screwed up. > > So you have memory corruption coming from someplace. could it be related to high mem - i have here 1024 Mb DDR RAM, and it was working with the G550DH > As for V_BIOS error - I have seen it before, but you better ask people on > xf...@xf.... It could have been fixed in CVS (ati.2 CVS is still > based on 4.2.99.3- code) > i suppose i should try again with the G550DH, and see whether it works with the newer XFree, i've updated several times after i changed to the radeon best, svetljo |
|
From: Vladimir D. <vo...@mi...> - 2003-01-31 18:11:34
|
On Fri, 31 Jan 2003, Svetoslav Slavtchev wrote: > Hi , > wanted to ask you to take a look at these oopses, > > dmesg @ http://varna.demon.co.uk/~svetlio/ati.2/RadeonOoopsesDmesg.txt > > dmesg | ksymoops @ > http://varna.demon.co.uk/~svetlio/ati.2/RadeonOopsesKsymoops.txt > > i was having 2 concurrent X users on my PC > until i changed my AGP Matrox G550-DH against Radeon AIW 7500 > see http://varna.demon.co.uk/~svetlio/aivils/ > or the original site @ http://startx.times.lv > > but now with the radeon i can not get it working. > > if both X servers are started at the same time i get the oopses and no > DRI on the radeon. > > if i try to start the second X server later, the Nvidia driver can not > start First of all, it looks like you are using a binary driver.. Secondly, the ksymoops output shows that the error was someplace in radeon_do_cp_idle. However I do not think the code is wrong there - and it is pretty simple so it must be that the argument dev_priv is screwed up. So you have memory corruption coming from someplace. As for V_BIOS error - I have seen it before, but you better ask people on xf...@xf.... It could have been fixed in CVS (ati.2 CVS is still based on 4.2.99.3- code) best Vladimir Dergachev > > (EE) NVIDIA(0): Cannot read V_BIOS > (EE) NVIDIA(0): Failed to initialize the NVdriver kernel module! > (EE) NVIDIA(0): *** Aborting *** > > > best, > > svetljo > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Gatos-devel mailing list > Gat...@li... > https://lists.sourceforge.net/lists/listinfo/gatos-devel > |
|
From: Svetoslav S. <ga...@st...> - 2003-01-31 17:48:28
|
Hi , wanted to ask you to take a look at these oopses, dmesg @ http://varna.demon.co.uk/~svetlio/ati.2/RadeonOoopsesDmesg.txt dmesg | ksymoops @ http://varna.demon.co.uk/~svetlio/ati.2/RadeonOopsesKsymoops.txt i was having 2 concurrent X users on my PC until i changed my AGP Matrox G550-DH against Radeon AIW 7500 see http://varna.demon.co.uk/~svetlio/aivils/ or the original site @ http://startx.times.lv but now with the radeon i can not get it working. if both X servers are started at the same time i get the oopses and no DRI on the radeon. if i try to start the second X server later, the Nvidia driver can not start (EE) NVIDIA(0): Cannot read V_BIOS (EE) NVIDIA(0): Failed to initialize the NVdriver kernel module! (EE) NVIDIA(0): *** Aborting *** best, svetljo |
|
From: Vladimir D. <vo...@mi...> - 2003-01-31 15:09:11
|
It could be that /dev/dri permissions are screwed up. Try moving this
directory to someplace else - X should create it anew.
best
Vladimir Dergachev
On Fri, 31 Jan 2003, Monari Emanuele wrote:
> Hi all!!!
> I've a radeon 7500 (m7) on my notebook.And I tried to set-up new ati.2
> with 4.2.99.
>
> Worklist:
> Compiled xfree4.2.99: Done.
> Compiled ati.2 from main cvs: Done.
> Compiled drm-kernel from cvs (insmod says version 1.100.0 20021218)
> Installed ati.2 & drm.
>
>
> X is up and working (included consol switching... :) )
> but the 3d acceleration is down. :(
>
> I have failed somewhere or 3d is not already supported on 4.2.99?
> ThankYou!!!!
> E.M.
>
> P.S.: dri section is present on XF86Config file... For 4.2.1 with
> precompiled ati.2 3d works fine with this conf-file....
> The Xfree log says:
>
> [...]
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 6, (OK)
> drmGetBusid returned ''
> (II) RADEON(0): [drm] drmSetBusid failed (6, PCI:1:0:0), Permission
> denied
> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
> [...]
>
> E.M.
> --
> Risparmierei un sacco di tempo se lasciassi perdere tutto e diventassi
> matto adesso.
>
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-31 15:07:23
|
Thanks !!
I am away on a business trip - I'll apply it as soon as I get back.
best
Vladimir Dergachev
On Fri, 31 Jan 2003, Svetoslav Slavtchev wrote:
> hi ,
> could you apply this diff ?
>
> best,
>
> svetljo
>
> ############################
> diff -Naur km.old/km_api.c km/km_api.c
> --- km.old/km_api.c 2003-01-27 19:18:00.000000000 +0100
> +++ km/km_api.c 2003-01-31 12:23:59.000000000 +0100
> @@ -18,6 +18,7 @@
> #include <linux/config.h>
> #include <linux/version.h>
> #include <linux/module.h>
> +#include <linux/kmod.h>
> #include <linux/kernel.h>
> #include <linux/sched.h>
> #include <linux/init.h>
> @@ -469,6 +470,8 @@
>
> printk("Kmultimedia API module version %s loaded\n", KM_API_VERSION);
>
> +request_module("videodev");
> +
> return 0;
> }
>
> diff -Naur km.old/km.c km/km.c
> --- km.old/km.c 2003-01-30 18:36:07.000000000 +0100
> +++ km/km.c 2003-01-31 12:23:08.000000000 +0100
> @@ -18,6 +18,7 @@
> #include <linux/config.h>
> #include <linux/version.h>
> #include <linux/module.h>
> +#include <linux/kmod.h>
> #include <linux/kernel.h>
> #include <linux/sched.h>
> #include <linux/init.h>
> @@ -849,6 +850,9 @@
> }
> }
> if(result<0)printk("km: **** no supported devices found ****\n");
> +
> +request_module("km_api_drv");
> +
> return result;
> }
>
>
>
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-31 15:05:24
|
On Fri, 31 Jan 2003, Ilya Romanenko wrote:
> Shure It really works, but the picture is only 2/3 of the screen.
> It works but unusefull !
2/3 ?? Which mode are you using ? In my experience the TV display was ok,
there were some black borders which vary from TV to TV but not very large.
best
Vladimir Dergachev
>
> |You could use vesa framebuffer and let bios set up everything, but this
> |will display the same picture on both TV and the monitor.
> |
> | best
> |
> | Vladimir Dergachev
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
|
|
From: Monari E. <em...@li...> - 2003-01-31 14:23:27
|
Hi all!!! I've a radeon 7500 (m7) on my notebook.And I tried to set-up new ati.2 with 4.2.99. Worklist: Compiled xfree4.2.99: Done. Compiled ati.2 from main cvs: Done. Compiled drm-kernel from cvs (insmod says version 1.100.0 20021218) Installed ati.2 & drm.=20 X is up and working (included consol switching... :) )=20 but the 3d acceleration is down. :( I have failed somewhere or 3d is not already supported on 4.2.99? ThankYou!!!! E.M. P.S.: dri section is present on XF86Config file... For 4.2.1 with precompiled ati.2 3d works fine with this conf-file.... The Xfree log says: [...] drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 6, (OK) drmGetBusid returned '' (II) RADEON(0): [drm] drmSetBusid failed (6, PCI:1:0:0), Permission denied (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. [...] E.M. --=20 Risparmierei un sacco di tempo se lasciassi perdere tutto e diventassi matto adesso. |
|
From: Svetoslav S. <ga...@st...> - 2003-01-31 11:46:22
|
hi ,
could you apply this diff ?
best,
svetljo
############################
diff -Naur km.old/km_api.c km/km_api.c
--- km.old/km_api.c 2003-01-27 19:18:00.000000000 +0100
+++ km/km_api.c 2003-01-31 12:23:59.000000000 +0100
@@ -18,6 +18,7 @@
#include <linux/config.h>
#include <linux/version.h>
#include <linux/module.h>
+#include <linux/kmod.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/init.h>
@@ -469,6 +470,8 @@
printk("Kmultimedia API module version %s loaded\n", KM_API_VERSION);
+request_module("videodev");
+
return 0;
}
diff -Naur km.old/km.c km/km.c
--- km.old/km.c 2003-01-30 18:36:07.000000000 +0100
+++ km/km.c 2003-01-31 12:23:08.000000000 +0100
@@ -18,6 +18,7 @@
#include <linux/config.h>
#include <linux/version.h>
#include <linux/module.h>
+#include <linux/kmod.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/init.h>
@@ -849,6 +850,9 @@
}
}
if(result<0)printk("km: **** no supported devices found ****\n");
+
+request_module("km_api_drv");
+
return result;
}
|
|
From: Luc V. H. <lu...@e-...> - 2003-01-31 09:05:41
|
Too bad, seems I'm going to have use something else than ATI although it seems to be the most cost effictive solution. Tnx for the help Luc Van Hoeylandt Ilya Romanenko wrote: > Shure It really works, but the picture is only 2/3 of the screen. > It works but unusefull ! > > |You could use vesa framebuffer and let bios set up everything, but this > |will display the same picture on both TV and the monitor. |
|
From: Ilya R. <il...@vo...> - 2003-01-31 06:59:51
|
Shure It really works, but the picture is only 2/3 of the screen. It works but unusefull ! |You could use vesa framebuffer and let bios set up everything, but this |will display the same picture on both TV and the monitor. | | best | | Vladimir Dergachev |
|
From: Vladimir D. <vo...@mi...> - 2003-01-30 20:52:13
|
I have posted a new set of 4.3.0 binaries - could you try avview with
these ?
thanks !
Vladimir Dergachev
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-30 20:40:55
|
On Thu, 30 Jan 2003, Svetoslav Slavtchev wrote:
> >
> > Which AVview version are you using ? All the latest ones are started with
> > start_avview or start_avview.no_install.
> >
> > best
> >
> > Vladimir Dergachev
> the one from cvs :)
> but my distribution uses TCL/TK 8.3,
> so i have 8.4 in /usr/local
>
> [root@svetljo stable]# cat /usr/bin/avview
> #!/bin/bash
> export LD_LIBRARY_PATH=/usr/local/lib
> /usr/bin/start_avview
> [root@svetljo stable]#
>
>
I see. Well, on my machine it does not produce this error..
I am going to post a new set of binaries soon - could you try with these ?
best
Vladimir Dergachev
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-30 20:03:31
|
On Thu, 30 Jan 2003, Svetoslav Slavtchev wrote:
> Hi,
>
> * latest km from CVS
> * latest AVview from CVS
> * latest ati.2 experimental-2 binaries (troubles with the CVS code)
> * XFree86-4.2.99.5-20030122
> * linux-2.4.20
> ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
>
> troubles with avview:
> ###############################################
> [root@svetljo root]# avview
> control_screen=
> .setup.f.pane1.f.canvas.f.optionmenu0.menu
> NUM_ADAPTORS=1
> Adaptor 0: ATI Radeon Video Adapter
> type input video image
> ports 61
> 61 ATI Radeon Video Adapter
> X Error of failed request: BadMatch (invalid parameter attributes)
> Major opcode of failed request: 145 (XVideo)
> Minor opcode of failed request: 14 ()
> Serial number of failed request: 622
> Current serial number in output stream: 622
Which AVview version are you using ? All the latest ones are started with
start_avview or start_avview.no_install.
best
Vladimir Dergachev
|
|
From: Svetoslav S. <ga...@st...> - 2003-01-30 18:24:48
|
Hi,
* latest km from CVS
* latest AVview from CVS
* latest ati.2 experimental-2 binaries (troubles with the CVS code)
* XFree86-4.2.99.5-20030122
* linux-2.4.20
ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
troubles with avview:
###############################################
[root@svetljo root]# avview
control_screen=
.setup.f.pane1.f.canvas.f.optionmenu0.menu
NUM_ADAPTORS=1
Adaptor 0: ATI Radeon Video Adapter
type input video image
ports 61
61 ATI Radeon Video Adapter
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 145 (XVideo)
Minor opcode of failed request: 14 ()
Serial number of failed request: 622
Current serial number in output stream: 622
[root@svetljo root]#
###############################################
zapping-gnome2 and xawtv work
but overlay doesn't work that good
(there was an option in avview which could make it good,
but as i can not start avview ... :( )
cat /dev/vbi0 returns nothing
that's what i have in dmesg:
#########################################
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 942M
agpgart: Detected Via Apollo Pro KT266 chipset
agpgart: AGP aperture is 128M @ 0xd0000000
[drm] AGP 0.99 on VIA Apollo KT133 @ 0xd0000000 128MB
[drm] Initialized radeon 1.100.0 20021218 on minor 0
Linux video capture interface: v1.00
Kmultimedia API module version alpha-3.0 loaded
Kmultimedia module version alpha-3.0 loaded
Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=928
**CKPT km.c km_probe 477
km: using irq 9
Register aperture is 0xe4000000 0x00010000
kms variables: reg_aperture=0xfd321000
sizeof(kmfl_template)=624 sizeof(KM_FIELD)=48
Device ATI Technologies Inc Radeon 7500 QW 01:00.0 (0x1002:0x5157) corresponds to /dev/video0
kms variables: reg_aperture=0xfd321000
km: no data is available until AVview or xawtv is started
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
radeon_get_window_parameters: width=720 height=240
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
**CKPT km_api_data.c km_deallocate_data 401
**CKPT km_api_data.c km_deallocate_data 407
km: closed stream, 0 buffers captured
vbi_buf_size=20160
**CKPT km.c generic_allocate_dvb 67
**CKPT km.c generic_allocate_dvb 82
**CKPT km.c generic_allocate_dvb 130
regards,
svetljo
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-30 14:28:19
|
I have just committed the first version of km that is supposed to support
VBI capture for radeons. Unfortunately, I am not able to test it as there
is too much interference on my antenna (have no idea why so far).
Thus, I would appreciate very much if someone with AIW Radeon, AIW Radeon
7500 or 8500 card tried the code and let me know how it works.
* latest km from CVS
* latest AVview from CVS
* latest ati.2 from CVS
install km, start AVview. As root type
dmesg
this should show km loading
Do
cat /dev/vbi0
If there is no data it should not print anything. If there is vbi data it
is supposed to print it - but I have no idea how well this works. The
output will most like look like random characters, this is normal.
^C
dmesg
This should show km reporting how many buffers were captured in the stream
used by /dev/vbi0.
thanks !
Vladimir Dergachev
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-29 22:03:08
|
You could use vesa framebuffer and let bios set up everything, but this
will display the same picture on both TV and the monitor.
best
Vladimir Dergachev
On Wed, 29 Jan 2003, Luc Van Hoeylandt wrote:
> Hi,
>
> I'm looking for a ATI based card with dualhead support so i can view a
> textmode shell on the first output and view the second fbdev output on a
> tv. I'm unable to use X for various reasons. Is this possible with a
> radeon 7000 or 9000 ?
>
> Sorry if this is the wrong mailinglist but i can't find anything like
> gatos-users
>
> tnx,
>
> Luc
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
|
|
From: Luc V. H. <lu...@e-...> - 2003-01-29 16:52:43
|
Hi, I'm looking for a ATI based card with dualhead support so i can view a textmode shell on the first output and view the second fbdev output on a tv. I'm unable to use X for various reasons. Is this possible with a radeon 7000 or 9000 ? Sorry if this is the wrong mailinglist but i can't find anything like gatos-users tnx, Luc |
|
From: Vladimir D. <vo...@mi...> - 2003-01-29 16:43:19
|
On Wed, 29 Jan 2003, Monari Emanuele wrote:
> While compiling cvs tree, with xfree 4.2.1 the compiler stops here
> giving the error message below.
> I have resolved xf86Pci.h missing that xmkmf alerts about linking it
> form the x source. Is it right?
> How can I make it work?
>
Current ati.2 CVS is now against XFree86 4.2.99.3.
best
Vladimir Dergachev
> ThankYou!!!
> ____
>
> root@little:/usr/src/ati.2# make
> [...]
> gcc -O2 -fno-strength-reduce -ansi -pedantic -Wall -Wpointer-arith
> -fno-merge-constants -I. -I../xc//programs/Xserver/hw/xfree86/common
> [...]
> -DFUNCPROTO=15 -DNARROWPROTO -DIN_MODULE -DXFree86Module -DGLXEXT
> -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -c
> radeon_probe.c
>
> radeon_probe.c:84: `PCI_CHIP_RADEON_LX' undeclared here (not in a
> function)
> radeon_probe.c:84: initializer element is not constant
> radeon_probe.c:84: (near initialization for `RADEONChipsets[7].token')
> [...]
> radeon_probe.c:89: initializer element is not constant
> radeon_probe.c:89: (near initialization for `RADEONChipsets[12]')
> radeon_probe.c:90: `PCI_CHIP_RV200_QX' undeclared here (not in a
> function)
> radeon_probe.c:90: initializer element is not constant
> radeon_probe.c:90: (near initialization for `RADEONChipsets[13].token')
> radeon_probe.c:90: initializer element is not constant
> radeon_probe.c:90: (near initialization for `RADEONChipsets[13]')
> radeon_probe.c:91: `PCI_CHIP_RV250_Id' undeclared here (not in a
> function)
> [...]
> radeon_probe.c:133: initializer element is not constant
> radeon_probe.c:133: (near initialization for `RADEONPciChipsets[26]')
> _____
> --
> Risparmierei un sacco di tempo se lasciassi perdere tutto e diventassi
> matto adesso.
>
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-29 16:42:45
|
Try using AVview.
Vladimir Dergachev
On Wed, 30 Jan 2003, Daniel Zhelyazkov wrote:
>
> Hi, I am having some hard time getting this card's TV capture device to
> work under Linux. The driver can not
> find it's resources right. After fixing that (or have I?). The driver
> seems to load properly but something is wrong
> :(. Please help me!. What am I doing wrong? Thanks!
>
>
> OS: slackware 8.1 kernel 2.4.18
> Card: Tekram M230 bt819 2MB tda8425
>
>
> $ ffmpeg abc.mpg -vd /dev/video0
> Output #0, mpeg, to 'abc.mpg':
> Stream #0.0: Video: mpeg1video, 160x128, 25.00 fps, 200 kb/s
> Stream #0.1: Audio: mp2, 44100 Hz, mono, 64 kb/s
> Audio sampling: 44100 Hz, mono
> VIDIOCGCAP: Invalid argument
>
>
> $ xawtv
> This is xawtv-3.74, running on Linux/i686 (2.4.18)
> /dev/video0: wrong device
> v4l-conf had some trouble, trying to continue anyway
> no video grabber device available
>
>
> I have installed the ati.2 drivers and loaded these X modules:
>
>
> Load "dbe"
> Load "bt829"
> Load "v4l"
> Load "fi1236"
> Load "msp3430"
> Load "tda8425"
> Load "saa7114"
>
>
> So here is some info:
>
>
> Kmultimedia API module version alpha-2.0 loaded
> insmod ./km_drv.o km_debug=3
> Kmultimedia module version alpha-2.0 loaded
> Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=252
> km: using irq 5
>
> //it found irq 0 which was imposible as its the system's timer irq so i
> //set it to the first irq reserved for pci devices by the bios
>
> km: device -805431296
> Register_aperture is 0x00000000 0x00000000
>
> //i told it to use 0xda000000 0x00ffffff or exactly 2MB
>
> kms variables: reg_aperture=0xd0a0e000
>
> // the reg_aperture changes depending on that if lirc_dev is loaded or
> not
>
> sizeof(kmfl_template)=56 sizeof(KM_FIELD)=28
> Device ATI Technologies Inc 264VT [Mach64 VT] 00:0a.0 (0x1002:0x5654)
> corresponds to /dev/video0
> PCI: Setting latency timer of device 00:0a.0 to 64
> kms variables: reg_aperture=0xd0a0e000 <- is that right?
>
>
> #/proc/iomem
> dc000000-dc007fff : ymfpci
> ffff0000-ffffffff : reserved
> ...skipping...
> 00000000-0009ffff : System RAM
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000f0000-000fffff : System ROM
> 00100000-0ffeffff : System RAM
> 00100000-0028031c : Kernel code
> 0028031d-002eade3 : Kernel data
> 0fff0000-0fff2fff : ACPI Non-volatile Storage
> 0fff3000-0fffffff : ACPI Tables
> d8000000-d9ffffff : VIA Technologies, Inc. VT82C693A/694x [Apollo
> PRO133x]
> da000000-daffffff : ATI Technologies Inc 264VT [Mach64 VT]
> da000000-dafffffe : km_ati (Mach64)
> dc000000-dc007fff : Yamaha Corporation YMF-724F [DS-1 Audio Controller]
> dc000000-dc007fff : ymfpci
> ffff0000-ffffffff : reserved
>
>
> # lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo
> PRO133x] (rev 22)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
> MVP3/Pro133x AGP]
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South]
> (rev 09)
> 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
> 00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management
> 00:0a.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64
> VT] (rev 40)
> 00:0b.0 Multimedia audio controller: Yamaha Corporation YMF-724F [DS-1
> Audio Controller] (rev 03)
>
>
> # less /proc/interrupts
> CPU0
> 0: 59686 XT-PIC timer
> 1: 1284 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 4: 5860 XT-PIC serial
> 5: 0 XT-PIC km_ati (Mach64)
> 8: 1 XT-PIC rtc
> 11: 6135 XT-PIC ymfpci
> 14: 8172 XT-PIC ide0
> 15: 4 XT-PIC ide1
> NMI: 0
> ERR: 0
>
>
> # less /proc/video/dev/video0
> name : Km
> type : VID_TYPE_CAPTURE|VID_TYPE_TELETEXT
> hardware : 0x1
>
>
> # less /proc/devices
> Character devices:
> 1 mem
> 2 pty
> 3 ttyp
> 4 ttyS
> 5 cua
> 7 vcs
> 10 misc
> 14 sound
> 29 fb
> 61 BaseRemoteCtl
> 81 video_capture
> 109 lvm
> 128 ptm
> 129 ptm
> 136 pts
> 137 pts
> 162 raw
> 195 nvidia
>
> Block devices:
> 1 ramdisk
> 2 fd
> 3 ide0
> 7 loop
> 9 md
> 22 ide1
> 43 nbd
> 58 lvm
>
>
> $ v4l-conf
> v4l-conf: using X11 display :0
> dga: version 2.0
> mode: 800x600, depth=16, bpp=16, bpl=1600, base=0xda000000
> /dev/video0: wrong device
>
>
> # lsmod
> Module Size Used by Tainted: P
> km_v4l 3004 0 (unused)
> km_drv 22488 0 [km_v4l]
> km_api 2056 1 [km_drv]
> videodev 4448 1 [km_v4l km_drv]
> lirc_bt829 2440 0 (unused)
> lirc_dev 7600 1 [lirc_bt829]
> ymfpci 40800 1
> ac97_codec 9568 0 [ymfpci]
> apm 9148 2
> NVdriver 819904 0 (unused)
> ide-scsi 7456 0
> soundcore 3236 2 [ymfpci]
>
>
> Daniel Zhelyazkov
> dan...@gm...
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
|
|
From: Monari E. <em...@li...> - 2003-01-29 16:25:37
|
While compiling cvs tree, with xfree 4.2.1 the compiler stops here giving the error message below. I have resolved xf86Pci.h missing that xmkmf alerts about linking it form the x source. Is it right? How can I make it work? ThankYou!!! ____ root@little:/usr/src/ati.2# make [...] gcc -O2 -fno-strength-reduce -ansi -pedantic -Wall -Wpointer-arith -fno-merge-constants -I. -I../xc//programs/Xserver/hw/xfree86/common [...] -DFUNCPROTO=3D15 -DNARROWPROTO -DIN_MODULE -DXFree86Module -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -c radeon_probe.c radeon_probe.c:84: `PCI_CHIP_RADEON_LX' undeclared here (not in a function) radeon_probe.c:84: initializer element is not constant radeon_probe.c:84: (near initialization for `RADEONChipsets[7].token') [...] radeon_probe.c:89: initializer element is not constant radeon_probe.c:89: (near initialization for `RADEONChipsets[12]') radeon_probe.c:90: `PCI_CHIP_RV200_QX' undeclared here (not in a function) radeon_probe.c:90: initializer element is not constant radeon_probe.c:90: (near initialization for `RADEONChipsets[13].token') radeon_probe.c:90: initializer element is not constant radeon_probe.c:90: (near initialization for `RADEONChipsets[13]') radeon_probe.c:91: `PCI_CHIP_RV250_Id' undeclared here (not in a function) [...] radeon_probe.c:133: initializer element is not constant radeon_probe.c:133: (near initialization for `RADEONPciChipsets[26]') _____ --=20 Risparmierei un sacco di tempo se lasciassi perdere tutto e diventassi matto adesso. |
|
From: Daniel Z. <dan...@gm...> - 2003-01-29 15:44:46
|
Hi, I am having some hard time getting this card's TV capture device to
work under Linux. The driver can not
find it's resources right. After fixing that (or have I?). The driver
seems to load properly but something is wrong
:(. Please help me!. What am I doing wrong? Thanks!
OS: slackware 8.1 kernel 2.4.18
Card: Tekram M230 bt819 2MB tda8425
$ ffmpeg abc.mpg -vd /dev/video0
Output #0, mpeg, to 'abc.mpg':
Stream #0.0: Video: mpeg1video, 160x128, 25.00 fps, 200 kb/s
Stream #0.1: Audio: mp2, 44100 Hz, mono, 64 kb/s
Audio sampling: 44100 Hz, mono
VIDIOCGCAP: Invalid argument
$ xawtv
This is xawtv-3.74, running on Linux/i686 (2.4.18)
/dev/video0: wrong device
v4l-conf had some trouble, trying to continue anyway
no video grabber device available
I have installed the ati.2 drivers and loaded these X modules:
Load "dbe"
Load "bt829"
Load "v4l"
Load "fi1236"
Load "msp3430"
Load "tda8425"
Load "saa7114"
So here is some info:
Kmultimedia API module version alpha-2.0 loaded
insmod ./km_drv.o km_debug=3
Kmultimedia module version alpha-2.0 loaded
Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=252
km: using irq 5
//it found irq 0 which was imposible as its the system's timer irq so i
//set it to the first irq reserved for pci devices by the bios
km: device -805431296
Register_aperture is 0x00000000 0x00000000
//i told it to use 0xda000000 0x00ffffff or exactly 2MB
kms variables: reg_aperture=0xd0a0e000
// the reg_aperture changes depending on that if lirc_dev is loaded or
not
sizeof(kmfl_template)=56 sizeof(KM_FIELD)=28
Device ATI Technologies Inc 264VT [Mach64 VT] 00:0a.0 (0x1002:0x5654)
corresponds to /dev/video0
PCI: Setting latency timer of device 00:0a.0 to 64
kms variables: reg_aperture=0xd0a0e000 <- is that right?
#/proc/iomem
dc000000-dc007fff : ymfpci
ffff0000-ffffffff : reserved
...skipping...
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-0ffeffff : System RAM
00100000-0028031c : Kernel code
0028031d-002eade3 : Kernel data
0fff0000-0fff2fff : ACPI Non-volatile Storage
0fff3000-0fffffff : ACPI Tables
d8000000-d9ffffff : VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x]
da000000-daffffff : ATI Technologies Inc 264VT [Mach64 VT]
da000000-dafffffe : km_ati (Mach64)
dc000000-dc007fff : Yamaha Corporation YMF-724F [DS-1 Audio Controller]
dc000000-dc007fff : ymfpci
ffff0000-ffffffff : reserved
# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x] (rev 22)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South]
(rev 09)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management
00:0a.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64
VT] (rev 40)
00:0b.0 Multimedia audio controller: Yamaha Corporation YMF-724F [DS-1
Audio Controller] (rev 03)
# less /proc/interrupts
CPU0
0: 59686 XT-PIC timer
1: 1284 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 5860 XT-PIC serial
5: 0 XT-PIC km_ati (Mach64)
8: 1 XT-PIC rtc
11: 6135 XT-PIC ymfpci
14: 8172 XT-PIC ide0
15: 4 XT-PIC ide1
NMI: 0
ERR: 0
# less /proc/video/dev/video0
name : Km
type : VID_TYPE_CAPTURE|VID_TYPE_TELETEXT
hardware : 0x1
# less /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
7 vcs
10 misc
14 sound
29 fb
61 BaseRemoteCtl
81 video_capture
109 lvm
128 ptm
129 ptm
136 pts
137 pts
162 raw
195 nvidia
Block devices:
1 ramdisk
2 fd
3 ide0
7 loop
9 md
22 ide1
43 nbd
58 lvm
$ v4l-conf
v4l-conf: using X11 display :0
dga: version 2.0
mode: 800x600, depth=16, bpp=16, bpl=1600, base=0xda000000
/dev/video0: wrong device
# lsmod
Module Size Used by Tainted: P
km_v4l 3004 0 (unused)
km_drv 22488 0 [km_v4l]
km_api 2056 1 [km_drv]
videodev 4448 1 [km_v4l km_drv]
lirc_bt829 2440 0 (unused)
lirc_dev 7600 1 [lirc_bt829]
ymfpci 40800 1
ac97_codec 9568 0 [ymfpci]
apm 9148 2
NVdriver 819904 0 (unused)
ide-scsi 7456 0
soundcore 3236 2 [ymfpci]
Daniel Zhelyazkov
dan...@gm...
|
|
From: Vladimir D. <vo...@mi...> - 2003-01-29 15:29:55
|
> Anyway, is there any idea what way capture stuff could be integrated
> into dri? I've now got all the sources including Leif's patch against
> mach64 branch and I was going to try something, but I just know
> nothing about it yet so any hints would be usefull.
For radeons we only need to share an interrupt handler and fix memory
controller issues.
For rage128 (I have not thought much about it) it is likely we need to
share an interrupt handler and, perhaps, a dma queue.
For mach64 we need to share an interrupt handler and a dma queue and I
remember there had been some issues with DMA and 3d so their usage of dma
could be somewhat tricky.
best
Vladimir Dergachev
> --
> Best regards,
> Nikolai Zhubr
>
> > Also, I km_v4l.c does not mess with irq anymore. Instead it has calls to
> > start/stop_transfer and it can wait on dataq waitqueue in dvb's - as the
> > only thing it has to know is when a new field has arrived.
>
> > best
>
> > Vladimir Dergachev
>
>
|
|
From: Nikolai Z. <s0...@ho...> - 2003-01-29 08:27:50
|
Wednesday, 29 January, 2003, 3:52:22, Vladimir Dergachev wrote: [...] >> 1)get status: >> status=readl... >> mask=readl... >> if !(status & mask) return; >> 2)acknowledge: >> writel(status & mask ...... >> 3)generate abstract events: >> if((status & mask) & (1<<0)) kms->do_something(kms); >> if((status & mask) & (1<<1)) kms->do_something_else(kms); >> etc. >> 4)go to 1. > Unfortunately this won't work. You see DRM uses this same irq and exact > same registers (but different bits) so we have to be careful only to touch > those bits that we actually use. Hmm. I thought what I suggest is not really so different from what happens now. Anyway, is there any idea what way capture stuff could be integrated into dri? I've now got all the sources including Leif's patch against mach64 branch and I was going to try something, but I just know nothing about it yet so any hints would be usefull. -- Best regards, Nikolai Zhubr > Also, I km_v4l.c does not mess with irq anymore. Instead it has calls to > start/stop_transfer and it can wait on dataq waitqueue in dvb's - as the > only thing it has to know is when a new field has arrived. > best > Vladimir Dergachev |
|
From: Vladimir D. <vo...@mi...> - 2003-01-29 04:55:34
|
On Tue, 28 Jan 2003, Mark H. James wrote:
> Or if you don't boot straight into X, you could load km as part of the X startup script, so if there's a problem you can fix it in text mode after rebooting.
>
One thing to keep in mind is that km should be loaded after drm-kernel.
best
Vladimir Dergachev
|