From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 13 21:30:06 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90AF2106568B for ; Thu, 13 Aug 2009 21:30:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7F1D58FC71 for ; Thu, 13 Aug 2009 21:30:06 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7DLU6FW068825 for ; Thu, 13 Aug 2009 21:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7DLU63f068822; Thu, 13 Aug 2009 21:30:06 GMT (envelope-from gnats) Date: Thu, 13 Aug 2009 21:30:06 GMT Message-Id: <200908132130.n7DLU63f068822@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?iso-8859-1?B?QXVy6WxpZW4gTely6Q==?= Cc: Subject: Re: kern/136762: [ichsmb] ichsmb can't map resources of compatible IXP SMBus controller X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?iso-8859-1?B?QXVy6WxpZW4gTely6Q==?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 21:30:06 -0000 The following reply was made to PR kern/136762; it has been noted by GNATS. From: =?iso-8859-1?B?QXVy6WxpZW4gTely6Q==?= To: , Cc: Subject: Re: kern/136762: [ichsmb] ichsmb can't map resources of compatible IXP SMBus controller Date: Thu, 13 Aug 2009 22:59:54 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_0091_01CA1C69.C5CCFD50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi After checks on other systems, it seems that the IXP SMBus controller = should not be recognized by ichsmb but by intpm. I tried changing the = declarations in intpm to add its PCI ID and, by loading intpm manually = afterwards, the resources of the device are correctly allocated. Problem = is that implementation seems incomplete, as SMI mode is not supported in = intpm, and driver still doesn't attach.=20 I patched intpm.c this way to make it recognize the controller : 98a99,101 > case 0x43721002: > device_set_desc(dev, "ATI IXP400 SMBus Controller"); > break; When module is loaded, this output is displayed : Aug 12 19:42:31 milkyway kernel: intsmb0: port 0x900-0x90f at device 20.0 on pci0 Aug 12 19:42:31 milkyway kernel: intsmb0: intr SMI enabled revision 0 Aug 12 19:42:31 milkyway kernel: intsmb0: Unsupported interrupt mode Aug 12 19:42:31 milkyway kernel: device_attach: intsmb0 attach returned = 6 Thanks for your help, Aur=E9lien ------=_NextPart_000_0091_01CA1C69.C5CCFD50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

After checks on other systems, it seems = that the=20 IXP SMBus controller should not be recognized by ichsmb but by intpm. I = tried=20 changing the declarations in intpm to add its PCI ID and, by loading = intpm=20 manually afterwards, the resources of the device are correctly = allocated. Problem is that implementation seems incomplete, as SMI mode = is not=20 supported in intpm, and driver still doesn't attach.

I patched intpm.c this way to make it = recognize the=20 controller :

98a99,101
>       case=20 0x43721002:
>         =      =20 device_set_desc(dev, "ATI IXP400 SMBus=20 Controller");
>        &nbs= p;     =20 break;

When module is loaded, this output is = displayed=20 :

Aug 12 19:42:31 milkyway kernel: = intsmb0: <ATI=20 IXP400 SMBUS Controller (by KindMan)> port 0x900-0x90f at device 20.0 = on=20 pci0
Aug 12 19:42:31 milkyway kernel: intsmb0: intr SMI enabled = revision=20 0
Aug 12 19:42:31 milkyway kernel: intsmb0: Unsupported interrupt = mode
Aug=20 12 19:42:31 milkyway kernel: device_attach: intsmb0 attach returned=20 6

Thanks for your help,

Aur=E9lien

------=_NextPart_000_0091_01CA1C69.C5CCFD50--