Date: Mon, 28 Sep 2015 19:04:27 +0000 From: "Pokala, Ravi" <rpokala@panasas.com> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: bus_.*_resource() and rid Message-ID: <D22EDCCD.146B0A%rpokala@panasas.com> In-Reply-To: <D22ED71B.146AE6%rpokala@panasas.com> References: <D214E963.145154%rpokala@panasas.com> <1637146.Rv3dkk0gMi@ralph.baldwin.cx> <D22E9D9D.146A5C%rpokala@panasas.com> <3440562.CxbPY93XVj@ralph.baldwin.cx> <D22ED71B.146AE6%rpokala@panasas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: Ravi Pokala <rpokala@panasas.com> Date: 2015-09-28, Monday at 11:52 To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: bus_.*_resource() and rid >Hmm... perhaps: > > struct resource_list *rl =3D >bus_get_resource_list(device_get_parent(dev), dev); > rid =3D resource_list_add_next(rl, SYS_RES_IOPORT, start, end, count); > >I'll try that. Err, never mind, resource_list_add_next() doesn't do what I was thinking it did. So, forget I said that. :-) -Ravi >Thanks! > >-Ravi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D22EDCCD.146B0A%rpokala>