public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <johannes.thumshirn@men.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Andreas Werner <andreas.werner@men.de>,
	<linux-kernel@vger.kernel.org>,
	Johannes Thumshirn <johannes.thumshirn@men.de>
Subject: Re: [PATCH] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0
Date: Mon, 15 Dec 2014 14:23:37 +0100	[thread overview]
Message-ID: <20141215132335.GA3439@jtlinux> (raw)
In-Reply-To: <1414512692-1433-1-git-send-email-johannes.thumshirn@men.de>

On Tue, Oct 28, 2014 at 05:11:32PM +0100, Johannes Thumshirn wrote:
> Currently it is not possible to have a kernel with built-in MCB attached
> devices. This results out of the fact that mcb-pci requests PCI BAR 0, then
> parses the chameleon table and calls the driver's probe function before
> releasing BAR 0 again. When building the kernel with modules this is not a
> problem (and therefore it wasn't detected by my tests yet).
> 
> A solution is to only remap the 1st 0x200 bytes of a Chameleon PCI device.
> 0x200 bytes is the maximum size of a Chameleon v2 Table.
> 
> Also this patch stops disabling the PCI device on successful registration of MCB
> devices.
> 
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@men.de>
> Suggested-by: Bjorn Helgaas <bhelgaas@google.com>

Hi Greg,

Is there any specific reason why you didn't pick this one up for 3.19? Or did it
just got lost in your queue?

Thanks,
	Johannes


  parent reply	other threads:[~2014-12-15 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 16:11 [PATCH] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0 Johannes Thumshirn
2014-10-28 16:22 ` Bjorn Helgaas
2014-12-15 13:23 ` Johannes Thumshirn [this message]
2014-12-15 17:01   ` Greg Kroah-Hartman

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=20141215132335.GA3439@jtlinux \
    --to=johannes.thumshirn@men.de \
    --cc=andreas.werner@men.de \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.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