From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [204.233.198.50] (helo=linserver.romualt.dhs.org) by speech.braille.uwo.ca with smtp (Exim 3.35 #1 (Debian)) id 17AzhW-0000q8-00 for ; Thu, 23 May 2002 17:00:46 -0400 Received: (qmail 2424 invoked by uid 1002); 23 May 2002 21:00:04 -0000 Date: Thu, 23 May 2002 16:00:04 -0500 From: Gregory Nowak To: speakup@braille.uwo.ca Subject: Re: US Robotics 56K Voice PCI Message-ID: <20020523160004.A2401@romualt.dhs.org> References: <002401c20298$18b38d20$ec7d0cd8@oemcomputer> <20020523153511.A2310@romualt.dhs.org> <000401c2029a$63fded00$d6780cd8@oemcomputer> <20020523154953.A2377@romualt.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020523154953.A2377@romualt.dhs.org>; from greg@romualt.dhs.org on Thu, May 23, 2002 at 03:49:53PM -0500 Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Just to add to this, here is my serial portion of /usr/src/linux/.config for kernel 2.4.17. CONFIG_SERIAL=y CONFIG_SERIAL_CONSOLE=y # CONFIG_SERIAL_ACPI is not set CONFIG_SERIAL_EXTENDED=y # CONFIG_SERIAL_MANY_PORTS is not set CONFIG_SERIAL_SHARE_IRQ=y # CONFIG_SERIAL_DETECT_IRQ is not set # CONFIG_SERIAL_MULTIPORT is not set # CONFIG_HUB6 is not set # CONFIG_SERIAL_NONSTANDARD is not set All you need to activate here are SERIAL_EXTENDED and SERIaL_SHARE_IRQ. I've just included my entire serial config for purposes of context. Greg On Thu, May 23, 2002 at 03:49:53PM -0500, Gregory Nowak wrote: > I'm sorry about that. I forgot that you might not have gotten around to building your own kernel yet. I haven't used zipspeak for 2 years or so. Does anyone out there remember if the standard zipspeak kernel comes with extended serial options configured into it. If not, then you will need to build your own kernel. If you're up to reading a couple of docs, it is not as hard as it sounds, as long as you know what hardware you have in your system. > Greg > >