Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754448AbXHRG72 (ORCPT ); Sat, 18 Aug 2007 02:59:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751561AbXHRG7T (ORCPT ); Sat, 18 Aug 2007 02:59:19 -0400 Received: from mx30.mail.ru ([194.67.23.238]:20920 "EHLO mx30.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751269AbXHRG7S (ORCPT ); Sat, 18 Aug 2007 02:59:18 -0400 From: Andrey Borzenkov To: Bjorn Helgaas Subject: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip Date: Sat, 18 Aug 2007 10:59:12 +0400 User-Agent: KMail/1.9.7 Cc: Andrew Morton , Samuel Ortiz , "Linus Walleij (LD/EAB)" , linux-kernel@vger.kernel.org, Michal Piotrowski , ambx1@neo.rr.com, linux-pcmcia@lists.infradead.org References: <200708112239.37475.arvidjaar@mail.ru> <200708131009.46641.bjorn.helgaas@hp.com> In-Reply-To: <200708131009.46641.bjorn.helgaas@hp.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6422843.rQnnpa6CLf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708181059.13741.arvidjaar@mail.ru> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3613 Lines: 97 --nextPart6422843.rQnnpa6CLf Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 13 August 2007, Bjorn Helgaas wrote: > On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote: > > This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable > > PnP by default; it is apparently enabled now and fails to activte IrDA > > completely. So it moves to post-2.6.22 regressions :) > > > > let me know which information you need > > > > [ 2192.666450] pnp: PnP ACPI init > > [ 2192.666589] ACPI: bus type pnp registered > > [ 2192.686035] pnp: Device 00:0a activated. > > [ 2192.686089] 00:0a: SMCf010 not responding at SIR 0x100, FIR 0x2e8; > > auto-configuring > > [ 2192.687610] pnp: Device 00:0a disabled. > > [ 2192.693179] pnp: Device 00:0a activated. > > [ 2192.693210] 00:0a: not responding at SIR 0x100, FIR 0x2e8; swapping > > SIR/FIR and reconfiguring > > [ 2192.694720] pnp: Device 00:0a disabled. > > [ 2192.701232] pnp: Device 00:0a activated. > > [ 2192.701259] 00:0a: responds at SIR 0x2e8, FIR 0x100 > > [ 2192.709309] pnp: PnP ACPI: found 12 devices > > [ 2192.709351] ACPI: ACPI bus type pnp unregistered > > > > .... > > > > [ 2207.986550] Detected unconfigured Toshiba laptop with ALi ISA bridge > > SMSC IrDA chip, pre-configuring device. > > [ 2207.986587] Activated ALi 1533 ISA bridge port 0x02e8. > > [ 2207.986602] Activated ALi 1533 ISA bridge port 0x02f8. > > [ 2207.986817] found SMC SuperIO Chip (devid=3D0x5a rev=3D00 base=3D0x0= 02e): > > LPC47N227 > > [ 2207.986851] smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, ir= q: > > 7, mode: 0x0e > > [ 2207.986873] smsc_ircc_present: can't get sir_base of 0x2e8 > > As of 2.6.23-rc2, we should have: > - probes for 8250 legacy devices (as in 2.6.21 and previous) > - smsc PNP probes turned off by default (2.6.21 and previous had no > PNP probes for smsc at all) > - some complicated PNP quirks for SMCf010 devices > > In other words, I think we're basically back where we started. Nope, it is a regression. > The 8250=20 > driver should find a ttyS3 device at 0x2e8, and it should claim those > ports, which will prevent smsc from claiming them. > This worked in 2.6.22 and does not work in 2.6.23. So something changed. I= =20 make a separate post about it because it is probably unrelated to smsc. > If you use "setserial /dev/ttyS3 none", the 8250 driver should release > the ports at 0x2e8, and then the smsc-ircc2 driver should be able to > load correctly. I think this is what we always had to do in the past, > right? > No; it "just worked". I do not even have setserial command ... installed on= e=20 but this does not support "none" > If that doesn't work, try removing the body of quirk_smc_enable() in > drivers/pnp/quirks.c in addition. It's possible that the quirk changes > the config in a way that messes up the smsc-ircc2 probe. > If I unload 8250 smsc-ircc2 loads just fine.=20 --nextPart6422843.rQnnpa6CLf Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBGxpjBR6LMutpd94wRAlitAKDNKmKkcTJ5vfGmzAReYgL6tl8V+QCeKa+J ai2j0zh+4wyszqXKIOXkuQk= =vtGR -----END PGP SIGNATURE----- --nextPart6422843.rQnnpa6CLf-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/