From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 19/20] [POWERPC] pci32: 4xx embedded platforms want to reassign all PCI resources
Date: Thu, 13 Dec 2007 15:59:46 -0600 [thread overview]
Message-ID: <20071213155946.0e0c39a0@weaponx> (raw)
In-Reply-To: <1197581846.15741.183.camel@pasglop>
On Fri, 14 Dec 2007 08:37:26 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Thu, 2007-12-13 at 15:11 -0600, Josh Boyer wrote:
> > Well, there is physical PCI hardware on the boards, yes. But what if
> > people have no intention of using it? E.g. they have no devices, etc.
> > Now we're requiring PCI support to be built into the kernel.
> >
> > I'm just being pedantic about keeping embedded tiny.
>
> Keeping your embedded design tiny (and thus your own BSP) is one thing,
> but adding ifdef's all over the place so that somebody can tinify an
> eval board, I'm less sure about this... but if you want, you can fixup
> my patches.
I'm not really advocating for ifdefs. If it annoys me enough (which I
doubt it will), then I'd try to come up with some way to avoid those
too. For now, I think selecting PCI in Kconfig for those boards is OK.
josh
next prev parent reply other threads:[~2007-12-13 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 7:38 [PATCH 19/20] [POWERPC] pci32: 4xx embedded platforms want to reassign all PCI resources Benjamin Herrenschmidt
2007-12-13 9:42 ` Stefan Roese
2007-12-13 9:56 ` Stefan Roese
2007-12-13 11:12 ` Benjamin Herrenschmidt
2007-12-13 19:01 ` Josh Boyer
2007-12-13 20:37 ` Benjamin Herrenschmidt
2007-12-13 20:40 ` Josh Boyer
2007-12-13 20:52 ` Benjamin Herrenschmidt
2007-12-13 21:11 ` Josh Boyer
2007-12-13 21:37 ` Benjamin Herrenschmidt
2007-12-13 21:59 ` Josh Boyer [this message]
2007-12-14 5:48 ` Stefan Roese
2007-12-13 19:05 ` Josh Boyer
2007-12-13 20:37 ` Benjamin Herrenschmidt
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=20071213155946.0e0c39a0@weaponx \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 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.