You can subscribe to this list here.
2002 |
Jan
(2) |
Feb
(2) |
Mar
(22) |
Apr
(24) |
May
(7) |
Jun
(44) |
Jul
(16) |
Aug
(2) |
Sep
(13) |
Oct
(11) |
Nov
(19) |
Dec
(25) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(16) |
Feb
(27) |
Mar
(5) |
Apr
(20) |
May
(17) |
Jun
(34) |
Jul
(29) |
Aug
(22) |
Sep
(25) |
Oct
(11) |
Nov
(13) |
Dec
(18) |
2004 |
Jan
(25) |
Feb
(22) |
Mar
(33) |
Apr
(15) |
May
(37) |
Jun
(15) |
Jul
(12) |
Aug
(22) |
Sep
(18) |
Oct
(45) |
Nov
(19) |
Dec
(30) |
2005 |
Jan
(31) |
Feb
(35) |
Mar
(27) |
Apr
(22) |
May
(9) |
Jun
(13) |
Jul
(13) |
Aug
(9) |
Sep
(25) |
Oct
(25) |
Nov
(12) |
Dec
(20) |
2006 |
Jan
(14) |
Feb
(16) |
Mar
(17) |
Apr
(8) |
May
(7) |
Jun
(20) |
Jul
(21) |
Aug
(12) |
Sep
(19) |
Oct
(6) |
Nov
(23) |
Dec
(15) |
2007 |
Jan
(13) |
Feb
(14) |
Mar
(24) |
Apr
(21) |
May
(9) |
Jun
(5) |
Jul
(7) |
Aug
(9) |
Sep
(21) |
Oct
(5) |
Nov
(30) |
Dec
(9) |
2008 |
Jan
(15) |
Feb
(18) |
Mar
(4) |
Apr
(11) |
May
(3) |
Jun
(14) |
Jul
(12) |
Aug
(1) |
Sep
(31) |
Oct
(10) |
Nov
(9) |
Dec
(2) |
2009 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(2) |
May
(7) |
Jun
(22) |
Jul
(5) |
Aug
(1) |
Sep
(26) |
Oct
(13) |
Nov
(2) |
Dec
(10) |
2010 |
Jan
(29) |
Feb
(2) |
Mar
(23) |
Apr
(9) |
May
(7) |
Jun
(8) |
Jul
(4) |
Aug
(4) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(9) |
2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(25) |
May
(2) |
Jun
(19) |
Jul
(6) |
Aug
(4) |
Sep
(9) |
Oct
(3) |
Nov
(8) |
Dec
(7) |
2012 |
Jan
(5) |
Feb
(10) |
Mar
(10) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
(18) |
Dec
(10) |
2013 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(4) |
Jun
|
Jul
(26) |
Aug
(13) |
Sep
(24) |
Oct
(2) |
Nov
(1) |
Dec
(4) |
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
(5) |
2015 |
Jan
(1) |
Feb
(8) |
Mar
(7) |
Apr
(30) |
May
(3) |
Jun
(4) |
Jul
|
Aug
(7) |
Sep
(6) |
Oct
(13) |
Nov
(9) |
Dec
(2) |
2016 |
Jan
|
Feb
(7) |
Mar
(11) |
Apr
(6) |
May
(2) |
Jun
(16) |
Jul
(2) |
Aug
(6) |
Sep
(2) |
Oct
(2) |
Nov
(2) |
Dec
(7) |
2017 |
Jan
(9) |
Feb
(25) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(14) |
Sep
(23) |
Oct
(3) |
Nov
|
Dec
(4) |
2018 |
Jan
|
Feb
|
Mar
(6) |
Apr
(4) |
May
(11) |
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
(3) |
Nov
(20) |
Dec
(10) |
2019 |
Jan
(4) |
Feb
(2) |
Mar
(9) |
Apr
(7) |
May
(2) |
Jun
(14) |
Jul
(17) |
Aug
(8) |
Sep
(9) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
2020 |
Jan
(5) |
Feb
(13) |
Mar
|
Apr
(6) |
May
|
Jun
(7) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(11) |
Dec
(4) |
2021 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
(4) |
May
(7) |
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
(8) |
Nov
|
Dec
(3) |
2022 |
Jan
(5) |
Feb
(13) |
Mar
|
Apr
(3) |
May
(4) |
Jun
(4) |
Jul
|
Aug
(10) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(4) |
2023 |
Jan
(10) |
Feb
(5) |
Mar
|
Apr
|
May
(5) |
Jun
(4) |
Jul
(6) |
Aug
(4) |
Sep
(28) |
Oct
(8) |
Nov
(2) |
Dec
(1) |
2024 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
(3) |
Jun
(1) |
Jul
(10) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
(9) |
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mitchell F. <mit...@ya...> - 2002-06-28 15:52:33
|
Compiling my own kernel fixed that problem. With the modules inserted, when I run ibtest for the first time it segfaults. I tried running it under gdb after compiling with the "-g" option, but it says the program exits. Running ibtest a second time, it stops at "trying to open pad = 12 on /dev/gpib0 ...", I can ctrl-c it. Mitchell --- frank mori hess <fm...@st...> wrote: > The only thing that could cause the init_module to fail is if the > release code for your pcmcia modules don't match the value in the header > files you compiled against. Apparently, this has been a problem with > Suse and RedHat in the past. You can disable the check ( it's in the > init_ni_gpib_cs() function in drivers/tnt4882/tnt4882_cs.c ) or compile > your own kernel so you know the release code is consistent. > > Frank > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: Major A <an...@us...> - 2002-06-28 13:59:26
|
> The VFS interface doesn't exist at present. Ah. Is there an older version that works with 2.4.x kernels and has a VFS interface? > Sorry, you are probably SOL as far as HP cards go, as far as I know > Agilent doesn't release register-level info on their cards. It's too bad, > because 90% of the code required for a basic driver already exists. Maybe I should try and read out the FPGA's EEPROM? (just joking...) Cheers, Andras =========================================================================== Major Andras e-mail: an...@us... www: http://andras.webhop.org/ =========================================================================== |
From: frank m. h. <fm...@st...> - 2002-06-28 12:31:45
|
On Thu, 27 Jun 2002, Major A wrote: > > Hi, > > I just downloaded linux-gpib-3.1.4 and failed to get anything > working. This may be due to the card not being supported, or due to my > stupidity, or both. Unfortunately, the documentation shipped with the > package seems to be outdated, I couldn't find ibchk and the other > utilities mentioned, and no such modules as gpib0.o etc. are built. Yes, the documentation is quite outdated. > > I did a modprobe on the driver I believe I need (cec-gpib), which then > printed an initialization message in the system log. Now there's some > confusion as to what device files I need -- I tried various > major/minor combinations (c 31 0, c 31 17, c 160 0, c 160 17), with no > success: only c 160 0 seems to have a kernel driver behind it, but it > says "invalid argument" to anything I do. I'd like to use the VFS > interface, so I didn't bother setting up a config file etc. > The VFS interface doesn't exist at present. > Another potential problem is the card: it's an HP PCI card and has two > chips on it: a PLX9050 (which is also used by cards supported by > cec-gpib and ines-gpib, apparently), and a Xilinx FPGA. I only hope > that it's compatible to one of the other PCI cards... This is the > output of lspci -v: > > 01:0a.0 Communication controller: PLX Technology, Inc. PCI <-> IOBus Bridge (rev 01) > Subsystem: Hewlett-Packard Company: Unknown device 10b0 > Flags: medium devsel, IRQ 11 > Memory at ff8fec00 (32-bit, non-prefetchable) [size=128] > I/O ports at dc00 [size=128] > Memory at ff8fe800 (32-bit, non-prefetchable) [size=32] > Memory at f6af8000 (32-bit, prefetchable) [size=32K] > Memory at ff8fe400 (32-bit, non-prefetchable) [size=16] > > Anyone recognize this? Sorry, you are probably SOL as far as HP cards go, as far as I know Agilent doesn't release register-level info on their cards. It's too bad, because 90% of the code required for a basic driver already exists. > > Before I forget: I use devfs, is there any support for it in > linux-gpib? It would be nice to have it, so I wouldn't have to create > device files "by hand". > No, but it should get put in eventually... Frank |
From: frank m. h. <fm...@st...> - 2002-06-27 22:50:43
|
On Thu, 27 Jun 2002, Mitchell Ferschweiler wrote: > When I do an insmod (or modprobe) it returns the following: > > Symbol version prefix '' > Using /lib/modules/2.4.10-4GB/misc/tnt4882.o > /lib/modules/2.4.10-4GB/misc/tnt4882.o: init_module: Operation not > permitted > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters > > Mitchell > The only thing that could cause the init_module to fail is if the release code for your pcmcia modules don't match the value in the header files you compiled against. Apparently, this has been a problem with Suse and RedHat in the past. You can disable the check ( it's in the init_ni_gpib_cs() function in drivers/tnt4882/tnt4882_cs.c ) or compile your own kernel so you know the release code is consistent. Frank |
From: Mitchell F. <mit...@ya...> - 2002-06-27 22:12:03
|
When I do an insmod (or modprobe) it returns the following: Symbol version prefix '' Using /lib/modules/2.4.10-4GB/misc/tnt4882.o /lib/modules/2.4.10-4GB/misc/tnt4882.o: init_module: Operation not permitted Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters Mitchell --- frank mori hess <fm...@st...> wrote: > > Oops, fixed now, I tested it as far as modprobing this time. > > Frank > > On Thu, 27 Jun 2002, Mitchell Ferschweiler wrote: > > > The compile finishes, but depmod returns the following: > > > > depmod: *** Unresolved symbols in > > /lib/modules/2.4.10-4GB/misc/tnt4882.o > > depmod: writeb_wrapper > > depmod: inb_wrapper > > depmod: outb_wrapper > > depmod: readb_wrapper > > > > Mitchell > > > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: Major A <an...@us...> - 2002-06-27 21:04:25
|
Hi, I just downloaded linux-gpib-3.1.4 and failed to get anything working. This may be due to the card not being supported, or due to my stupidity, or both. Unfortunately, the documentation shipped with the package seems to be outdated, I couldn't find ibchk and the other utilities mentioned, and no such modules as gpib0.o etc. are built. I did a modprobe on the driver I believe I need (cec-gpib), which then printed an initialization message in the system log. Now there's some confusion as to what device files I need -- I tried various major/minor combinations (c 31 0, c 31 17, c 160 0, c 160 17), with no success: only c 160 0 seems to have a kernel driver behind it, but it says "invalid argument" to anything I do. I'd like to use the VFS interface, so I didn't bother setting up a config file etc. Another potential problem is the card: it's an HP PCI card and has two chips on it: a PLX9050 (which is also used by cards supported by cec-gpib and ines-gpib, apparently), and a Xilinx FPGA. I only hope that it's compatible to one of the other PCI cards... This is the output of lspci -v: 01:0a.0 Communication controller: PLX Technology, Inc. PCI <-> IOBus Bridge (rev 01) Subsystem: Hewlett-Packard Company: Unknown device 10b0 Flags: medium devsel, IRQ 11 Memory at ff8fec00 (32-bit, non-prefetchable) [size=128] I/O ports at dc00 [size=128] Memory at ff8fe800 (32-bit, non-prefetchable) [size=32] Memory at f6af8000 (32-bit, prefetchable) [size=32K] Memory at ff8fe400 (32-bit, non-prefetchable) [size=16] Anyone recognize this? Before I forget: I use devfs, is there any support for it in linux-gpib? It would be nice to have it, so I wouldn't have to create device files "by hand". Any help would be much appreciated, in particular the VFS interface stuff. Andras =========================================================================== Major Andras e-mail: an...@us... www: http://andras.webhop.org/ =========================================================================== |
From: frank m. h. <fm...@st...> - 2002-06-27 15:39:51
|
Oops, fixed now, I tested it as far as modprobing this time. Frank On Thu, 27 Jun 2002, Mitchell Ferschweiler wrote: > The compile finishes, but depmod returns the following: > > depmod: *** Unresolved symbols in > /lib/modules/2.4.10-4GB/misc/tnt4882.o > depmod: writeb_wrapper > depmod: inb_wrapper > depmod: outb_wrapper > depmod: readb_wrapper > > Mitchell > |
From: Mitchell F. <mit...@ya...> - 2002-06-27 14:47:55
|
The compile finishes, but depmod returns the following: depmod: *** Unresolved symbols in /lib/modules/2.4.10-4GB/misc/tnt4882.o depmod: writeb_wrapper depmod: inb_wrapper depmod: outb_wrapper depmod: readb_wrapper Mitchell --- frank mori hess <fm...@st...> wrote: > > Try now? > > Frank > > On Wed, 26 Jun 2002, Mitchell Ferschweiler wrote: > > > When compiling I now get the following error message: > > > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-27 13:31:28
|
On Wed, 26 Jun 2002, Graeme Woollett wrote: > Hello > I successfully biult and installed the modules for this card using : > modprobe cec-gpib.o > This loads cec-gpib,nec7210 & gpib-common > You want the pc2-gpib module for an isa cec card, not the cec-gpib module (which is for the pci cec card). Also, there might be some problems with pc2 support in the last release although it seems to be fixed in the current cvs head. Frank |
From: Graeme W. <g.w...@ir...> - 2002-06-27 04:37:53
|
Hello I successfully biult and installed the modules for this card using : modprobe cec-gpib.o This loads cec-gpib,nec7210 & gpib-common /etc/gpib.conf is as follows: /* This is how you might set up a pcIIa board on /dev/gpib0, uncomment to use. */ interface { minor = 0 board_type = pcII pad = 0 sad = 0 timeout = 3s eos = 0x0a set-reos yes set-bin no base = 0x2B8 irq = 7 dma = 3 master yes } /* Now the device sections define the device characteristics for each device. * These are only used if you want to open the device using ibfind() (instead * of ibdev() ) */ device { name = voltmeter /* device mnemonic */ minor = 0 /* minor number for interface board this device is connected to */ pad = 10 /* The Primary Address */ sad = 0 /* Secondary Address */ /* init-string = D2HELLO */ /* send some init chars */ init-flags = LLO,DCL /* set flags */ eos=0xa /* EOS Byte */ set-reos no /* Terminate read if EOS */ set-bin no /* Compare EOS 8-bit */ } device { name = scope minor = 0 pad=8 sad=0 } ibtest program responds with: ibBoardFunc :[xxxxxxxx] (-)< ERR> EDVR <OS ERROR> -- errrno=19 (no such device) failed to get descriptor Any ideas Thanks Graeme Woollett |
From: frank m. h. <fm...@st...> - 2002-06-26 23:43:38
|
Try now? Frank On Wed, 26 Jun 2002, Mitchell Ferschweiler wrote: > When compiling I now get the following error message: > |
From: Mitchell F. <mit...@ya...> - 2002-06-26 23:21:05
|
When compiling I now get the following error message: gcc -D__KERNEL__ -I/usr/src/linux-2.4.10.SuSE/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -I. -I../include -I../../include -c -o tnt4882_init.o tnt4882_init.c In file included from tnt4882_init.c:21: tnt4882.h:68: parse error before `init_ni_gpib_cs' tnt4882.h:68: warning: type defaults to `int' in declaration of `init_ni_gpib_cs' tnt4882.h:68: warning: data definition has no type or storage class tnt4882.h:69: parse error before `exit_ni_gpib_cs' tnt4882.h:69: warning: type defaults to `int' in declaration of `exit_ni_gpib_cs' tnt4882.h:69: warning: data definition has no type or storage class make[2]: *** [tnt4882_init.o] Error 1 make[2]: Leaving directory `/home/mitchell/linux-gpib/driver/tnt4882' make[1]: *** [subdirs] Error 2 make[1]: Leaving directory `/home/mitchell/linux-gpib/driver' make: *** [linux-gpib] Error 2 Mitchell --- frank mori hess <fm...@st...> wrote: > > > On Wed, 26 Jun 2002, Mitchell Ferschweiler wrote: > > > Here are the messages from my /var/log/messages: > > > > Jun 26 08:38:56 linux cardmgr[365]: initializing socket 0 > > Jun 26 08:38:56 linux cardmgr[365]: unsupported card in socket 0 > > Jun 26 08:38:56 linux cardmgr[365]: product info: "National > > Instruments", "PCMCIA-GPIB", "Rev. C", "" > > Jun 26 08:38:56 linux cardmgr[365]: manfid: 0x010b, 0x4882 > > > > Mitchell, > > Would you try out the current cvs with your ni pcmcia card? The > interface > name for gpib.conf is ni_pcmcia, and the module is tnt4882. You will > have > to make sure you enabled pcmcia support during make config. > > Frank > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-26 22:09:00
|
On Wed, 26 Jun 2002, Mitchell Ferschweiler wrote: > When I run make initally (and it invokes util/Setup), after I press > enter at the about screen, I get a blue screen where the kernel source > path dialog should be. If I press enter during the blue screen, It > quits and prints: > > ./Setup 24r command not found > make: *** [.config.stat] Error 127 > > > The laptop is running a clean install of SuSe 7.3. The same installer > works fine on my desktop (Debian Woody). > > Mitchell > Okay, the cvs should work now. It turns out debian's dialog program (I use debian) is actually cdialog which works slightly differently than the original. Also, the config scripts should be able to use whiptail now too instead of dialog. Frank |
From: Mitchell F. <mit...@ya...> - 2002-06-26 20:01:06
|
When I run make initally (and it invokes util/Setup), after I press enter at the about screen, I get a blue screen where the kernel source path dialog should be. If I press enter during the blue screen, It quits and prints: ./Setup 24r command not found make: *** [.config.stat] Error 127 The laptop is running a clean install of SuSe 7.3. The same installer works fine on my desktop (Debian Woody). Mitchell > > Would you try out the current cvs with your ni pcmcia card? The > interface > name for gpib.conf is ni_pcmcia, and the module is tnt4882. You will > have > to make sure you enabled pcmcia support during make config. > > Frank > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-26 17:38:14
|
On Wed, 26 Jun 2002, Mitchell Ferschweiler wrote: > Here are the messages from my /var/log/messages: > > Jun 26 08:38:56 linux cardmgr[365]: initializing socket 0 > Jun 26 08:38:56 linux cardmgr[365]: unsupported card in socket 0 > Jun 26 08:38:56 linux cardmgr[365]: product info: "National > Instruments", "PCMCIA-GPIB", "Rev. C", "" > Jun 26 08:38:56 linux cardmgr[365]: manfid: 0x010b, 0x4882 > Mitchell, Would you try out the current cvs with your ni pcmcia card? The interface name for gpib.conf is ni_pcmcia, and the module is tnt4882. You will have to make sure you enabled pcmcia support during make config. Frank |
From: Mitchell F. <mit...@ya...> - 2002-06-26 15:42:11
|
Here are the messages from my /var/log/messages: Jun 26 08:38:56 linux cardmgr[365]: initializing socket 0 Jun 26 08:38:56 linux cardmgr[365]: unsupported card in socket 0 Jun 26 08:38:56 linux cardmgr[365]: product info: "National Instruments", "PCMCIA-GPIB", "Rev. C", "" Jun 26 08:38:56 linux cardmgr[365]: manfid: 0x010b, 0x4882 Mitchell __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-25 02:14:28
|
On Mon, 24 Jun 2002, Mitchell Ferschweiler wrote: > No. The PCII/PCIIA card works only in PCII mode. In PCIIA mode, there > is an error about command bytes, identical to the one discussed > previously on the list. I can double check my settings, but I'm pretty > sure I had everything right. The PCII/PCIIA card didn't work at all > with the 3.1.4, but with the lastest CVS, the PCII mode works. > > Mitchell > You may be having an ioport conflict. In IIA mode, the pcII/IIA actually provides 16 ioports instead of the 8 used by a real IIA. The extra ioports are used to access the extra capabilities of the nat4882 chip. They are not allocated by the driver, and if something else is writing to them it could put the nat4882 into an unusable state. The extra ioports come after the first 8 with the same spacing of 0x400. I suppose I could add a new interface for 'pcII/IIA in IIA mode' that allocates all 16 ioports so a conflict will show up right away. Yes, I should do that. Frank |
From: Mitchell F. <mit...@ya...> - 2002-06-25 00:49:53
|
No. The PCII/PCIIA card works only in PCII mode. In PCIIA mode, there is an error about command bytes, identical to the one discussed previously on the list. I can double check my settings, but I'm pretty sure I had everything right. The PCII/PCIIA card didn't work at all with the 3.1.4, but with the lastest CVS, the PCII mode works. Mitchell --- frank mori hess <fm...@st...> wrote: > > > On Mon, 24 Jun 2002, Mitchell Ferschweiler wrote: > > > The pc2a card works with dma. The pc2/pc2a card works in pc2 mode. > In > > pc2a mode, the command bytes is still a problem. > > > > Do you mean rather it works in pc2a mode but not in pc2 mode? Also, > did > you remember to change the gpib config file as well as the board > switch > when switching between the modes? > > Frank > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-24 22:58:25
|
On Mon, 24 Jun 2002, Mitchell Ferschweiler wrote: > The pc2a card works with dma. The pc2/pc2a card works in pc2 mode. In > pc2a mode, the command bytes is still a problem. > Do you mean rather it works in pc2a mode but not in pc2 mode? Also, did you remember to change the gpib config file as well as the board switch when switching between the modes? Frank |
From: Mitchell F. <mit...@ya...> - 2002-06-24 17:12:04
|
The pc2a card works with dma. The pc2/pc2a card works in pc2 mode. In pc2a mode, the command bytes is still a problem. Thanks alot, amazing job doing that with no hardware :) Mitchell --- frank mori hess <fm...@st...> wrote: > The hang on dma writes with the pc2a should be fixed in cvs now. I > haven't tested any of the changes though (I should be getting some > hardware I can use soon). Also, the pc2 may possibly work now. > > Frank __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: frank m. h. <fm...@st...> - 2002-06-22 20:16:48
|
On Thu, 20 Jun 2002, Mitchell Ferschweiler wrote: > I am happy to do any testing with the hardware I can > get my hands on. > > Just tell me what I have to do :) > > Thanks, > Mitchell > > The first thing I need are the manufacurer/device id numbers. They should show up in one of your logs in the failure message if you try and plug your ni pcmcia gpib card into your laptop. Frank |
From: frank m. h. <fm...@st...> - 2002-06-21 23:47:22
|
On Wed, 19 Jun 2002, Mitchell Ferschweiler wrote: > Hello, > > I have a National Instruments PCIIa card. When I try > and write a string to a device (HP 3456A Digital > Voltmeter), it freezes my computer. The transaction is > complete, the instrument does what the command asked, > but the computer completely stops responding (can't > switch consoles, no response from the mouse, keyboard, > etc..) > Reading from the same device works just fine. > The hang on dma writes with the pc2a should be fixed in cvs now. I haven't tested any of the changes though (I should be getting some hardware I can use soon). Also, the pc2 may possibly work now. Frank |
From: frank m. h. <fm...@st...> - 2002-06-21 16:12:41
|
Have you read the section of the INSTALL file where it talks about setting up your kernel sources? In any case, the pcII card isn't working at the moment. I have a patch on my local machine that might make it work, but the sourceforge cvs seems to be down this morning. Frank On Fri, 21 Jun 2002, Ulhas Vaidya wrote: > > hi frank (and others on the list), > > i am trying to install the code (ver 3.1.4) on rh 7.1 running on kernel > 2.4.2-2 and gcc 2.96. The hardware is NI PCII card with addr 0x2b8, irq=7, > dma=0. the "make config" seems to doing fine. i do see a gpib.conf > created in /etc with correct hardware settings. > > however, make config fails. i have put the screen dump in the attchment > since i failed to understand why this should happen. it reports the > problems with header files in the kernel source. could you please help me > through this? i know the attachment is really big, but i thought it to be > better to provide all the info i could. > > thanks, > > ulhas > > > =============================================================================== > From, > """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" > Ulhas Vaidya Ph : 2152971 Extn. 2441 > Dept. of Condensed Matter Physics and FAX: 91-22-215 2110 > Materials Science > Tata Institute Of Fundamental Research, EMail: ul...@ti... > Colaba, MUMBAI. 400005 INDIA ul...@re... > """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" > =============================================================================== > |
From: Ulhas V. <ul...@ti...> - 2002-06-21 14:33:44
|
hi frank (and others on the list), i am trying to install the code (ver 3.1.4) on rh 7.1 running on kernel 2.4.2-2 and gcc 2.96. The hardware is NI PCII card with addr 0x2b8, irq=7, dma=0. the "make config" seems to doing fine. i do see a gpib.conf created in /etc with correct hardware settings. however, make config fails. i have put the screen dump in the attchment since i failed to understand why this should happen. it reports the problems with header files in the kernel source. could you please help me through this? i know the attachment is really big, but i thought it to be better to provide all the info i could. thanks, ulhas =============================================================================== From, """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Ulhas Vaidya Ph : 2152971 Extn. 2441 Dept. of Condensed Matter Physics and FAX: 91-22-215 2110 Materials Science Tata Institute Of Fundamental Research, EMail: ul...@ti... Colaba, MUMBAI. 400005 INDIA ul...@re... """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" =============================================================================== |
From: Mitchell F. <mit...@ya...> - 2002-06-21 00:36:44
|
I am happy to do any testing with the hardware I can get my hands on. Just tell me what I have to do :) Thanks, Mitchell --- frank mori hess <fm...@st...> wrote: > > > On Wed, 19 Jun 2002, Mitchell Ferschweiler wrote: > > > I also have a PCII/PCIIA card. When I configure it > to > > use the same dma, irq, and io address as my PCIIA, > and > > try to do ibtest, it results in the command bytes > > error: > > > > enter primary address for device (not interface > board) > > [0-30]: 26 > > trying to open pad = 26 on /dev/gpib0 ... > > clearing device.. > > gpib clear error > > ibsta = 0x130 > > iberr= 0 EDVR > > ibcnt = 0 > > > > Both of my tests were done with the CVS source. > > > > I also have a PCMCIA National Instruments card I > am > > interested in using with linux. Is there any > support > > or planned support for it? > > > > Thanks, > > Mitchell > > > > It looks like it's time for me to add a proper > compile-time option for > enabling verbose debugging output. I should be able > to put that in over > the weekend, and then we can debug the pc2a dma and > pc2a command problems. > NI pcmcia support is probably doable, if you are > willing to do the > testing. > > Frank > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |