From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Martin Drohmann <m_droh01@uni-muenster.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why does printk helps PCMCIA card to initialise?
Date: Sun, 20 Feb 2005 12:38:17 +0000 [thread overview]
Message-ID: <20050220123817.A12696@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42187819.5050808@uni-muenster.de>; from m_droh01@uni-muenster.de on Sun, Feb 20, 2005 at 12:44:25PM +0100
On Sun, Feb 20, 2005 at 12:44:25PM +0100, Martin Drohmann wrote:
> #ifdef CONFIG_PCI
> if (s->cb_dev) {
> ret = pci_bus_alloc_resource(s->cb_dev->bus, res, num, 1,
> min, 0, pcmcia_align, &data);
> } else
> #endif
> - printk("This line will never be printed, but it helps!!!");
If you added this, you've done much more than just adding it. Look
two lines above and realise that you've just changed what the "else"
clause conditionalises.
> ret = allocate_resource(&ioport_resource, res, num, min,
> ~0UL,
> 1, pcmcia_align, &data);
So, with your printk in place, we try pci_bus_alloc_resource. If that
succeeds or fails, we completely stomp on that with allocate_resource.
Bad. Very bad.
The first thing that needs solving is why you're getting the "odd IO
request" crap. That may explain why the resource can't be allocated.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2005-02-20 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 11:44 Why does printk helps PCMCIA card to initialise? Martin Drohmann
2005-02-20 9:25 ` Vicente Feito
2005-02-20 12:38 ` Russell King [this message]
2005-02-21 9:17 ` Russell King
2005-02-21 10:37 ` Andrew Morton
2005-02-21 20:20 ` Linus Torvalds
[not found] <3zXLc-3vg-13@gated-at.bofh.it>
[not found] ` <3zYxA-4dY-13@gated-at.bofh.it>
[not found] ` <3AhTz-3pR-15@gated-at.bofh.it>
2005-02-22 10:14 ` Martin Drohmann
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 22:34 David Hinds
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=20050220123817.A12696@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m_droh01@uni-muenster.de \
/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