linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Allen Curtis <acurtis@onz.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Ppc Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 2.6.12-rc2] Freescale 8272ADS PCI bridge support to the
Date: Fri, 13 May 2005 14:09:46 -0700	[thread overview]
Message-ID: <541a45636bdf88d9eb3c08febd63d5c5@onz.com> (raw)
In-Reply-To: <757b7fc162262dae582e1d85b6f36e62@freescale.com>

Is the patch necessary? In the March archive it appears that people 
were using the standard 8260 PCI support. What is the issue? Perhaps I 
could provide a patch to m8260_pci.c (as you suggested)

>> Where can I find the kernel tree with this integrated?
>
> One doesn't exist.
>
Is there an embedded 2.5/2.6 tree somewhere? (I know about the 
bkbits.net/ppc/linux-2.5 tree

TIA

  reply	other threads:[~2005-05-13 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 17:09 [PATCH 2.6.12-rc2] Freescale 8272ADS PCI bridge support to the Allen Curtis
2005-05-13 17:43 ` Kumar Gala
2005-05-13 21:09   ` Allen Curtis [this message]
2005-05-16  7:44     ` Vitaly Bordug

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=541a45636bdf88d9eb3c08febd63d5c5@onz.com \
    --to=acurtis@onz.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).