From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
Subject: Re: [Fwd: help with PCI hotplug and a PCI device enabled after boot]
Date: Wed, 17 Aug 2005 13:15:22 +0200 [thread overview]
Message-ID: <200508171315.32704@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <1124276090.4423.46.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Am Mittwoch, 17. August 2005 12:54 schrieb Mauro Carvalho Chehab:
>Rolf,
>
>Em Qua, 2005-08-17 às 11:47 +0200, Rolf Eike Beer escreveu:
>> Mauro Carvalho Chehab wrote:
>> > I need some help with PCI hotplug for allowing a new driver at
>> >Video4Linux.
>> >
>> > I need memory to set its internal registers. Is there a way to make
>> >PCI drivers to allocate a memory region for the board?
>>
>> Use dummyphp instead of fakephp. It should handle this case. You can find
>> it here: http://opensource.sf-tec.de/kernel/dummyphp-2.6.13-rc1.diff
>
> Didn't compile cleanly against -rc6. Do I need another patch or -mm
>series?
>
>WARNING: /lib/modules/2.6.13-rc6/kernel/drivers/pci/hotplug/dummyphp.ko
>needs unknown symbol pci_bus_add_resources
Damn, I should stop editing diffs by hand. Change this to
pci_bus_assign_resources and it should work. Sorry.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-17 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 9:02 [Fwd: help with PCI hotplug and a PCI device enabled after boot] Mauro Carvalho Chehab
2005-08-17 9:47 ` Rolf Eike Beer
2005-08-17 10:54 ` Mauro Carvalho Chehab
2005-08-17 11:15 ` Rolf Eike Beer [this message]
2005-08-17 11:53 ` Mauro Carvalho Chehab
2005-08-17 12:11 ` Rolf Eike Beer
2005-08-17 12:15 ` Mauro Carvalho Chehab
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=200508171315.32704@bilbo.math.uni-mannheim.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.