Bug 10949 - PCMCIA Card to RS232 don't work
Summary: PCMCIA Card to RS232 don't work
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCMCIA (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Alan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-21 11:50 UTC by Kazankov Alexander
Modified: 2012-05-22 12:37 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.23
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Kazankov Alexander 2008-06-21 11:50:54 UTC
Latest working kernel version:
Earliest failing kernel version:
Distribution: gentoo
Hardware Environment:
lspci - 04:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
PCMCIA Card - http://www.rovermate.com/site/accessories/home.nsf/descriptions/RMA19

Software Environment:
module-init-tools 3.4
pcmciautils-014
udev-115

Problem Description:
I try serial the modem, by means of the program minicom. At start on the modem bulb TR (terminal ready) lights up and hangs on a line of initialization. At initialization the line is entered: AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0, in the answer should be OK. Then ATZ, in answer OK. At use of the built in modem, all works.

Steps to reproduce:
1) run: minicom -o
2) choose: configuration and set serial device to the /dev/ttyS0
3) choose: init.


I modprob yenta_socket and insert PCMCIA Card:

lspci:
05:00.0 Serial controller: Oxford Semiconductor Ltd Unknown device 9505
05:00.1 Bridge: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 0 (Disabled)

dmesg:
Yenta: CardBus bridge found at 0000:04:06.0 [1179:ff10]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:04:06.0, mfunc 0x01a01b22, devctl 0x66
Yenta: ISA IRQ mask 0x0cf8, PCI irq 18
Socket status: 30000820
pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff
cs: IO port probe 0x4000-0x4fff: clean.
pcmcia: parent PCI bridge Memory window: 0xdc000000 - 0xdc0fffff
pcmcia: parent PCI bridge Memory window: 0x68000000 - 0x6bffffff
pccard: CardBus card inserted into slot 0
PCI: Enabling device 0000:05:00.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18
ttyS0: detected caps 00000700 should be 00000100
0000:05:00.0: ttyS0 at I/O 0x4460 (irq = 18) is a 16C950/954
ttyS1: detected caps 00000700 should be 00000100
0000:05:00.0: ttyS1 at I/O 0x4468 (irq = 18) is a 16C950/954
ttyS2: detected caps 00000700 should be 00000100
0000:05:00.0: ttyS2 at I/O 0x4470 (irq = 18) is a 16C950/954
ttyS3: detected caps 00000700 should be 00000100
0000:05:00.0: ttyS3 at I/O 0x4478 (irq = 18) is a 16C950/954

Why ttyS2,3 If interfaces only 2?
Comment 1 Komuro 2008-10-26 06:17:40 UTC

Could you try the kernel 2.6.27?
Comment 2 Kazankov Alexander 2008-11-09 21:52:32 UTC
Same result.

В Вск, 26/10/2008 в 06:17 -0700, bugme-daemon@bugzilla.kernel.org пишет:
> http://bugzilla.kernel.org/show_bug.cgi?id=10949
> 
> 
> 
> 
> 
> ------- Comment #1 from komurojun-mbn@nifty.com  2008-10-26 06:17 -------
> 
> 
> Could you try the kernel 2.6.27?
> 
> 
Comment 3 Dominik Brodowski 2010-02-19 18:17:55 UTC
Well, "lspci" seems to say "Quad UART" -- so I see no surprise that there are four ports being detected, even though only two ports are connected externally. Does a newer kernel work?

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