LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Question about allocating resources for a hotplug device
@ 2008-11-06 19:18 arvind vasudev
0 siblings, 0 replies; only message in thread
From: arvind vasudev @ 2008-11-06 19:18 UTC (permalink / raw)
To: linux-kernel, jbarnes
Increasing the scope to include more people.
Thanks,
Arvind.
--- On Wed, 11/5/08, arvind vasudev <arvind_vasudev2000@yahoo.com> wrote:
> From: arvind vasudev <arvind_vasudev2000@yahoo.com>
> Subject: Question about allocating resources for a hotplug device
> To: linux-pci@vger.kernel.org
> Date: Wednesday, November 5, 2008, 11:43 AM
> Hello,
>
> I am not sure if this is the right place to ask this
> question, so please let me know if there is another list
> that I should post this on.
>
> The question is that I am hotpluging a bridge in a slot,
> and plugging in a device behind the bridge. When I do this,
> I can see that the kernel enumerates the bridge and the
> device (assigns bus and device numbers to them), but it
> fails to allocate the memory resource that the new device is
> requesting for 1MB. After tracing the kernel code (version
> 2.6.23), I can see that call to pci_bus_assign_resources()
> fails. In the normal initialization sequence, it appears as
> though the BAR registers of a device have to be initialized
> before the call to pci_bus_assign_resources(), possibly by
> the BIOS.
>
> How should the BAR registers of the new device be
> initialized in the case of hotplug?
>
> Thanks,
> Arvind.
>
>
>
>
> --
> To unsubscribe from this list: send the line
> "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-11-06 19:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-06 19:18 Question about allocating resources for a hotplug device arvind vasudev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).