linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <iweiny@acm.org>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Cardbus issues on TiBook
Date: Thu, 06 Sep 2001 13:19:36 -0700	[thread overview]
Message-ID: <3B97DA58.6894B342@acm.org> (raw)


As some of you may know I am trying to get an IBM microdrive working on
my TiBook.  I know there is an issue with irq's which I am trying to
work out but I have run into another issue I don't understand.

I get the following message in my startup:

kernel: Can't get bus-range for /pci@f2000000/cardbus@1a

I rsync'ed with Ben H's kernel recently and I found that the ioports and
memory ranges I had set for cardmgr were not working anymore.  So I
started changing them.  In my efforts to find ranges that worked I found
that "cat /proc/ioports" would result in a segfault.  From what I can
tell it is running off the end of the buffer in vsnprintf?

Before the Cardbus modules are loaded "cat /proc/ioports" works fine.

So my question is, what does the above message mean?  It is something
which is worked around later, or could it be the root of my problem?

Thanks,
Ira Weiny
iweiny@acm.org

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-09-06 20:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 20:19 Ira Weiny [this message]
2001-09-06 21:10 ` Cardbus issues on TiBook Armando Di Cianno
2001-09-07 16:24   ` Ira Weiny
2001-09-07 19:46     ` Armando Di Cianno
2001-09-13  8:19   ` PCMCIA issues Timothy A. Seufert
2001-09-13 12:54     ` Benjamin Herrenschmidt
2001-09-06 21:10 ` Cardbus issues on TiBook Benjamin Herrenschmidt
2001-09-07 16:36   ` Ira Weiny
2001-09-07 17:06     ` Benjamin Herrenschmidt
2001-09-07 23:47       ` System map in XMON (was: Cardbus issues on TiBook) Ira Weiny
2001-09-08 12:45         ` Benjamin Herrenschmidt
2001-09-06 23:01 ` Cardbus issues on TiBook Marcus O.C. Metzler

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=3B97DA58.6894B342@acm.org \
    --to=iweiny@acm.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).