« previous next »
Pages: [1] 2 3   Go Down

Author Topic: udev failing to produce device node, I think  (Read 2213 times)

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
udev failing to produce device node, I think
« on: April 17, 2012, 07:29:52 AM »
In the thread below, I am working on getting my dvb-t card, a Compro E700 to work

http://www.pclinuxos.com/forum/index.php/topic,86186.0.html

I am coming to a brickwall and I am assessing how high it is.   ;D

 The basic problem at the moment is, the card is recorded occupying a pci slot but no device node is created.

Quote
[root@KDE-mini gert]# lspci -vn -s 04:00.0
04:00.0 0400: 18c3:0720
        Subsystem: 185b:f000
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at feaf0000 (32-bit, non-prefetchable) [size=64K]
        Memory at feae0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [100] Device Serial Number 00-00-00-07-20-3c-11-00
        Capabilities: [400] Virtual Channel
       Kernel driver in use: -------
        Kernel modules: --------
[root@KDE-mini gert]#


I have done a lot searching on the net and it is a hard case. From this searching I have come to the conlusion that trying to use the module ngene is probably the way to go.  I have seen results of lspci -vn actually has the ngene listed in the two red lines I have shown.

I have looked at how udev may work and my understanding is that udev helps create the device nodes.

Manually loading ngene with modprobe ngene

Quote
[root@KDE-mini gert]# lsmod | grep -i ngene
ngene                  19867  0
dvb_core               76614  1 ngene
i2c_core               16500  2 ngene,nvidia
[root@KDE-mini gert]#


In /sys/bus/pci/devices/0000:04:00.0/modalias I find

Quote
pci:v000018C3d00000720sv0000185Bsd0000F000bc04sc00i00


I believe this is important but I don't understand how it fits into the picture, apart from userspace can access this information

Similar my understanding is that ngene may export the alias lines below to sysfs (not found where that may be though?) I thought the alias lines would help udev to auto load the module ngene, or the udev-rules would if the alias lines match.

Quote
[root@KDE-mini gert]# modinfo ngene
filename:       /lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene/ngene.ko.gz
license:        GPL
author:         Micronas, Ralph Metzler, Manfred Voelkel
description:    nGene
srcversion:     6E3C21BAF0A770637993D9D
alias:          pci:v000018C3d00000720sv00001461sd0000062Ebc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD20bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD10bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD00bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DB02bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DB01bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000ABC4bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000ABC3bc*sc*i*
depends:        dvb-core,i2c-core
vermagic:       2.6.38.8-pclos3.bfs SMP preempt mod_unload modversions 686
parm:           one_adapter:Use only one adapter. (int)
parm:           debug:Print debugging information. (int)
parm:           adapter_nr:DVB adapter numbers (array of short)
[root@KDE-mini gert]#


I have studied the following on udev

http://www.linuxfromscratch.org/lfs/view/development/chapter07/udev.html

Any pointers why I do not get a device node for the card, /dev/dvb

(Ahh yes, I know I am in very deep waters but this never seems to deter me )
« Last Edit: April 17, 2012, 07:33:17 AM by wedgetail »
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11545
  • ----IOFLU----
Re: udev failing to produce device node, I think
« Reply #1 on: April 17, 2012, 12:27:57 PM »
wedgetail:

Try a newer kernel.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: udev failing to produce device node, I think
« Reply #2 on: April 17, 2012, 12:56:50 PM »
Quote from: Old-Polack on April 17, 2012, 12:27:57 PM
wedgetail:

Try a newer kernel.

+1,

but there is no ngene module in new kernel ..

AS
Logged

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #3 on: April 17, 2012, 05:29:08 PM »
Ooooh, the wall suddenly got a lot higher   ;D

Quote
[root@KDE-mini-kernel3x gert]# uname -r
3.2.14-pclos7.bfs
[root@KDE-mini-kernel3x gert]#

Earlier I had already tried the later kernel, same result no device node.

Quote
[root@KDE-mini-kernel3x gert]# modprobe ngene
[root@KDE-mini-kernel3x gert]# lsmod |grep -i ngene
ngene                  23406  0
dvb_core               77173  1 ngene
cxd2099                 4891  1 ngene
i2c_core               16526  7 ngene,cxd2099,saa7134,nvidia,v4l2_common,videodev,tveeprom
[root@KDE-mini-kernel3x gert]# dmesg | grep -i ngene
nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[root@KDE-mini-kernel3x gert]#

