public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Date: Wed, 15 Jun 2011 18:58:47 +0200	[thread overview]
Message-ID: <4DF8E4C7.6060303@hartkopp.net> (raw)
In-Reply-To: <20110615165414.GA11421@ram-laptop>

On 15.06.2011 18:54, Ram Pai wrote:
> On Wed, Jun 15, 2011 at 06:40:35PM +0200, Oliver Hartkopp wrote:
>> On 12.06.2011 22:44, Ram Pai wrote:

>>> Looks like the kernel; by default, tries to allocate mem resource of size
>>> 0x4000000 each to the BARs of the cardbus bridge. This cannot be satisfied
>>> meeting all the constraints. The BIOS had not allocated the resource to
>>> begin with.
>>>
>>> Anyone knows if the default value can be reduced to something smaller?
>>> Or Should the resource requirements of cardbus bridge be made nice-to-have?
>>
>> Don't know ...
>>
>> Is anyone already working on this issue?
>>
>> I'm currently running 3.0.0-rc3-00055-gada9c93 which still does not work.
>>
>> Will say: 'Send more patches!' ... that i can test, if you still like the
>> problematic commit's idea ;-)
> 
> Oliver,
> 
> 	Yes. I am working on this. I will send you a patch soon; probably by
> the end of this week. See if they work for you.
> 
> Currently my thought is to make cardbus-bridge resource allocation
> nice-to-have, which means it will be attempted to allocate. But if in case of
> failures, we wont go the full length of releasing other resources to satisfy
> this resource.

Thanks for your fast feedback. I'm looking forward to help you.

Best regards,
Oliver

  reply	other threads:[~2011-06-15 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DEBCA3F.8050205@hartkopp.net>
     [not found] ` <BANLkTin_WHuy5MExNBHdeLiDmdmn7SZYkg@mail.gmail.com>
     [not found]   ` <4DED05C4.7050903@hartkopp.net>
     [not found]     ` <m3hb82wx6m.fsf@pullcord.laptop.org>
2011-06-07 18:36       ` sdhci-pci fails on 3.0.0-rc1 on Dell E6510 Oliver Hartkopp
2011-06-07 20:06         ` Oliver Hartkopp
2011-06-07 22:18           ` Yinghai Lu
2011-06-08  6:26             ` Oliver Hartkopp
2011-06-12 20:44               ` Ram Pai
2011-06-15 16:40                 ` Oliver Hartkopp
2011-06-15 16:54                   ` Ram Pai
2011-06-15 16:58                     ` Oliver Hartkopp [this message]
2011-06-15 18:31                 ` Bjorn Helgaas

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=4DF8E4C7.6060303@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=yinghai@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