Date: Tue, 29 Sep 2015 06:52:32 -0700 From: John Baldwin <jhb@freebsd.org> To: "Pokala, Ravi" <rpokala@panasas.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: bus_.*_resource() and rid Message-ID: <6031931.XlHKqU7cUF@ralph.baldwin.cx> In-Reply-To: <D22EDCCD.146B0A%rpokala@panasas.com> References: <D214E963.145154%rpokala@panasas.com> <D22ED71B.146AE6%rpokala@panasas.com> <D22EDCCD.146B0A%rpokala@panasas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, September 28, 2015 07:04:27 PM Pokala, Ravi wrote: > -----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 = > >bus_get_resource_list(device_get_parent(dev), dev); > > rid = 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. :-) Yeah, it's only really for bus drivers to use internally when enumerating resources (e.g. ACPI uses it when walking _CRS so that if there are multiple memory resources they use rids 0 .. N). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6031931.XlHKqU7cUF>