sane-project-website/old-archive/1999-12/0037.html

55 wiersze
2.5 KiB
HTML

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Sat Dec 4 14:24:25 1999 PST" -->
<!-- sent="Sat, 4 Dec 1999 21:56:48 +0000 (GMT)" -->
<!-- name="Tim Waugh" -->
<!-- email="tim@cyberelk.demon.co.uk" -->
<!-- subject="Re: hexadecimal C syntax for serial ports" -->
<!-- id="" -->
<!-- inreplyto="1z92ih5l.fsf@localhost.localdomain" -->
<title>sane-devel: Re: hexadecimal C syntax for serial ports</title>
<h1>Re: hexadecimal C syntax for serial ports</h1>
<b>Tim Waugh</b> (<a href="mailto:tim@cyberelk.demon.co.uk"><i>tim@cyberelk.demon.co.uk</i></a>)<br>
<i>Sat, 4 Dec 1999 21:56:48 +0000 (GMT)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#37">[ date ]</a><a href="index.html#37">[ thread ]</a><a href="subject.html#37">[ subject ]</a><a href="author.html#37">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<li> <b>Previous message:</b> <a href="0036.html">Tim Carroll: "hexadecimal C syntax for serial ports"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<li> <b>Reply:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
On 4 Dec 1999, Tim Carroll wrote:<br>
<p>
<i>&gt; Newbie-me would say that the printer port would be /dev/ttyS1, as this</i><br>
<i>&gt; port has been used successfully to activate a printer in the past. Is</i><br>
<i>&gt; there a method to determine this address in hexadecimal form?</i><br>
<p>
A serial printer, perhaps, but I thought that the qcams plugged into the<br>
parallel port. It will be at something like 0x278, 0x378, or 0x3bc,<br>
unless it's on a PCI card or something. Check in your BIOS settings.<br>
<p>
Tim.<br>
*/<br>
<p>
<p>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<li> <b>Previous message:</b> <a href="0036.html">Tim Carroll: "hexadecimal C syntax for serial ports"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<li> <b>Reply:</b> <a href="0038.html">Tim Carroll: "Re: hexadecimal C syntax for serial ports"</a>
<!-- reply="end" -->
</ul>