From owner-freebsd-drivers@FreeBSD.ORG Sun Mar 13 16:13:05 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1110106566B for ; Sun, 13 Mar 2011 16:13:05 +0000 (UTC) (envelope-from brix@FreeBSD.org) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 804608FC12 for ; Sun, 13 Mar 2011 16:13:05 +0000 (UTC) Received: from druadan.brixandersen.dk (0x55534f5f.adsl.cybercity.dk [85.83.79.95]) by solow.pil.dk (Postfix) with ESMTPA id A70651CC00B for ; Sun, 13 Mar 2011 17:13:03 +0100 (CET) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-10--396967715" Mime-Version: 1.0 (Apple Message framework v1082) From: Henrik Brix Andersen In-Reply-To: <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> Date: Sun, 13 Mar 2011 17:12:59 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> To: freebsd-drivers@freebsd.org X-Pgp-Agent: GPGMail 1.3.2 X-Mailer: Apple Mail (2.1082) Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 16:13:05 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-10--396967715 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Mar 12, 2011, at 20:47, Henrik Brix Andersen wrote: > On Mar 12, 2011, at 19:49, Henrik Brix Andersen wrote: >> I am writing a driver for the GPIO part of the AMD CS5536 south = bridge (isab0), but have encountered a problem with resource allocation. >> The GPIO address (0x6100-0x61FF) is available through PCI BAR 1 as = seen in the output from pciconf(8): >>=20 >> isab0@pci0:0:15:0: class=3D0x060100 card=3D0x20901022 = chip=3D0x20901022 rev=3D0x03 hdr=3D0x00 >> vendor =3D 'Advanced Micro Devices (AMD)' >> device =3D 'CS5536 [Geode companion] ISA' >> class =3D bridge >> subclass =3D PCI-ISA >> bar [10] =3D type I/O Port, range 32, base 0x6000, size 8, = enabled >> bar [14] =3D type I/O Port, range 32, base 0x6100, size 256, = enabled >> bar [18] =3D type I/O Port, range 32, base 0x6200, size 64, = enabled >> bar [20] =3D type I/O Port, range 32, base 0x9d00, size 128, = enabled >> bar [24] =3D type I/O Port, range 32, base 0x9c00, size 64, = enabled >>=20 >> However, when I try to allocate the I/O port resource in the = minimalistic example below, I always get 0x1100-0x1100, not = 0x6100-0x61FF? >>=20 >> I have modelled the code after recommendation from John Baldwin in = http://lists.freebsd.org/pipermail/freebsd-acpi/2007-August/003964.html = but I must be doing something wrong... >=20 > Ahh, I just re-read Johns recommendation and realized that isab does = not support proxying resource allocations (yet). I will try adding that = functionality and report back. I have a patch ready for allowing the PCI-ISA bridge to proxy = SYS_RES_MEMORY and SYS_RES_IOPORT resource allocations from direct = children to the parent PCI bus. The patch is available from here: = http://people.freebsd.org/~brix/src-patches/isa_pci.c.diff Comments are more than welcome. I am still trying to figure out how to = allow children to allocate and setup interrupts through isab; any = pointers to what needs to be done in that regard are also very welcome = since I'm not having much luck with it so far... Regards, Brix --=20 Henrik Brix Andersen --Apple-Mail-10--396967715 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEUEARECAAYFAk187QsACgkQv+Q4flTiePit6QCfUEqNuN7j7WaBUy/sto7F+m1e jqgAmOD1fyvOaSNZrOFaFY3qAzz5nd4= =Bfi8 -----END PGP SIGNATURE----- --Apple-Mail-10--396967715-- From owner-freebsd-drivers@FreeBSD.ORG Sun Mar 13 20:13:49 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96F5E1065670; Sun, 13 Mar 2011 20:13:49 +0000 (UTC) (envelope-from philip.s.schulz@googlemail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA408FC15; Sun, 13 Mar 2011 20:13:48 +0000 (UTC) Received: by qyk27 with SMTP id 27so3612800qyk.13 for ; Sun, 13 Mar 2011 13:13:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=QdInNExF+MSQhbARAJ/ZemEoKLXTyOBEbJ4IlvQU0zk=; b=SCYdlTH7npCTRO1+Owmd9KILQjuj45LEPQs+gPpaJXQ5g7cCXFF12j/ZB+h4TiZ+81 Qlg8eNcrchVdAur++KUl8YVJ7sQ8ZkF82FwBwyOd5xe/JkEOYZ1kFpyOFSWXINU+4slU Cn8SCljmg4LAlYL1PKk2MGS1nD0AFuBcyxaRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=INaPj0seNPKWONOseGAe3LaLZmFA8nT+POlxI3MR4D1uD8xmXZH8fLc2z9wllIXSZy orL2LPOkwS9N7vc/0rTX9rHEJsdCisjmDaIoMF57oGxuJEncq1SptLkZsDYV24zIAnbZ ZC1pd5aRHJO6GHuX38MrOI2cyoi31xXaZCDXA= MIME-Version: 1.0 Received: by 10.229.29.9 with SMTP id o9mr9455799qcc.58.1300045526209; Sun, 13 Mar 2011 12:45:26 -0700 (PDT) Received: by 10.229.185.146 with HTTP; Sun, 13 Mar 2011 12:45:26 -0700 (PDT) In-Reply-To: References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> Date: Sun, 13 Mar 2011 20:45:26 +0100 Message-ID: From: Philip Schulz To: Henrik Brix Andersen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-drivers@freebsd.org Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 20:13:49 -0000 Hi Brix, 2011/3/13 Henrik Brix Andersen : [...] > Comments are more than welcome. I am still trying to figure out how to al= low children to allocate and setup interrupts through isab; any pointers to= what needs to be done in that regard are also very welcome since I'm not h= aving much luck with it so far... > I'm currently working on a driver for the exact same device, except I'm going for the I2C engine. Naturally, I'm facing some similar issues ;-) I created a new isab driver that attaches specifically to the relevant function in the CS5536 chip, mainly because I didn't want to modify the existing generic PCI-ISA bridge driver. In the attach routine of my isab driver, I used BUS_GET_RESOURCE_LIST() to obtain the list of resources that the parent PCI bus allocated for the device. On my system (Alix 1.C), that list contains the I/O ranges the device announces in the BARs. The bus_alloc_resource (and the bus_release_resource) method then checks whether said list contains the requested resource. If so, my isab driver requests the resource from the PCI bus and returns the requested resource to the requestor. If not, the request is passed through so it eventually ends up at the nexus device driver on x86. On my system, the resource list obtained from the PCI bus does not contain any interrupts. If I read the PCI bus code correctly, that's because the "Interrupt Pin" and "Interrupt Line" fields in the device's PCI config space are not set up. I didn't find any code that sets up those fields which leads me to believe that the fields should have been set up by the BIOS. As a result, my isab driver cannot request any interrupts from the PCI bus driver. However, that's not a problem because my I2C device driver ("glxiic") is a child of isa, not isab. So the tree is something like glxiix - isa - isab - pci - ... - nexus - root. If the glxiic driver request an interrupt resource, the request passes the isab driver at one point. Because the interrupt resource is not in the list mentioned above, the request is passed onto the parent, which is the PCI bus. The PCI bus will only handle those requests that come from direct children, so the request is again passed up. Eventually, the nexus device handles the request and the interrupt is allocated. As with other ISA device drivers, the interrupt number used by glxiic is set up via device.hints. However, the driver still needs to route the interrupt in the "Extended PIC" that is part of the CS5536 chip. I'm not sure if this is the right concept, but I found it to work out for my needs. Hope that helps, Phil. From owner-freebsd-drivers@FreeBSD.ORG Sun Mar 13 22:00:51 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F4E01065672 for ; Sun, 13 Mar 2011 22:00:51 +0000 (UTC) (envelope-from brix@freebsd.org) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 2D0208FC1D for ; Sun, 13 Mar 2011 22:00:50 +0000 (UTC) Received: from druadan.brixandersen.dk (0x55534f5f.adsl.cybercity.dk [85.83.79.95]) by solow.pil.dk (Postfix) with ESMTPA id EEC9D1CC004; Sun, 13 Mar 2011 23:00:49 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-4--376100012" From: Henrik Brix Andersen In-Reply-To: Date: Sun, 13 Mar 2011 23:00:46 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> To: Philip Schulz X-Pgp-Agent: GPGMail 1.3.2 X-Mailer: Apple Mail (2.1082) Cc: freebsd-drivers@freebsd.org Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 22:00:51 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-4--376100012 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, On Mar 13, 2011, at 20:45, Philip Schulz wrote: > I'm currently working on a driver for the exact same device, except > I'm going for the I2C engine. Naturally, I'm facing some similar > issues ;-) I am also writing a driver for the SMBus controller present in the = CS5536 chip... What a coincidence :) > I created a new isab driver that attaches specifically to the > relevant function in the CS5536 chip, mainly because I didn't want to > modify the existing generic PCI-ISA bridge driver. Interesting! However, I am not sure that is the best approach. The idea = of enabling direct children of the PCI-ISA bridge driver to allocate = BARs from the parent PCI bus would also benefit other drivers currently = present in FreeBSD, e.g. the sys/i386/i386/geode.c driver and ichwd(4) - = and it would imho make a for a cleaner, more generic solution. > On my system, the resource list obtained from the PCI bus does not > contain any interrupts. If I read the PCI bus code correctly, that's > because the "Interrupt Pin" and "Interrupt Line" fields in the > device's PCI config space are not set up. I didn't find any code that > sets up those fields which leads me to believe that the fields should > have been set up by the BIOS. As a result, my isab driver cannot > request any interrupts from the PCI bus driver. As far as I can tell, this can be set up by using pci_write_config(9)? = See intpm(4) for an example. > However, that's not a problem because my I2C device driver ("glxiic") > is a child of isa, not isab. So the tree is something like glxiix - > isa - isab - pci - ... - nexus - root. If the glxiic driver request an > interrupt resource, the request passes the isab driver at one point. > Because the interrupt resource is not in the list mentioned above, the > request is passed onto the parent, which is the PCI bus. The PCI bus > will only handle those requests that come from direct children, so the > request is again passed up. Eventually, the nexus device handles the > request and the interrupt is allocated. Hmm, but wouldn't that go against the design of the CS5536? The DIVIL = function block found in the CS5536 is not hooked up to the ISA bus. Regards, Brix --=20 Henrik Brix Andersen --Apple-Mail-4--376100012 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk19Po8ACgkQv+Q4flTiePiaYQCeKW1gMkpzdaXlbmlg+j0JwB9O Kz4An1zbplF2yXEFsb3mYCkhkt+TC4zM =kCfT -----END PGP SIGNATURE----- --Apple-Mail-4--376100012-- From owner-freebsd-drivers@FreeBSD.ORG Sun Mar 13 23:15:46 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41631106566B; Sun, 13 Mar 2011 23:15:46 +0000 (UTC) (envelope-from philip.s.schulz@googlemail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id CB1F18FC1D; Sun, 13 Mar 2011 23:15:45 +0000 (UTC) Received: by qyk35 with SMTP id 35so868734qyk.13 for ; Sun, 13 Mar 2011 16:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xkSL3sbMWE6VQqfNGBYe8XUinAIV5ZT0pGXFdV/zCgg=; b=aykk4qvHREpYbDXNEITGUXMKvTT4x86PXFuiSvb82Le0f7fCScHa1eC0D7BaALvAp6 wZC2RaPHX+rLcef+/MWBf/alSuh/UMh/p4SueCN7yRExWtuBK7gyWVyb4JMkMRyuslrZ Wn+sItgBJ6HPRvNPkj53UjDS75xRbfvd+0t6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wkfWd9HlZEtKeyZ3zHCQDQWKZw+Z5NiaHFHWw5As9Z7bBBvZp6lD1jiOKdpnTd7nOK GxHFpcqG8rl57Yiqzr1LA/VnHwwj7BG3P8YZ1HWOSBy1qCv0LpIKIrHspyA7NinUPAjk gzWmh1s1O6h8bGL8WztE+JrCgInWWk0D83qZc= MIME-Version: 1.0 Received: by 10.229.20.81 with SMTP id e17mr9542928qcb.20.1300058144756; Sun, 13 Mar 2011 16:15:44 -0700 (PDT) Received: by 10.229.185.146 with HTTP; Sun, 13 Mar 2011 16:15:44 -0700 (PDT) In-Reply-To: References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> Date: Mon, 14 Mar 2011 00:15:44 +0100 Message-ID: From: Philip Schulz To: Henrik Brix Andersen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-drivers@freebsd.org Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 23:15:46 -0000 Hi Brix, 2011/3/13 Henrik Brix Andersen : > Hi, > > On Mar 13, 2011, at 20:45, Philip Schulz wrote: [...] >> I created a new isab driver that attaches specifically to the >> relevant function in the CS5536 chip, mainly because I didn't want to >> modify the existing generic PCI-ISA bridge driver. > > Interesting! However, I am not sure that is the best approach. The idea o= f enabling direct children of the PCI-ISA bridge driver to allocate BARs fr= om the parent PCI bus would also benefit other drivers currently present in= FreeBSD, e.g. the sys/i386/i386/geode.c driver and ichwd(4) - and it would= imho make a for a cleaner, more generic solution. > I agree, however I didn't add the resource allocation stuff to the existing PCI-ISA bridge driver only because I didn't feel comfortable touching it. In fact, I think the code is probably generic enough to go into the existing driver -- but I don't know if its right. What I did does also enable direct children of isab to obtain BAR resources. Anyways, I think we're doing the same thing in principle, see for yourself ;-) https://phs.phisch.org/~phs/glx_isab.c https://phs.phisch.org/~phs/glx_isab.h >> On my system, the resource list obtained from the PCI bus does not >> contain any interrupts. If I read the PCI bus code correctly, that's >> because the "Interrupt Pin" and "Interrupt Line" fields in the >> device's PCI config space are not set up. I didn't find any code that >> sets up those fields which leads me to believe that the fields should >> have been set up by the BIOS. As a result, my isab driver cannot >> request any interrupts from the PCI bus driver. > > As far as I can tell, this can be set up by using pci_write_config(9)? Se= e intpm(4) for an example. > I don't know, maybe the SMBus IRQ can be routed and handled through the PCI layer. But I think you'd still have to set it up in the CS5536's XPIC, wouldn't you? For me it was just easier to route the SMBus IRQ to an unused legacy IRQ. >> However, that's not a problem because my I2C device driver ("glxiic") >> is a child of isa, not isab. So the tree is something like glxiix - >> isa - isab - pci - ... - nexus - root. [...] > > Hmm, but wouldn't that go against the design of the CS5536? The DIVIL fun= ction block found in the CS5536 is not hooked up to the ISA bus. > I made my glxiic driver a child of isa(4) because I didn't know where else to put it. After all, the DIVIL contains a bunch of devices on legacy I/O addresses such as e.g. UARTs which are already managed by ISA device drivers. Also, I couldn't get glxiic to be a direct child of isab unless I added a device_add_child() to isab_attach() - something I didn't want to do because it would be non-generic. Finally, glxiic can't be a PCI device driver because on my system, the entire DIVIL announces itself as one single PCI function (15.0, seems to be the same on your system). If glxiic attached to that function, isab wouldn't be able to attach anymore and I'd lose all of the other ISA devices. Of course, I could have added the ISA bridge logic to glxiic as well, but then I'd have glxiic+isab merged in one driver. Any thoughts? Regards, Phil. P.S.: For those interested, the data sheet can be found at http://www.linuxmedialabs.com/LMLCD/LMLGEOMG/AMDG_CS5536.pdf From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 14:42:38 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDC7D106566B for ; Mon, 14 Mar 2011 14:42:38 +0000 (UTC) (envelope-from brix@freebsd.org) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 892568FC16 for ; Mon, 14 Mar 2011 14:42:38 +0000 (UTC) Received: from druadan.brixandersen.dk (0x55534f5f.adsl.cybercity.dk [85.83.79.95]) by solow.pil.dk (Postfix) with ESMTPA id 906991CC006; Mon, 14 Mar 2011 15:42:36 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-7--315993280" From: Henrik Brix Andersen In-Reply-To: Date: Mon, 14 Mar 2011 15:42:33 +0100 Content-Transfer-Encoding: 7bit Message-Id: <4A3AEDA0-9AAA-4040-AC02-6416543A1B6D@freebsd.org> References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> To: Philip Schulz X-Pgp-Agent: GPGMail 1.3.2 X-Mailer: Apple Mail (2.1082) Cc: freebsd-drivers@freebsd.org Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 14:42:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-7--315993280 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, On Mar 14, 2011, at 00:15, Philip Schulz wrote: > I made my glxiic driver a child of isa(4) because I didn't know where > else to put it. After all, the DIVIL contains a bunch of devices on > legacy I/O addresses such as e.g. UARTs which are already managed by > ISA device drivers. Also, I couldn't get glxiic to be a direct child > of isab unless I added a device_add_child() to isab_attach() - > something I didn't want to do because it would be non-generic. > Finally, glxiic can't be a PCI device driver because on my system, the > entire DIVIL announces itself as one single PCI function (15.0, seems > to be the same on your system). If glxiic attached to that function, > isab wouldn't be able to attach anymore and I'd lose all of the other > ISA devices. Of course, I could have added the ISA bridge logic to > glxiic as well, but then I'd have glxiic+isab merged in one driver. Right. I use DEVICE_IDENTIFY(9) to check the PCI device ID of the isab = device and add a glxiic(4) child upon match. This way, glxiic(4) becomes a child of isab. Regards, Brix --=20 Henrik Brix Andersen --Apple-Mail-7--315993280 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk1+KVkACgkQv+Q4flTiePjWgQCaAw20bwDifOBmadAzmvv9Kjg6 uDcAn2hLt7AQkBBLeUxQxUbeE7OZ+QVY =Gk6m -----END PGP SIGNATURE----- --Apple-Mail-7--315993280-- From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 15:25:48 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 654F1106564A; Mon, 14 Mar 2011 15:25:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 39EF08FC1E; Mon, 14 Mar 2011 15:25:48 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id B915C46B38; Mon, 14 Mar 2011 11:25:47 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3DF4A8A01B; Mon, 14 Mar 2011 11:25:47 -0400 (EDT) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Mon, 14 Mar 2011 10:28:57 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <0A707516-C7D1-4441-B17B-1273B6C256B0@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201103141028.57324.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 14 Mar 2011 11:25:47 -0400 (EDT) Cc: Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 15:25:48 -0000 On Sunday, March 13, 2011 12:12:59 pm Henrik Brix Andersen wrote: > On Mar 12, 2011, at 20:47, Henrik Brix Andersen wrote: > > On Mar 12, 2011, at 19:49, Henrik Brix Andersen wrote: > >> I am writing a driver for the GPIO part of the AMD CS5536 south bridge (isab0), but have encountered a problem with resource allocation. > >> The GPIO address (0x6100-0x61FF) is available through PCI BAR 1 as seen in the output from pciconf(8): > >> > >> isab0@pci0:0:15:0: class=0x060100 card=0x20901022 chip=0x20901022 rev=0x03 hdr=0x00 > >> vendor = 'Advanced Micro Devices (AMD)' > >> device = 'CS5536 [Geode companion] ISA' > >> class = bridge > >> subclass = PCI-ISA > >> bar [10] = type I/O Port, range 32, base 0x6000, size 8, enabled > >> bar [14] = type I/O Port, range 32, base 0x6100, size 256, enabled > >> bar [18] = type I/O Port, range 32, base 0x6200, size 64, enabled > >> bar [20] = type I/O Port, range 32, base 0x9d00, size 128, enabled > >> bar [24] = type I/O Port, range 32, base 0x9c00, size 64, enabled > >> > >> However, when I try to allocate the I/O port resource in the minimalistic example below, I always get 0x1100-0x1100, not 0x6100-0x61FF? > >> > >> I have modelled the code after recommendation from John Baldwin in http://lists.freebsd.org/pipermail/freebsd-acpi/2007-August/003964.html but I must be doing something wrong... > > > > Ahh, I just re-read Johns recommendation and realized that isab does not support proxying resource allocations (yet). I will try adding that functionality and report back. > > I have a patch ready for allowing the PCI-ISA bridge to proxy SYS_RES_MEMORY and SYS_RES_IOPORT resource allocations from direct children to the parent PCI bus. > The patch is available from here: http://people.freebsd.org/~brix/src- patches/isa_pci.c.diff Yes, I think this looks good. > Comments are more than welcome. I am still trying to figure out how to allow children to allocate and setup interrupts through isab; any pointers to what needs to be done in that regard are also very welcome since I'm not having much luck with it so far... Well, it depends on where the interrupts come from. Is your device's interrupt actually tied to the INTx line or an MSI or MSI-X message on the ISA bridge? If so it will need to allocate the resource from the isab device. If your device is just using an ISA IRQ then you will probably need to use hints or some other method for figuring out which ISA IRQ your device is using. -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 15:44:34 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41B261065670; Mon, 14 Mar 2011 15:44:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 153B28FC0C; Mon, 14 Mar 2011 15:44:34 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BCFE246B89; Mon, 14 Mar 2011 11:44:33 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 515BB8A01B; Mon, 14 Mar 2011 11:44:33 -0400 (EDT) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Mon, 14 Mar 2011 11:34:12 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <3550EA55-ADDE-40AC-9C22-1FAC441A0BC8@freebsd.org> <4A3AEDA0-9AAA-4040-AC02-6416543A1B6D@freebsd.org> In-Reply-To: <4A3AEDA0-9AAA-4040-AC02-6416543A1B6D@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201103141134.12832.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 14 Mar 2011 11:44:33 -0400 (EDT) Cc: Subject: Re: Allocating resources to isab children X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 15:44:34 -0000 On Monday, March 14, 2011 10:42:33 am Henrik Brix Andersen wrote: > Hi, > > On Mar 14, 2011, at 00:15, Philip Schulz wrote: > > I made my glxiic driver a child of isa(4) because I didn't know where > > else to put it. After all, the DIVIL contains a bunch of devices on > > legacy I/O addresses such as e.g. UARTs which are already managed by > > ISA device drivers. Also, I couldn't get glxiic to be a direct child > > of isab unless I added a device_add_child() to isab_attach() - > > something I didn't want to do because it would be non-generic. > > Finally, glxiic can't be a PCI device driver because on my system, the > > entire DIVIL announces itself as one single PCI function (15.0, seems > > to be the same on your system). If glxiic attached to that function, > > isab wouldn't be able to attach anymore and I'd lose all of the other > > ISA devices. Of course, I could have added the ISA bridge logic to > > glxiic as well, but then I'd have glxiic+isab merged in one driver. > > Right. I use DEVICE_IDENTIFY(9) to check the PCI device ID of the isab device and add a glxiic(4) child upon match. > This way, glxiic(4) becomes a child of isab. We could probably use this to replace a similar hack in place for one of the smbus(4) controller drivers (I think viapro or some such?) -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 19:34:26 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4527C106566C for ; Mon, 14 Mar 2011 19:34:26 +0000 (UTC) (envelope-from jessefrgsmith@yahoo.ca) Received: from nm5-vm0.bullet.mail.bf1.yahoo.com (nm5-vm0.bullet.mail.bf1.yahoo.com [98.139.213.150]) by mx1.freebsd.org (Postfix) with SMTP id C96098FC12 for ; Mon, 14 Mar 2011 19:34:25 +0000 (UTC) Received: from [98.139.212.148] by nm5.bullet.mail.bf1.yahoo.com with NNFMP; 14 Mar 2011 19:21:17 -0000 Received: from [98.139.212.217] by tm5.bullet.mail.bf1.yahoo.com with NNFMP; 14 Mar 2011 19:21:17 -0000 Received: from [127.0.0.1] by omp1026.mail.bf1.yahoo.com with NNFMP; 14 Mar 2011 19:21:17 -0000 X-Yahoo-Newman-Id: 694705.24163.bm@omp1026.mail.bf1.yahoo.com Received: (qmail 81232 invoked from network); 14 Mar 2011 19:21:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=YFLpq4Y4rYsXurWAvp2pSRyV3T2o7OjpuOqGCQxKSNDEG1XA2jsKZ4Yid+Z+fXLT9/pS4Yw/BeoXX8oDkpFUlc3bXyzIZHdpLFkw7aQuIq5mDiw78awyECL6xk0bnh5xCmHEXWwmuVQ9YxXhMVi/NTqZRpgsu861B3cljwaW4Io= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1300130477; bh=0ruM804J2rVxCh7PNx8lrZ4pw3YhV3ezRucwFHOkg5E=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=o5ibsS5Hc7eSEXtWos4vzEoIpjJ7urUbXpbWYV7LfhTafEUSs717iuZefH+JhvRHHWnhImBzN4gkQRcVYWs+IHaghS/FANeVLDXCuiv8NJQzaBBBfurvHSHGeKjSAEJzswL1QNXc68RgMzRigGZv5a8M5/55+w8VgJu/ryUVtlM= Received: from [192.168.0.104] (jessefrgsmith@24.137.101.247 with plain) by smtp129.mail.mud.yahoo.com with SMTP; 14 Mar 2011 12:21:16 -0700 PDT X-Yahoo-SMTP: NPm1JouswBClX_uJxHJINmnKUpROdMKvLL0- X-YMail-OSG: XGDGGQkVM1lw2VC0aO1cNIuv80DcjiYayQQIycSPaex67EA b65UXMl_9tNDQ6uXs72b7ZkYvHx2AgI9gB1LvTcKyBBC0t9DaOBF2B8vDRS6 C9.3ooLN4EzNtIs_P.rzdhPijirwtYXIJ0u4UijjCNWBnj05vFxxnfGCwGDJ QhA_tivPhFCF_TtEmyBZR9wParlzlVQkiOGWwSO1sj7VG_S8Q2H5pNVzE2fO 7Z3UxJAUYJCSRUophUCCkS1QBWRELlQiE0hrdlF1jVX3Y4pTz_50N0ftcARj 6s36JAP.lTczkCtN6k1ku0ZbHoFxoF.wafw-- X-Yahoo-Newman-Property: ymail-3 From: Jesse Smith To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Mon, 14 Mar 2011 16:20:44 -0300 Message-ID: <1300130444.2334.75.camel@hp-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Subject: Drivers and firmware for an Intel WiFi 1000 series network card X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 19:34:26 -0000 Good-day, I hope this is the right list to bring this up. I'm new to FreeBSD and I'm trying to get the OS running on my laptop. Everything seems to work okay, except for my wireless card. It's an Intel WiFi 1000 series. >From what I've read, most open source OSes don't include the firmware for this device. I'm curious if A) FreeBSD has the drivers/firmware for this card? B) If not, is there anything I can do to help get the required driver/firmware? Thank you, Jesse From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 20:40:53 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26F3B106564A for ; Mon, 14 Mar 2011 20:40:53 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id AAD458FC1C for ; Mon, 14 Mar 2011 20:40:52 +0000 (UTC) Received: from mac2.unsane.co.uk (mac2.unsane.co.uk [10.10.10.191] (may be forged)) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p2EKep2n039373 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 14 Mar 2011 20:40:51 GMT (envelope-from vince@unsane.co.uk) Message-ID: <4D7E7D53.9090106@unsane.co.uk> Date: Mon, 14 Mar 2011 20:40:51 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-drivers@freebsd.org References: <1300130444.2334.75.camel@hp-laptop> In-Reply-To: <1300130444.2334.75.camel@hp-laptop> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Drivers and firmware for an Intel WiFi 1000 series network card X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 20:40:53 -0000 On 14/03/2011 19:20, Jesse Smith wrote: > Good-day, > > I hope this is the right list to bring this up. I'm new to FreeBSD and > I'm trying to get the OS running on my laptop. Everything seems to work > okay, except for my wireless card. It's an Intel WiFi 1000 series. > > >From what I've read, most open source OSes don't include the firmware > for this device. I'm curious if > > A) FreeBSD has the drivers/firmware for this card? > B) If not, is there anything I can do to help get the required > driver/firmware? Hi, I believe this uses the iwn driver, the manpage indicates that you would want to kldload iwn1000fw then kldload if_iwn The manpage lists how to make this persistent on boot. Vince > Thank you, > Jesse > > > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 21:55:45 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 168D7106566B for ; Mon, 14 Mar 2011 21:55:45 +0000 (UTC) (envelope-from jessefrgsmith@yahoo.ca) Received: from nm1-vm0.bullet.mail.ne1.yahoo.com (nm1-vm0.bullet.mail.ne1.yahoo.com [98.138.91.74]) by mx1.freebsd.org (Postfix) with SMTP id CB54F8FC0A for ; Mon, 14 Mar 2011 21:55:41 +0000 (UTC) Received: from [98.138.90.48] by nm1.bullet.mail.ne1.yahoo.com with NNFMP; 14 Mar 2011 21:40:40 -0000 Received: from [98.138.87.9] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 14 Mar 2011 21:40:39 -0000 Received: from [127.0.0.1] by omp1009.mail.ne1.yahoo.com with NNFMP; 14 Mar 2011 21:40:39 -0000 X-Yahoo-Newman-Id: 686574.72846.bm@omp1009.mail.ne1.yahoo.com Received: (qmail 31848 invoked from network); 14 Mar 2011 21:40:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=UXeruje3N5ZaTZqbYII1dOXHs4gmQoDFiWwqyTiqaz0rbWE5/YeI32qVJkr9ZA90HKUJx6qFJ8G84xqwRhxRR1m7cjKKNpuOe1DYwijLzlQjpglzPjXoSPsm8mWSNezJqvwZVyGAUh5pSRHXMl8Y/Zg3PtyeOdCNi/cUVxEID0g= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1300138839; bh=9PXh3CM7gZervQrn4f+9ByTLAbN5b9reyn6NHJrJMcs=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=IwfHsBzBBRkdQ8RjRc7QKdU0PWniBDxpNFEtMKKB/LJp6EPPym2pmNLyNIZlqmVD1H++kEHVnjlg9NrOQzyJeS/bAO40DQKItAT77xEtL3mriOeMJ3CnNnQ3wmXUlDWPjFnHVdy8ut+9njpPXdgRB6N3mfjE+yd8U34W7HsbpsA= Received: from [192.168.0.104] (jessefrgsmith@24.137.101.247 with plain) by smtp141.mail.mud.yahoo.com with SMTP; 14 Mar 2011 14:40:39 -0700 PDT X-Yahoo-SMTP: NPm1JouswBClX_uJxHJINmnKUpROdMKvLL0- X-YMail-OSG: RNj7AqUVM1lut.sbsfiXsDx6Ar3BU.3vDk.rWS2_Dd3qNx_ WD6t_B1v8Lpc2TtE8K9.dv4Y1jTermCCWI0OQ8bIxJ10m31XKKJAtUlhoJHP sXznEgbuX9I4TMDxMvUhfZRk0.F9AzMc1otLvn55G0Mh_rBy.QEoEBQ6lJ1m pbJR9H1sIj.Jfjn5Bv2plcCx3n.F9rjXREcMybAZ..gqhw_NvAZKUpz3jzEe 0mEPI3VPAPVk9EWfRTyRAiQGDAR9USXsyR4X8cjfJACk3Bfu5LJqe41rcudt 8Bcur1xhVEyatXK4bqFs.v6tuse6D44vk3w-- X-Yahoo-Newman-Property: ymail-3 From: Jesse Smith To: freebsd-drivers In-Reply-To: <4D7E7D53.9090106@unsane.co.uk> References: <1300130444.2334.75.camel@hp-laptop> <4D7E7D53.9090106@unsane.co.uk> Content-Type: text/plain; charset="UTF-8" Date: Mon, 14 Mar 2011 18:40:06 -0300 Message-ID: <1300138806.2117.5.camel@hp-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Subject: Re: Drivers and firmware for an Intel WiFi 1000 series network card X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 21:55:45 -0000 On 14/03/2011 19:20, Jesse Smith wrote: > Good-day, > > I hope this is the right list to bring this up. I'm new to FreeBSD and > I'm trying to get the OS running on my laptop. Everything seems to work > okay, except for my wireless card. It's an Intel WiFi 1000 series. > > >From what I've read, most open source OSes don't include the firmware > for this device. I'm curious if > > A) FreeBSD has the drivers/firmware for this card? > B) If not, is there anything I can do to help get the required > driver/firmware? > > Hi, > I believe this uses the iwn driver, the manpage indicates that you would > want to > kldload iwn1000fw > then > kldload if_iwn > > The manpage lists how to make this persistent on boot. > Vince Vince, Thank you for the quick reply. This seems to put me on the right track. I loaded the files you suggested and my wireless card now shows up in the output from ifconfig. I'm thinking this is a good sign. Unfortunately when I bring up the interface and scan for networks with it, it doesn't find my wireless LAN. I also notice the light on my laptop indicating the wireless device is working hasn't come on. I'm thinking maybe the driver is loaded, but not the firmware? At least based off my experience with Linux, that's my assumption. Where should I go to trouble-shoot this? Thank you again, Jesse From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 14 22:24:46 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BBC11065677 for ; Mon, 14 Mar 2011 22:24:46 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 832ED8FC1B for ; Mon, 14 Mar 2011 22:24:45 +0000 (UTC) Received: from mac2.unsane.co.uk (mac2.unsane.co.uk [10.10.10.191] (may be forged)) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p2EMOiO0044293 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 14 Mar 2011 22:24:44 GMT (envelope-from vince@unsane.co.uk) Message-ID: <4D7E95AC.2090508@unsane.co.uk> Date: Mon, 14 Mar 2011 22:24:44 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-drivers@freebsd.org References: <1300130444.2334.75.camel@hp-laptop> <4D7E7D53.9090106@unsane.co.uk> <1300138806.2117.5.camel@hp-laptop> In-Reply-To: <1300138806.2117.5.camel@hp-laptop> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Drivers and firmware for an Intel WiFi 1000 series network card X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 22:24:46 -0000 On 14/03/2011 21:40, Jesse Smith wrote: > > Vince, > > Thank you for the quick reply. This seems to put me on the right track. > I loaded the files you suggested and my wireless card now shows up in > the output from ifconfig. I'm thinking this is a good sign. > > Unfortunately when I bring up the interface and scan for networks with > it, it doesn't find my wireless LAN. I also notice the light on my > laptop indicating the wireless device is working hasn't come on. I'm > thinking maybe the driver is loaded, but not the firmware? At least > based off my experience with Linux, that's my assumption. > > Where should I go to trouble-shoot this? How familiar with wireless on freebsd are you? I will assume you are running 8.x if you are running 7.x or lower things work a little differently. for 8.x you need to create the wlan device and associate it with the physical interface, for iwn this would be ifconfig wlan0 create wlandev iwn0 then ifconfig wlan0 up scan to scan for nearby access points. The firmware for the card is contained in the iwnXXXXfw module you have loaded. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html has a full description. If you have done this already and are still having problems someone more familiar with the iwn driver will probably have to help I'm afraid. possibly try posting the output of ifconfig -a and the dmesg output from when you loaded the modules. Vince > Thank you again, > Jesse > > > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" From owner-freebsd-drivers@FreeBSD.ORG Tue Mar 15 00:20:33 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A60E5106564A for ; Tue, 15 Mar 2011 00:20:33 +0000 (UTC) (envelope-from jessefrgsmith@yahoo.ca) Received: from nm26.bullet.mail.ac4.yahoo.com (nm26.bullet.mail.ac4.yahoo.com [98.139.52.223]) by mx1.freebsd.org (Postfix) with SMTP id 56EBD8FC13 for ; Tue, 15 Mar 2011 00:20:33 +0000 (UTC) Received: from [98.139.52.194] by nm26.bullet.mail.ac4.yahoo.com with NNFMP; 15 Mar 2011 00:06:58 -0000 Received: from [98.139.52.150] by tm7.bullet.mail.ac4.yahoo.com with NNFMP; 15 Mar 2011 00:06:58 -0000 Received: from [127.0.0.1] by omp1033.mail.ac4.yahoo.com with NNFMP; 15 Mar 2011 00:06:58 -0000 X-Yahoo-Newman-Id: 355470.95446.bm@omp1033.mail.ac4.yahoo.com Received: (qmail 69412 invoked from network); 15 Mar 2011 00:06:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=3zjT9BnnyHCnT19rJrssfhmh2pcDZCkRZUtGPIndtMKci/oDTsDA3TQETAy7UGTEofAu5Juib9H/yuWVyznptblY1VjQpyhJ9uwsw0PLGKfKFhnEohVDOGNDNhxWJ76wPAOJaAwLREFeUlWfiR8DiwkR8ABwCGngc+cufRO2Egk= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1300147617; bh=3EL4VUQYZbHS6PzyHsVx2C7ZHzI/2MYpmWnP9QVPEXw=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=A7fuoAP7BSZjnAaBZhUPPnTrnZvg2Q0q35oWL+STZwUA2aHsglWQRclWmCbHF8wxB5gW6Zo0ji+P/is2NAnnkjH1/seI70YnaDVtgGtAKin0MtlI6U/YRBmjtJW9L2sb/X8HzwJqvM43vkm0TkL6xM7Ann69MCdmCFrcZ6gkbRE= Received: from [192.168.0.104] (jessefrgsmith@24.137.101.247 with plain) by smtp142.mail.mud.yahoo.com with SMTP; 14 Mar 2011 17:06:57 -0700 PDT X-Yahoo-SMTP: NPm1JouswBClX_uJxHJINmnKUpROdMKvLL0- X-YMail-OSG: j4eeOIcVM1nR362UcMvA9n6SV5fgQIyGpOjbEizp9aEnyHj 8pcBSexKySZ0JCaCLFleN1YhC6tEv0VkTxkD5jTJPeIKakSSsXESTGcrHvXI aJ3RilO7TRvt_u01MK8qUJ0WaWMcoCpIasQCREtaUHxqS9N8PUgCp3yfdoKq nhu5f67SXwZTLGgforPE_85caJoYKD0_v.UR7fz.KNRVbY3AS.ydvHHlWxfZ HHrTg1gbq7CT8tZ6pvWbz66L0nu290oxzF_Hne_DAhZsRbD2W6hkkQRlQrRz y7xPe3JN2VvhPcUpKLlGto2SsJKLYejwJrGMXh1nxPOr8JlHiwySiYnARy_E sClbrNNN_zS8Bw2IpX.m5s01OegId4hLKyXJ9hbvnQKuV X-Yahoo-Newman-Property: ymail-3 From: Jesse Smith To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Mon, 14 Mar 2011 21:06:24 -0300 Message-ID: <1300147584.2169.3.camel@hp-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Subject: Re: Drivers and firmware for an Intel WiFi 1000 series network card X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 00:20:33 -0000 > > Vince, > > Thank you for the quick reply. This seems to put me on the right track. > I loaded the files you suggested and my wireless card now shows up in > the output from ifconfig. I'm thinking this is a good sign. > > Unfortunately when I bring up the interface and scan for networks with > it, it doesn't find my wireless LAN. I also notice the light on my > laptop indicating the wireless device is working hasn't come on. I'm > thinking maybe the driver is loaded, but not the firmware? At least > based off my experience with Linux, that's my assumption. > > Where should I go to trouble-shoot this? > How familiar with wireless on freebsd are you? I will assume you are > running 8.x if you are running 7.x or lower things work a little > differently. > for 8.x you need to create the wlan device and associate it with the > physical interface, for iwn this would be > ifconfig wlan0 create wlandev iwn0 > then > ifconfig wlan0 up scan > to scan for nearby access points. > The firmware for the card is contained in the iwnXXXXfw module you > have > loaded. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html > has a full description. > > If you have done this already and are still having problems someone > more familiar with the iwn driver will probably have to help I'm > afraid. > possibly try posting the output of ifconfig -a and the dmesg output > from when you loaded the modules. > Vince Thanks again. It turns out I was missing the "ifconfig wlan0 create" step after loading the appropriate modules. (My wireless experience on FreeBSD up to this point has been nil.) Putting it all together I've managed to successful scan local networks. I appreciate your efforts to get me through this. Jesse From owner-freebsd-drivers@FreeBSD.ORG Sat Mar 19 18:10:15 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61772106564A for ; Sat, 19 Mar 2011 18:10:15 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 44C608FC14 for ; Sat, 19 Mar 2011 18:10:15 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Q10IE-0001BU-C7 for freebsd-drivers@freebsd.org; Sat, 19 Mar 2011 10:50:26 -0700 Message-ID: <31189503.post@talk.nabble.com> Date: Sat, 19 Mar 2011 10:50:26 -0700 (PDT) From: fdeliege To: freebsd-drivers@freebsd.org In-Reply-To: <4D5AB1A3.4040109@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: fdeliege@gmail.com References: <4D5AB1A3.4040109@gmail.com> Subject: Re: mps and Dell PERC H200 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2011 18:10:15 -0000 Hi Attila, I am getting a very similar problem except that the mps driver only picks 6 disks. This seem to correspond to bay 0,1,2,3,4,5,6. But maybe two of your disks were located in the internal bays (12, 13) ? Anyway, if you found any solution for this, I'd like to hear how you made it. Many thanks, Francois -- View this message in context: http://old.nabble.com/mps-and-Dell-PERC-H200-tp30933171p31189503.html Sent from the freebsd-drivers mailing list archive at Nabble.com. From owner-freebsd-drivers@FreeBSD.ORG Sat Mar 19 18:10:15 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E691B106566B for ; Sat, 19 Mar 2011 18:10:15 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id CA2358FC15 for ; Sat, 19 Mar 2011 18:10:15 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Q10JI-0001EQ-Bi for freebsd-drivers@freebsd.org; Sat, 19 Mar 2011 10:51:32 -0700 Message-ID: <31189504.post@talk.nabble.com> Date: Sat, 19 Mar 2011 10:51:32 -0700 (PDT) From: fdeliege To: freebsd-drivers@freebsd.org In-Reply-To: <4D5AB1A3.4040109@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: fdeliege@gmail.com References: <4D5AB1A3.4040109@gmail.com> Subject: Re: mps and Dell PERC H200 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2011 18:10:16 -0000 Hi Attila, I am getting a very similar problem except that the mps driver only picks 6 disks. This seem to correspond to bay 0,1,2,3,4,5,6. But maybe two of your disks were located in the internal bays (12, 13) ? Anyway, if you have found any solution for this, I'd like to hear how you made it. Many thanks, Francois -- View this message in context: http://old.nabble.com/mps-and-Dell-PERC-H200-tp30933171p31189504.html Sent from the freebsd-drivers mailing list archive at Nabble.com. From owner-freebsd-drivers@FreeBSD.ORG Sat Mar 19 18:10:17 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A057106566C for ; Sat, 19 Mar 2011 18:10:17 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 1D70E8FC08 for ; Sat, 19 Mar 2011 18:10:17 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Q10JI-0001ET-FT for freebsd-drivers@freebsd.org; Sat, 19 Mar 2011 10:51:32 -0700 Message-ID: <31189505.post@talk.nabble.com> Date: Sat, 19 Mar 2011 10:51:32 -0700 (PDT) From: fdeliege To: freebsd-drivers@freebsd.org In-Reply-To: <4D5AB1A3.4040109@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: fdeliege@gmail.com References: <4D5AB1A3.4040109@gmail.com> Subject: Re: mps and Dell PERC H200 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2011 18:10:17 -0000 Hi Attila, I am getting a very similar problem except that the mps driver only picks 6 disks. This seem to correspond to bay 0,1,2,3,4,5,6. But maybe two of your disks were located in the internal bays (12, 13) ? Anyway, if you have found any solution for this, I'd like to hear how you made it. Many thanks, Francois -- View this message in context: http://old.nabble.com/mps-and-Dell-PERC-H200-tp30933171p31189505.html Sent from the freebsd-drivers mailing list archive at Nabble.com.