From owner-freebsd-current Sun Feb 20 3:38:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 4EAA437BA81; Sun, 20 Feb 2000 03:38:39 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12MUhA-000MIb-0K; Sun, 20 Feb 2000 11:38:36 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA23236; Sun, 20 Feb 2000 11:40:55 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 11:38:51 +0000 (GMT) From: Doug Rabson To: Hellmuth Michaelis Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > Doug Rabson wrote: > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > pci0 > > > ata0: at 0x1f0 irq 14 on atapci0 > > > ata1: at 0x170 irq 15 on atapci0 > > > ... > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > think there will be some people who will find it cumbersome to have to > > > change the IO on a card that was working fine before. > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > driver doesn't really need that many IO ports so I'm sending this email to > > > both parties. > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > that range so it needs to split the range in to two or more pieces and > > only allocate ports which it actually needs. > > How do you come to that conclusion ? > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > The card in question allocates 3 portranges for this uses with each 0x40 > bytes in length. > > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > So where is the bug ? > > This all looks perfectly reasonable to me with the exception that we could > start argueing about whether it would be reasonable to split the allocation > ranges for the ISAC and to save (if at all possible, there are some more > registers at the end of the HSCX on the card) some bytes in the HSCX case. So you are saying that what we really have here is a simple i/o conflict and possibly the ISDN card can be reconfigured to use a non-conflicting address? If so, then everything is working correctly and the resource manager has pointed a possible hardware problem :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message