Date: Thu, 13 Aug 2009 21:30:06 GMT From: =?iso-8859-1?B?QXVy6WxpZW4gTely6Q==?= <aurelien.mere@amc-os.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/136762: [ichsmb] ichsmb can't map resources of compatible IXP SMBus controller Message-ID: <200908132130.n7DLU63f068822@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/136762; it has been noted by GNATS. From: =?iso-8859-1?B?QXVy6WxpZW4gTely6Q==?= <aurelien.mere@amc-os.com> To: <bug-followup@FreeBSD.org>, <freebsd@amc-os.com> 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: <ATI IXP400 SMBUS Controller = (by KindMan)> 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 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18813"> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2 face=3DArial>Hi</FONT></DIV> <DIV><FONT size=3D2 face=3DArial></FONT> </DIV> <DIV><FONT size=3D2 face=3DArial>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. </FONT></DIV> <DIV><FONT size=3D2 face=3DArial></FONT> </DIV> <DIV><FONT size=3D2 face=3DArial>I patched intpm.c this way to make it = recognize the=20 controller :</FONT></DIV> <DIV><FONT size=3D2 face=3DArial></FONT> </DIV> <DIV><FONT size=3D2=20 face=3DArial>98a99,101<BR>> case=20 0x43721002:<BR>> = =20 device_set_desc(dev, "ATI IXP400 SMBus=20 Controller");<BR>> &nbs= p; =20 break;<BR></FONT></DIV> <DIV><FONT size=3D2 face=3DArial>When module is loaded, this output is = displayed=20 :</FONT></DIV> <DIV><FONT size=3D2 face=3DArial></FONT> </DIV> <DIV><FONT size=3D2 face=3DArial>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<BR>Aug 12 19:42:31 milkyway kernel: intsmb0: intr SMI enabled = revision=20 0<BR>Aug 12 19:42:31 milkyway kernel: intsmb0: Unsupported interrupt = mode<BR>Aug=20 12 19:42:31 milkyway kernel: device_attach: intsmb0 attach returned=20 6<BR></FONT></DIV> <DIV><FONT size=3D2 face=3DArial>Thanks for your help,</FONT></DIV> <DIV><FONT size=3D2 face=3DArial>Aur=E9lien</FONT></DIV> <DIV><FONT size=3D2 face=3DArial> </DIV></FONT></BODY></HTML> ------=_NextPart_000_0091_01CA1C69.C5CCFD50--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200908132130.n7DLU63f068822>