headers
VL-axnet-w- | 1 Aug 2004 01:14
Picon
Favicon

RE: find a small program or a procedure

Yes, that program have to read one byte from the parallel port,
and write it into a file one after the other as long as the
prallel port is readable.
I tested the command: "cat </dev/parport0 >>file.txt", but
the result is none, because - I think - the parallel port isn't
initialised to input-state.

Greetings,
Laci

> -----Original Message-----
> From: Sindi Keesan
> Sent: Friday, July 30, 2004 6:24 PM
> To: VL-axe-w
> Cc: linux-parport <at> lists.infradead.org
> Subject: Re: [Linux-parport] find a small program or a procedure
> 
> 
> Please explain in more detail what you mean here.
> Do you want to find a program that will take raw data that 
> comes to the 
> parallel port, and will make a file from it?
> 
> Parallel port data acquisition software?
> Serial port data acquisition is more common, sometimes using special 
> hardware (data acquisition card).
> 
> 
> 
> On Fri, 30 Jul 2004, VL-axe-w wrote:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Erwin Volz | 10 Aug 2004 21:39
Picon
Favicon

Re: PCI-Card VScom 210L not detected

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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Harisiadis | 13 Aug 2004 07:34
Picon

reading parallel status register

Did you ever get any information from your thread on parallel port registers??

 

I need to know the same.

 

Please email me back,

 

Leo

_______________________________________________
Linux-parport mailing list
Linux-parport <at> lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-parport
Permalink | Reply | 1 comment |
headers
Theodore A. Roth | 13 Aug 2004 19:08

getting read(2) to timeout

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 <at> jabber.org
Permalink | Reply | 1 comment |
headers
Robert Heller | 13 Aug 2004 19:35
Favicon

Re: getting read(2) to timeout


In message <Pine.LNX.4.53.0408130949010.8406 <at> 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 <at> jabber.org
>
>_______________________________________________
>Linux-parport mailing list
>Linux-parport <at> lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-parport
                                     \/
Robert Heller                        ||InterNet:   heller <at> cs.umass.edu
http://vis-www.cs.umass.edu/~heller  ||            heller <at> deepsoft.com
http://www.deepsoft.com              /\FidoNet:    1:321/153
Permalink | Reply | 0 comments |
headers
Sindi Keesan | 15 Aug 2004 01:22

/dev/lp0: No such device

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)
Permalink | Reply | 1 comment |
headers
Sindi Keesan | 18 Aug 2004 06:05

Re: /dev/lp0: No such device

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.
Permalink | Reply | 0 comments |
headers
David Woodhouse | 19 Aug 2004 16:17
Favicon

Administrivia

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 <at> lists.infradead.org' you will now need to match
'linux-XXX-bounces.* <at> lists.infradead.org' instead, if in fact you're not
already doing so.

--

-- 
dwmw2

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Carol Jackson | 31 Aug 2004 15:06
Picon
Favicon

Driver for Video Blaster WebCam model CTWBCM (Parallel port)

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
Permalink | Reply | 0 comments |

Gmane