mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: arvind vasudev <arvind_vasudev2000@yahoo.com>
To: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org
Subject: Question about allocating resources for a hotplug device
Date: Thu, 6 Nov 2008 11:18:17 -0800 (PST)	[thread overview]
Message-ID: <339187.36838.qm@web63901.mail.re1.yahoo.com> (raw)

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


      

                 reply	other threads:[~2008-11-06 19:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=339187.36838.qm@web63901.mail.re1.yahoo.com \
    --to=arvind_vasudev2000@yahoo.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®