Bug 169125 - Silicom Ltd Dual / Double Serial Port PCMCIA card 2S100 does not work correctly
Summary: Silicom Ltd Dual / Double Serial Port PCMCIA card 2S100 does not work correctly
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pcmcia-cs   
(Show other bugs)
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-23 13:16 UTC by Tony McConnell
Modified: 2012-06-20 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 13:33:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tony McConnell 2005-09-23 13:16:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
Odd behaviour when a pcmcia serial port card is used.

When it's plugged in it is identified as:

Socket 0:
  funcid network_adapter
  lan_technology ARCnet
  vers_1 4.1, "Silicom Ltd.", "Double Serial Card", "2S100 1.00020702"
  config base 0x03f8 mask 0x0003 last_index 0x01
  cftable_entry 0x01 [default]
    Vcc Vnom 5V Iavg 70mA
    timing wait 1500ns
    io 0x0000-0x000f [lines=4] [16bit]
    irq mask 0x9eb8 [level]
  manfid 0x0089, 0x0301

Showing /var/log/messages:
Sep 23 14:03:35 laptop2 kernel: ttyS4 at I/O 0x100 (irq = 3) is a 16550A
Sep 23 14:03:35 laptop2 kernel: ttyS5 at I/O 0x108 (irq = 3) is a 16550A

Using /dev/ttyS4 is fine. 

However, using /dev/ttyS5 causes the characters sent to come out of /dev/ttyS4 and NOT out of /dev/ttyS5!

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Obtain a dual port serial pcmcia card
2. Plug into a PCMCIA slot
3. Attempt to use the serial ports.

Actual Results:  Use of /dev/ttyS4 or /dev/ttyS5 results in output always occuring on /dev/ttyS4.

Expected Results:  Use of /dev/ttyS4 should cause output on /dev/ttyS4. Use of /dev/ttyS5 should cause output on /dev/ttyS5.

Additional info:

This problem also exhibits on Redhat 9.0

Comment 1 Pete Zaitcev 2006-09-21 02:45:36 UTC
No, I've got no clue about the reason either.
Maybe it lies about its port bases somehow, so decodes impoperly.
I wonder what Windows says about the resultant port bases.

Comment 2 Jiri Pallich 2012-06-20 13:33:38 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.