From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Chuck Ebbert" <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org,
"Dominik Brodowski" <linux@dominikbrodowski.net>
Subject: Re: [solved] Yenta Cardbus allocation failure
Date: Tue, 19 Dec 2006 10:24:18 +0100 [thread overview]
Message-ID: <d9def9db0612190124i74a336b7j6dd0d0f638d5466e@mail.gmail.com> (raw)
In-Reply-To: <200612190359_MC3-1-D590-3237@compuserve.com>
On 12/19/06, Chuck Ebbert <76306.1226@compuserve.com> wrote:
> In-Reply-To: <d9def9db0612181612v657197ees925609243fc1ef65@mail.gmail.com>
>
> On Tue, 19 Dec 2006 01:12:07 +0100, Markus Rechberger wrote:
>
> > I went on with investigating that problem and found the problem,
> > though I'm not sure if that solution is acceptable..
> >
> > seems like the memory range gets preallocated in setup-bus.c, and
> > CARDBUS_MEM_SIZE defines that size.
> >
> > I changed
> > #define CARDBUS_MEM_SIZE (32*1024*1024)
> > to
> > #define CARDBUS_MEM_SIZE (48*1024*1024)
> >
> > and now the system is able to allocate the resources for the 3rd
> > pci/pcmcia function.
> >
> > Can anyone please have a closer look at it too? I think the whole
> > implementation isn't really good there..
> >
> > so this is the new output of iomem:
> > $ cat /proc/iomem
> > ...
> > 30000000-35ffffff : PCI Bus #02
> > 30000000-32ffffff : PCI CardBus #03
> > 36000000-360003ff : 0000:00:1f.1
> > 39000000-3bffffff : PCI CardBus #03
> > 39000000-39ffffff : 0000:03:00.0
> > 3a000000-3affffff : 0000:03:00.1
> > 3b000000-3bffffff : 0000:03:00.2 <- this one failed to allocate
> previously
>
> Wow, 3 regions of 16MB each! Your change fixes this problem for you, but
> what if someone needs four such regions?
>
I documented everything I found about that issue (even the allocated
resources in window$)
http://linuxtv.org/v4lwiki/index.php/Talk:Pinnacle/310c#PCI_allocation_failed
that's why I wrote that the current implementation isn't nice..
I'm currently on the cx88 driver (which needs that memory region) to
get my Pinnacle Cardbus device work..
I won't get back to the PCI subsystem before I'm done with it.
Markus
next prev parent reply other threads:[~2006-12-19 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 8:55 Chuck Ebbert
2006-12-19 9:24 ` Markus Rechberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 8:04 Markus Rechberger
2006-12-19 0:12 ` [solved] " Markus Rechberger
2006-12-21 3:40 ` Andrew Morton
2006-12-21 7:07 ` Linus Torvalds
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=d9def9db0612190124i74a336b7j6dd0d0f638d5466e@mail.gmail.com \
--to=mrechberger@gmail.com \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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®