Andy Smith writes:
> Hi Martin,
>
> I have been using it successfully for a long time, but all I do is
> read whole lines from the serial device like:
>
> my $dev = '/dev/ttyUSB0';
> my $port = Device::SerialPort->new($dev);
>
> $port->baudrate(57600);
> $port->write_settings;
>
> open my $fh
On 27/10/17 15:38, Martin McCormick wrote:
> A perldoc of Device::SerialPort says that lookfor is
> supposed to block or hold until a character string emerges from
> the port as in /dev/ttyUSB0 or /dev/ttyS1. When I trace the
> code, it just loops as fast as it can and never holds to wait fo
Andy Smith writes:
> Hi Martin,
> I have been using it successfully for a long time, but all I do is
> read whole lines from the serial device like:
>
> my $dev = '/dev/ttyUSB0';
> my $port = Device::SerialPort->new($dev);
>
> $port->baudrate(57600);
> $port->write_settings;
>
> open my $fh,
On 10/26/2017 05:37 PM, Martin McCormick wrote:
The perl list I subscribe to seems to be on the fritz or I would
take the question there. I want to write code that receives from
a RS-232 port and I just can't seem to get it to do anything.
The port I am reading is connected to a scanner
On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote:
> The perl list I subscribe to seems to be on the fritz or I would
> take the question there. I want to write code that receives from
> a RS-232 port and I just can't seem to get it to do anything.
>
> The port I am reading i
Hi Martin,
On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote:
> If anybody has gotten the perl Device::SerialPort to
> work, I am interested to know what I am doing or not doing.
I have been using it successfully for a long time, but all I do is
read whole lines from the seri
I think you must load a module to identify those ports.
I also think that serial.o does such.
Once I read something about multiport boards in setserial man pages. Try
that. Theres also the serial howto you can check
- Original Message -
From: "hogan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; ; "LUV-talk
mailing list" <[EMAIL PROTECTED]>
Sent: Sunday, February 18, 2001 1:44 AM
Subject: Re: Serial ports - how to get them to coexist peacefully...
Only proble
> What I did when presented with this problem was to do a bit of surgery on
the old
> ISA board and change its IRQ to a spare in the computer I was using. I cut
one
> track solder a wire the new interrupt pad to get it to work. With setserial
and
> this setup I was able to run four Serial Terminals
hogan wrote:
>
> Can I make the onboard and oncard ttyS's play nice on same IRQ?
> or should I play musical jumpers until they're on separate IRQs?
>
What I did when presented with this problem was to do a bit of surgery on the
old
ISA board and change its IRQ to a spare in the computer I
On Sat, Feb 17, 2001 at 03:16:44AM +1100, hogan wrote:
> Can I make the onboard and oncard ttyS's play nice on same IRQ?
no.
> or should I play musical jumpers until they're on separate IRQs?
yes.
> Read something in 2.4.1 kernel config about making serial ports nice to one
> another when
On Friday 16 February 2001 17:27, Sean 'Shaleh' Perry wrote:
> > Can I make the onboard and oncard ttyS's play nice on same IRQ?
> > ... or should I play musical jumpers until they're on separate
> > IRQs?
>
> I would change the jumpers. Hoping the software ca multiplex is a
> recipe for disaster.
On Sat, Feb 17, 2001 at 03:16:44AM +1100, hogan wrote:
> P133, 48MB RAM, Debian Testing/Unstable (some bits from unstable) 2.2.17 (move
> to 2.4.1 on hold for time being whilst I read Rusty's howtos on netfilter etc.
> :) ).
>
> Have two onboard ports - ttyS0 and ttyS1 (IRQ 4&3 respectively)
> Hav
>
> Can I make the onboard and oncard ttyS's play nice on same IRQ?
> ... or should I play musical jumpers until they're on separate IRQs?
>
I would change the jumpers. Hoping the software ca multiplex is a recipe for
disaster.
> Read something in 2.4.1 kernel config about making serial ports
Quoting John Conover ([EMAIL PROTECTED]):
>
> How do you make the serial ports in 2.1 go faster than 38,400? The arg
> spd_vhi doesn't work any more, (setserial claims its depreciated, and
> it doesn't work,) but the docs claim that that is the way to do it.
You said in your previous posting that
John writes:
> How do you make the serial ports in 2.1 go faster than 38,400?
By telling them to. Speeds to 115200 are supported.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On Thu, 12 Mar 1998, Graham Lillico +44 1785 248131 wrote:
> Does anyone know why on boot up my Serial ports are displayed as /dev/tty00
> and
> /dev/tty01?
Don't know about the "/dev/" but my kernel (serial built-in) says:
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03
On Wed, 5 Mar 1997, Mark Lever wrote:
> getty processed on ttyS1 block modem access to cua1. When a getty is
> running (getty, agetty, uugetty or mgetty) and I try to run kermit
> (or minicom or statserial) I get a can't open device error. Why? They
> didn't used to. Is this a new kernel feature?
On Wed, 5 Mar 1997, Mark Lever wrote:
> getty processed on ttyS1 block modem access to cua1. When a getty is
> running (getty, agetty, uugetty or mgetty) and I try to run kermit (or
> minicom or statserial) I get a can't open device error. Why? They
> didn't used to. Is this a new kernel featu
On Wed, 5 Mar 1997,, Mark wrote:
Mark> Hi all,
Mark>
Mark> I just joined the mailing list since I just upgraded my 2 year
Mark> old Slackware installation to Debian 1.2.7 from ftp.debian.org.
Mark>
Mark> All in all, I'd have to say I'm pleased but there are a few
Mark> nagging ques
Sherwood Botsford <[EMAIL PROTECTED]> writes:
> CAVEAT I'm an ignoramlepuss about Linux/Debian.
[ good info about serial ports deleted ]
I do recall a discussion recently where someone posted text from the
maintainer of the Linux kernel's serial port code that essentially
said that cua* devices
21 matches
Mail list logo
