From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Boucher Subject: Re: Major problem with serial driver and serial_pci_guess_board() Date: Tue, 26 Aug 2003 16:48:30 -0400 Sender: linux-serial-owner@vger.kernel.org Message-ID: <20030826204830.GA30364@endlich.mbsi.ca> References: <20030826182745.GA29051@endlich.mbsi.ca> <20030826201601.J28810@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from modemcable198.171-130-66.que.mc.videotron.ca ([66.130.171.198]:42505 "EHLO valve.mbsi.ca") by vger.kernel.org with ESMTP id S261353AbTHZUsk (ORCPT ); Tue, 26 Aug 2003 16:48:40 -0400 Content-Disposition: inline In-Reply-To: <20030826201601.J28810@flint.arm.linux.org.uk> List-Id: linux-serial@vger.kernel.org To: Russell King Cc: linux-serial@vger.kernel.org, arjanv@redhat.com, jsimon@linuxant.com Hi Russell, On Tue, Aug 26, 2003 at 08:16:01PM +0100, Russell King wrote: > On Tue, Aug 26, 2003 at 02:27:46PM -0400, Marc Boucher wrote: > > This problem appears to be present in all recent serial driver variants, > > including those in 2.6 and the latest RedHat Severn beta. It is > > a serious issue preventing our drivers from working correctly. > > My only interest is in 2.6, and the messages appear to be from a > 2.4 kernel. It does seem that we are detecting a device incorrectly, > since we aren't finding an 8250-compatible serial port. The messages indeed came from a 2.4 kernel, specifically 2.4.21-20.1.2024.2.1.nptl (included in RedHat Severn). But a similar problem occurs under 2.6 (tested with Arjan's 2.6.0-0.test4.1.32 rpm): Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A PCI: Enabling device 0000:00:08.0 (0000 -> 0003) ttyS2 at I/O 0x1428 (irq = 10) is a 8250 ttyS3 at I/O 0x1440 (irq = 10) is a 8250 [root@xe4000 root]# lspci -vvx -d 10b9:5457 00:08.0 Modem: ALi Corporation Intel 537 [M5457 AC-Link Modem] (prog-if 00 [Generic]) Subsystem: Hewlett-Packard Company: Unknown device 0025 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Unfortunately, we don't have tables of exclusion, nor do we have > a clean method to do that at present in any kernel. Would it not be possible to include devices we *know* use the confusing class IDs in the pci_serial_quirks table with an initialization routine that always fails? (under 2.6; for 2.4 we might need to implement something equivalent) > What I'd like to see is the output from lspci -vvx from a range of > PCI cards with this problem to see if there is characteristic (eg, > the PCI class/programming interface IDs) we can pick up on. I'll try to send you that info as we confirm other cases.. Many thanks for the quick response, Marc > > -- > Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux > http://www.arm.linux.org.uk/personal/aboutme.html >