public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn Ervin" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup and PCI Express Serial Cards
Date: Sat, 16 Jan 2010 10:25:52 -0600	[thread overview]
Message-ID: <13F9EC9DDF3943A3AECE7E2CC91B3731@AVERATECLAPTOP> (raw)
In-Reply-To: <Pine.LNX.4.61.1001161008440.31153@jimi.tabbweb.com>

How much was the card, and where can I get one?
I've been wanting a way to use my PC express slot in my laptop, hoping 
someone would make a synth to plug into it.  So far I have only found PC 
express video cards.
I would use one of these for my DecTalk synth, serial type.
Glenn
----- Original Message ----- 
From: "Trevor Astrope" <astrope@tabbweb.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, January 16, 2010 9:18 AM
Subject: Re: Speakup and PCI Express Serial Cards


This is what I am thinking as well. Just fyi, the card doesn't use any
special drivers and is compatible with the linux serial driver, which is
built into my kernel. The company supports linux as well. This is why I
bought it. It was just supposed to work. <grin>

Here is the output from setserial:

/dev/ttyS0, Line 0, UART: 16950/954, Port: 0xcc00, IRQ: 16
         Baud_base: 115200, close_delay: 50, divisor: 0
         closing_wait: 3000
         Flags: spd_normal skip_test

Does speakup get the serial port address from the bios? Since the card
isn't built-in, it would make sense that speakup can't find it, if this is
the case.

Using lspci, it does list the card and the serial port address and irq.

Btw, I did try changing the uart to 16550A, as the card supports this uart
type, but still no go.

Thanks,

Trevor

On Fri, 15 Jan 2010, Adam Myrow wrote:

> On Fri, 15 Jan 2010, Trevor Astrope wrote:
>
>> The serial port is provided by an Axxon pci express card.
>
> I think that's the problem.  So far as I know, Speakup still doesn't 
> support
> serial ports that aren't built-in to the computer.  Since computers 
> generally
> don't come with serial ports anymore, that is a huge problem.  Somehow, 
> there
> needs to be a way to pass IRQ and port addresses to the module so that 
> such
> PCI serial cards can work.  I've never encountered a PCI express serial 
> card,
> so don't know if any special support in the kernel is required, other than
> the obvious of having support for PCI express in the first place.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Trevor Astrope
 ` Kirk Reiser
   ` Trevor Astrope
 ` Adam Myrow
   ` Glenn Ervin
   ` Trevor Astrope
     ` Glenn Ervin [this message]
       ` Trevor Astrope
     ` Gregory Nowak
       ` Trevor Astrope
       ` William Hubbs
         ` Trevor Astrope
           ` Samuel Thibault
             ` Trevor Astrope
               ` Samuel Thibault
               ` Trevor Astrope

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13F9EC9DDF3943A3AECE7E2CC91B3731@AVERATECLAPTOP \
    --to=glennervin@cableone.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).