From erwvolz at bluewin.ch  Tue Aug 10 15:39:47 2004
From: erwvolz at bluewin.ch (Erwin Volz)
Date: Tue Aug 10 15:39:58 2004
Subject: [Linux-parport] PCI-Card VScom 210L not detected
In-Reply-To: <1087561917.3843.23.camel@vserv.lokales-netz.de>
References: <1087561917.3843.23.camel@vserv.lokales-netz.de>
Message-ID: <200408102139.47976.erwvolz@bluewin.ch>

Hello

I have now found the source of my problems, so I will close this tread.

Concerning the VScom 210L-Card, the problem was not parport_serial. The 
problem was connected with the setserial-script, which tried to autodetect 
all serial ports. 
This autodetecting somehow colliedid with parport_serial. It also detected 
only one of the two ports of the card, but that never bothered me much.
In the meantime I have changed the setserial-script to manual detection, and 
now everything works perfect.

It took some time to find the root of the problem, but I lerned to build my 
own kernel and several other things, so it was worth the trouble ;-)

Erwin Volz

Am Freitag, 18. Juni 2004 14.31 schrieb Erwin Volz:
> Hello
>
> I'm running Suse-Linux 9.1 (Suse-Kernel 2.6.5) on a VIA 686 chipset. As
> the parallel port is defect, I replaced it with a Titan VScom 210L,
> which ran without problem on the 2.4.19 and 2.4.20 Kernel for over a
> year.
>
> After installing Suse 9.1, I wasn't able to detect the parallel port
> anymore.
> Card-ID: 14d2:8021, which is a supported device
> Output from lspci -v:
> 0000:00:0a.0 Serial controller: Titan Electronics Inc VScom 210L 2 port
> serial and 1 port parallel adaptor (prog-if 02 [16550])
>         Subsystem: Titan Electronics Inc VScom 210L 2 port serial and 1
> port parallel adaptor
>         Flags: medium devsel, IRQ 9
>         I/O ports at ac00
>         I/O ports at b000 [size=8]
>         I/O ports at b400 [size=8]
>         I/O ports at b800 [size=8]
>         Memory at dc000000 (32-bit, non-prefetchable) [size=64]
>
> If I do a "modprobe parport_serial", I get the following response
> (dmesg):
>
> parport_pc: Via 686A parallel port disabled in BIOS
>
> which is not surprising, because it is deactivated in the BIOS, but it
> doesn't work either if I activate the parallel port in the BIOS
>
> If I do a "modprobe parport_serial io=0xb800 irq=auto", I get the
> following response (dmesg):
>
> parport_pc: Via 686A parallel port disabled in BIOS
> parport_serial: Unknown parameter `io'
>
> Parport_serial seems not to accept any parameters.
>
> Just to play a bit I made also "modprobe parport_pc io=0xb800 irq=auto
>
> parport 0xb800 (WARNING): CTR: wrote 0x0c, read 0x00
> parport 0xb800 (WARNING): DATA: wrote 0xaa, read 0x00
> parport 0xb800: You gave this address, but there is probably no parallel
> port there!
> parport0: PC-style at 0xb800 [PCSPP,TRISTATE,EPP]
>
> So parport_pc seems to accept the parameters, but of course when I
> started lp, it was unable to print, as parport serial was missing.
>
> Is this only a problem of the Suse-Kernel, or is it a general problem?
>
> Thank you for any help.
>
> Erwin
>
>
> _______________________________________________
> Linux-parport mailing list
> Linux-parport@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-parport

From sfiros at comcast.net  Fri Aug 13 01:34:02 2004
From: sfiros at comcast.net (Harisiadis)
Date: Fri Aug 13 05:34:34 2004
Subject: [Linux-parport] reading parallel status register
Message-ID: <000001c480f7$248f6030$6501a8c0@parents>

Did you ever get any information from your thread on parallel port
registers??
 
I need to know the same.
 
Please email me back,
 
Leo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infradead.org/pipermail/linux-parport/attachments/20040813/bd1d51cd/attachment.html
From troth at openavr.org  Fri Aug 13 13:08:39 2004
From: troth at openavr.org (Theodore A. Roth)
Date: Fri Aug 13 13:11:25 2004
Subject: [Linux-parport] getting read(2) to timeout
Message-ID: <Pine.LNX.4.53.0408130949010.8406@knuth.amplepower.com>

Hi,

I'm writing a user-space application for communicating with a home made
device via ppdev using EPP mode. If my device is present and powered up,
read(2) works fine, otherwise read(2) blocks.

Is there any way to have read(2) timeout so I can have the application
either give up or try something else? I have tried using the PPSETTIME
ioctl command, but obviously that is not doing what I want.

The only thing I can think of doing is to open(2) the device with
O_NONBLOCK, then catch the read(2) failure and retry a few times before
giving up.

I'm developing this on a debian system with a 2.6.6-1-686 kernel.

Thanks.

---
Ted Roth
PGP Key ID: 0x18F846E9
Jabber ID: troth@jabber.org

From heller at deepsoft.com  Fri Aug 13 13:35:19 2004
From: heller at deepsoft.com (Robert Heller)
Date: Fri Aug 13 13:35:27 2004
Subject: [Linux-parport] getting read(2) to timeout 
In-Reply-To: Your message of "Fri, 13 Aug 2004 10:08:39 PDT."
	<Pine.LNX.4.53.0408130949010.8406@knuth.amplepower.com> 
Message-ID: <200408131735.i7DHZK0s028662@athos.cs.umass.edu>



In message <Pine.LNX.4.53.0408130949010.8406@knuth.amplepower.com>, "Theodore A
. Roth" writes:
>Hi,
>
>I'm writing a user-space application for communicating with a home made
>device via ppdev using EPP mode. If my device is present and powered up,
>read(2) works fine, otherwise read(2) blocks.
>
>Is there any way to have read(2) timeout so I can have the application
>either give up or try something else? I have tried using the PPSETTIME
>ioctl command, but obviously that is not doing what I want.
>
>The only thing I can think of doing is to open(2) the device with
>O_NONBLOCK, then catch the read(2) failure and retry a few times before
>giving up.

open(2) w/O_NONBLOCK is the proper way to go.  Then you use select(2)
with a timeout.  See 'man 2 select' for how to do this. There is an
example code fragment (at least on my system -- WBL 3.0).  There is also
a select_tut man page in section 2 (man 2 select_tut), which is a
tutorial for select(2).

read(2) does not really have a timeout option itself (the is the nature
of how UNIX does I/O) -- this is what select is for (or at least one of
the things select is for).

>
>I'm developing this on a debian system with a 2.6.6-1-686 kernel.
>
>Thanks.
>
>---
>Ted Roth
>PGP Key ID: 0x18F846E9
>Jabber ID: troth@jabber.org
>
>_______________________________________________
>Linux-parport mailing list
>Linux-parport@lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-parport
                                     \/
Robert Heller                        ||InterNet:   heller@cs.umass.edu
http://vis-www.cs.umass.edu/~heller  ||            heller@deepsoft.com
http://www.deepsoft.com              /\FidoNet:    1:321/153

From keesan at iamjlamb.com  Sat Aug 14 19:22:00 2004
From: keesan at iamjlamb.com (Sindi Keesan)
Date: Sat Aug 14 19:22:22 2004
Subject: [Linux-parport] /dev/lp0:  No such device
In-Reply-To: <mailman.149.1091350814.18209.mailman@lists.infradead.org>
Message-ID: <Pine.LNX.4.44.0408141352210.22788-100000@foxxy.triohost.com>

I wrote to the list earlier when mdacon and parport_pc conflicted and was 
told to do:
insmod parport_pc io=0x378

This fixed mdacon.  (I did not have this problem on another computer with 
an MDA card with parallel port.)

On this computer dmesg tells me:
parport0:  PC-style at 0x378 [SPP]

This is the parallel port in my MDA (Hercules generic) card that was 
causing the parport_pc problem in this computer (the MDA screen got 
jumbled when parport_pc probed for addresses).

I have disabled the onboard parport.

I try to print using:

cat filename.txt > /dev/lp0

It looks like something might be happening but then I just get a screen 
prompt again.

On two other computers without MDA card, just the onboard parport, 
printing works, with both cat and ghostscript.

Is there something I can do to make printing work in linux on this
computer?  Might a different MDA card work better?  I have one MDA card
with no parport that I could try there.  I don't need two parports.  I
have a switch box to share one port.

Or can I do something with software instead of changing the hardware?  I
don't need to specify IRQ 7 on other computers but would it help here, and
if so do I do so while doing

insmod parport or parport-pc and how?  
insmod parport_pc io=0x378 irq=7 dma=3?  (I found this somewhere).

Probably not relevant, but the only odd thing about this computer is it
appears not to have a scroll buffer in linux (shift PgUp or PgDn don't
work).  The DOS kermit scroll buffer (PgUp) works fine.  It is circa 1997,
P I.  I am using SW7.1 (basiclinux 2).

Sindi Keesan (linux newbie)


From keesan at iamjlamb.com  Wed Aug 18 00:05:54 2004
From: keesan at iamjlamb.com (Sindi Keesan)
Date: Wed Aug 18 00:05:28 2004
Subject: [Linux-parport] /dev/lp0:  No such device
In-Reply-To: <Pine.LNX.4.44.0408141352210.22788-100000@foxxy.triohost.com>
Message-ID: <Pine.LNX.4.44.0408180003240.29508-100000@foxxy.triohost.com>

On Sat, 14 Aug 2004, Sindi Keesan wrote:

> I wrote to the list earlier when mdacon and parport_pc conflicted and was 
> told to do:
> insmod parport_pc io=0x378
> 
> This fixed mdacon.  (I did not have this problem on another computer with 
> an MDA card with parallel port.)
> 
> On this computer dmesg tells me:
> parport0:  PC-style at 0x378 [SPP]

> This is the parallel port in my MDA (Hercules generic) card that was 
> causing the parport_pc problem in this computer (the MDA screen got 
> jumbled when parport_pc probed for addresses).
> 
> I have disabled the onboard parport.
> 
> I try to print using:
> 
> cat filename.txt > /dev/lp0
> 
> It looks like something might be happening but then I just get a screen 
> prompt again.


> 
> On two other computers without MDA card, just the onboard parport, 
> printing works, with both cat and ghostscript.
> 
> Is there something I can do to make printing work in linux on this
> computer?  Might a different MDA card work better?

The answer is yes, this particular MGA card was the problem.  Another card 
(with different io address of 3BC) printed just fine.  I still have no 
idea how to get lp1 printing but changing the card should fix lp0 in 
linux.  Apparently some older hardware won't work with linux.  Another MGA 
card would do DOS llpro file transfer but not plip.  


From postmaster at infradead.org  Thu Aug 19 10:17:33 2004
From: postmaster at infradead.org (David Woodhouse)
Date: Thu Aug 19 10:32:58 2004
Subject: [Linux-parport] Administrivia
Message-ID: <1092925053.14552.2095.camel@hades.cambridge.redhat.com>

I'm about to change these lists to use VERP on outgoing mail --
including the recipient's address in the reverse-path of each mail to
make it easier to track bounces. 

Since the most reliable way to filter list mail is by its reverse-path,
I figured I ought to give a little bit of notice of the change -- so if
you were filtering on the reverse-path
'linux-XXX-bounces@lists.infradead.org' you will now need to match
'linux-XXX-bounces.*@lists.infradead.org' instead, if in fact you're not
already doing so.

-- 
dwmw2


From carol.jackson3 at sympatico.ca  Tue Aug 31 09:06:58 2004
From: carol.jackson3 at sympatico.ca (Carol Jackson)
Date: Tue Aug 31 10:37:41 2004
Subject: [Linux-parport] Driver for Video Blaster WebCam model CTWBCM
	(Parallel port)
Message-ID: <413477F2.2080709@sympatico.ca>

Hi,

I am looking for a driver for the above WebCam. I contacted CreativeLabs 
but they told me that they did not develop a driver
for that model (old model)  for Windows XP/Linux. Would anyone have done 
some work for that model?

Thank you in advance.

Bernard Jean Sapin