Since this system is a very sparsely populated system I am not sure if I am missing something here but this test KDE-mini seems to run very nicely I just have not had time to add more programs.

AS
Sorry I don't understand  you comment on ngene, it seems to behave the same in all my systems?

Quote
[root@KDE-mini-kernel3x gert]# udevadm --debug monitor
main: runtime dir '/dev/.udev'
run_command: calling: monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1334703085.795557] remove   /bus/pci/drivers/ngene (drivers)
UDEV  [1334703085.795816] remove   /bus/pci/drivers/ngene (drivers)
KERNEL[1334703085.795950] remove   /module/ngene (module)
UDEV  [1334703085.796123] remove   /module/ngene (module)
KERNEL[1334703085.802588] remove   /class/dvb (class)
KERNEL[1334703085.802827] remove   /module/dvb_core (module)
UDEV  [1334703085.802844] remove   /class/dvb (class)
UDEV  [1334703085.802855] remove   /module/dvb_core (module)
KERNEL[1334703085.807872] remove   /module/cxd2099 (module)
UDEV  [1334703085.807889] remove   /module/cxd2099 (module)

KERNEL[1334703142.728065] add      /module/cxd2099 (module)
UDEV  [1334703142.728087] add      /module/cxd2099 (module)
KERNEL[1334703142.728786] add      /module/dvb_core (module)
KERNEL[1334703142.729141] add      /class/dvb (class)
UDEV  [1334703142.729154] add      /module/dvb_core (module)
UDEV  [1334703142.729166] add      /class/dvb (class)
KERNEL[1334703142.729503] add      /module/ngene (module)
KERNEL[1334703142.729743] add      /bus/pci/drivers/ngene (drivers)
UDEV  [1334703142.729756] add      /bus/pci/drivers/ngene (drivers)
UDEV  [1334703142.729768] add      /module/ngene (module)
^C
[root@KDE-mini-kernel3x gert]#

Above shows what happens when I modprobe -r ngene and modprobe ngene

Right now I am struggling to find my website records as I am in the testing system, I have however found one or two places where the ngene code was recorded I will have to locate that again.  I will scan this and see if I can make out what it is supposed to do.  Earlier I was just looking at the alias lines and pondering how I could add one covering this system.

Quote
[root@KDE-mini-kernel3x gert]# modprobe -c |grep ngene
alias pci:v000018C3d00000720sv0000185Bsd0000F000bc*sc*i* ngene <----- from /etc/modprobe.conf
alias pci:v000018C3d00000720sv00001461sd0000062Ebc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000ABC3bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000ABC4bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000DB01bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000DB02bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000DD00bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000DD10bc*sc*i* ngene
alias pci:v000018C3d00000720sv000018C3sd0000DD20bc*sc*i* ngene
[root@KDE-mini-kernel3x gert]#

The alias lines above all but one comes from module ngene I added the other via /etc/modprobe.conf

I interpret the above that if a match to above lines is found then ngene would automatically be installe/inserted but can not yet prove it to myself.

I will return to my usual kernel.
« Last Edit: April 17, 2012, 05:40:47 PM by wedgetail »
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: udev failing to produce device node, I think
« Reply #4 on: April 17, 2012, 05:32:57 PM »
Quote from: wedgetail on April 17, 2012, 05:29:08 PM

AS
Sorry I don't understand  you comment on ngene, it seems to behave the same in all my systems?


Am I allowed to be wrong from time to time ? :D ;D
You are right, it is there!  ;)

AS
Logged

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #5 on: April 17, 2012, 05:50:47 PM »
AS
Yes  ;D ;D  
I did get real nervous when I saw the comment, starting to think that somehow I had dragged ngene in with some lspci xxxx statement.

Edit:

I have been wondering why ngene did not run, not knowing what that means. Normally I assume a module driver running would end up with furnishing device node etc.  This does not seem to happen here so I assumed that ngene die not run or if it did that it would provide error messages?

Quote
[root@KDE-mini gert]# dmesg|grep -i ngene
nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[root@KDE-mini gert]#   


I have found following
http://kerneldox.com/d2/d0a/ngene-cards_8c_source.html
and right at the end I see:

Quote
printk(KERN_INFO
00446                "nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas\n");


I am tempted to say that some part of ngene may have run to generate red line in dmesg each time a run attempted.  I don't know however if the code I have been looking at is that installed in the pclinuxos.

The code is not really a beginners example so this needs some procrastination on my part.  I have been scanning loosely and I think I have convinced myself that if all was ok this program would have generated a device node.
« Last Edit: April 17, 2012, 06:58:40 PM by wedgetail »
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #6 on: April 17, 2012, 07:00:58 PM »
I think my question now is, where can I find the source code for ngene used in pclinuxos.   8)
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: udev failing to produce device node, I think
« Reply #7 on: April 17, 2012, 07:07:29 PM »
Quote from: wedgetail on April 17, 2012, 07:00:58 PM
I think my question now is, where can I find the source code for ngene used in pclinuxos.   8)


You can find the source in the kernel-3.2.x-source package.   ;)

Quote
# find /usr/src/linux-3.2.15 -name ngene\*
/usr/src/linux-3.2.15/drivers/media/dvb/ngene
/usr/src/linux-3.2.15/drivers/media/dvb/ngene/ngene-dvb.c
/usr/src/linux-3.2.15/drivers/media/dvb/ngene/ngene.h
/usr/src/linux-3.2.15/drivers/media/dvb/ngene/ngene-core.c
/usr/src/linux-3.2.15/drivers/media/dvb/ngene/ngene-i2c.c
/usr/src/linux-3.2.15/drivers/media/dvb/ngene/ngene-cards.c

AS
Logged

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #8 on: April 17, 2012, 08:29:30 PM »
AS
Using slightly different find method but a bit odd, no source files?

Quote
[root@KDE-mini gert]# locate ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene/ngene.ko.gz
/usr/lib/kde4/kcm_dolphingeneral.so
/usr/share/kde4/services/kcmdolphingeneral.desktop
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Kconfig
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Makefile
[root@KDE-mini gert]#

I looked in the kernel 3.x system too same thing?
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: udev failing to produce device node, I think
« Reply #9 on: April 17, 2012, 08:35:14 PM »
Quote from: wedgetail on April 17, 2012, 08:29:30 PM
AS
Using slightly different find method but a bit odd, no source files?

Quote
[root@KDE-mini gert]# locate ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene/ngene.ko.gz
/usr/lib/kde4/kcm_dolphingeneral.so
/usr/share/kde4/services/kcmdolphingeneral.desktop
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Kconfig
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Makefile
[root@KDE-mini gert]#

I looked in the kernel 3.x system too same thing?

Quote from: AS on April 17, 2012, 07:07:29 PM

You can find the source in the kernel-3.2.x-source package.   ;)

AS
Logged

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #10 on: April 17, 2012, 09:00:47 PM »
AS

 :-[ :-[ errrhh lost for words.  Downloading now.


Quote
# find /usr/src/linux-3.2.15 -name ngene\*

You have linux here, is this because you compile your systems from source code? 
Hmmm, considering that below I have highlighted in red the ngene part, this seems another not very smart question.  :'(


Well download finished, and it looks like I am ready to dive in.

Quote
[root@KDE-mini gert]# locate  ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene
/lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene/ngene.ko.gz
/usr/lib/kde4/kcm_dolphingeneral.so
/usr/share/kde4/services/kcmdolphingeneral.desktop
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Kconfig
/usr/src/kernel-devel-2.6.38.8-pclos3.bfs/drivers/media/dvb/ngene/Makefile
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/Kconfig
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/Makefile
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/ngene-cards.c
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/ngene-core.c
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/ngene-dvb.c
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/ngene-i2c.c
/usr/src/linux-2.6.38.8-pclos3/drivers/media/dvb/ngene/ngene.h
[root@KDE-mini gert]#

The kitchen sink has sprung a leak, so I will be otherwise occupied for a while.   Never a dull moment here.  ;D
« Last Edit: April 17, 2012, 09:03:14 PM by wedgetail »
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Wildman

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 7553
  • Symphony for a Unstrung Tongue
Re: udev failing to produce device node, I think
« Reply #11 on: April 17, 2012, 09:52:19 PM »
Not sure if this will help any, but the bug list for ngene  might be of use...(shot in the dark, really)

http://ngene.wikidot.com/what-is-ngene
Logged
Happiness is not having what you want, but wanting what you have!

Joe Gable, "Joble" Was my Friend..
Dave "Exwintech" has also gone on...
Linux Counter #288984

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #12 on: April 17, 2012, 11:28:26 PM »
Wildman
Thanks for replying, you never know.

No it is not the same, you have found something called nGENE a program for graphics handling/presentation I think. The module I am chasing is one called nGene and it handles digital TV cards, my particular card is Compro Vista E700 which I got in the days when I was still using Windows mainly now it is the other way around and I find it is not well supported in Linux.    :)
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2428
  • Any Bugs in site?
Re: udev failing to produce device node, I think
« Reply #13 on: April 18, 2012, 06:36:21 AM »
Well, a bit wild, but I could not resist the urge to try and run a make on some ngene files from the internet. So it has now turned to programming questions.

I don't expect it to be working but I am intrigued with the output from the make, which I assume is safe enough as long as I don't try make-install?  

Quote
[gert@KDE-mini:/btest] $make
make -C /lib/modules/2.6.38.8-pclos3.bfs/build SUBDIRS=/btest CONFIG_DVB_NGENE=m CONFIG_DVB_DRXD=m modules
make[1]: Entering directory `/usr/src/kernel-devel-2.6.38.8-pclos3.bfs'
  CC [M]  /btest/drxd_hard.o
  CC [M]  /btest/drxd_firm.o
  CC [M]  /btest/ngene_core.o
/btest/ngene_core.c: In function ‘ngene_i2c_init’:
/btest/ngene_core.c:1095:14: error: ‘I2C_CLASS_TV_ANALOG’ undeclared (first use in this function)
/btest/ngene_core.c:1095:14: note: each undeclared identifier is reported only once for each function it appears in
/btest/ngene_core.c:1103:2: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:359)
/btest/ngene_core.c:1103:11: error: ‘I2C_HW_SAA7146’ undeclared (first use in this function)
/btest/ngene_core.c:1115:2: warning: passing argument 1 of ‘__mutex_init’ from incompatible pointer type
include/linux/mutex.h:115:13: note: expected ‘struct mutex *’ but argument is of type ‘struct rt_mutex *’
/btest/ngene_core.c: At top level:
/btest/ngene_core.c:1761:2: error: unknown field ‘ioctl’ specified in initializer
/btest/ngene_core.c:1761:2: warning: initialization from incompatible pointer type
/btest/ngene_core.c:3314:2: error: unknown field ‘ioctl’ specified in initializer
/btest/ngene_core.c:3314:2: warning: initialization from incompatible pointer type
/btest/ngene_core.c:3330:12: warning: ‘lnbh21_set_voltage’ defined but not used
/btest/ngene_core.c:3355:12: warning: ‘lnbh21_set_tone’ defined but not used
/btest/ngene_core.c:3417:12: warning: ‘viper_switch_ctrl’ defined but not used
/btest/ngene_core.c:3433:12: warning: ‘viper_switch_ctrl2’ defined but not used
/btest/ngene_core.c:3449:12: warning: ‘viper_gate_ctrl’ defined but not used
/btest/ngene_core.c:3462:12: warning: ‘python_switch_ctrl’ defined but not used
/btest/ngene_core.c:3476:12: warning: ‘viper_reset_xc’ defined but not used
/btest/ngene_core.c:3496:12: warning: ‘python_gate_ctrl’ defined but not used
make[2]: *** [/btest/ngene_core.o] Error 1
make[1]: *** [_module_/btest] Error 2
make[1]: Leaving directory `/usr/src/kernel-devel-2.6.38.8-pclos3.bfs'
make: *** [all] Error 2
[gert@KDE-mini:/btest] $

I2C_CLASS_TV_ANALOG this only shows in a few lines

Quote
#ifdef I2C_ADAP_CLASS_TV_DIGITAL
   adap->class=I2C_ADAP_CLASS_TV_DIGITAL|I2C_CLASS_TV_ANALOG;
#else
   adap->class=I2C_CLASS_TV_ANALOG;
#endif

Where would I be expected to declare this?


« Last Edit: April 18, 2012, 06:38:22 AM by wedgetail »
Logged
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: udev failing to produce device node, I think
« Reply #14 on: April 18, 2012, 07:06:13 AM »
Quote from: wedgetail on April 18, 2012, 06:36:21 AM
Well, a bit wild, but I could not resist the urge to try and run a make on some ngene files from the internet. So it has now turned to programming questions.

You need to carefully verify about the requirements, very often modules source code is bound to a very specific kernel release ... and left there in wild ...

AS

Quote
I don't expect it to be working but I am intrigued with the output from the make, which I assume is safe enough as long as I don't try make-install?  

Logged
Pages: [1] 2 3   Go Up
« previous next »