All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Wei <wei.zhang@freescale.com>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: MPC8548 PCI Express Support
Date: Fri, 29 Dec 2006 10:21:27 +0800	[thread overview]
Message-ID: <45947BA7.7000704@freescale.com> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D90105CF46AB@EMPBEDEX.empirix.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB18030; format=flowed, Size: 1202 bytes --]

Yes, the MPC8548 patch for 2.6.18 is under development, please wait for 
a while.

Morrison, Tom wrote:
> Hi,
>
> I am a newbie to this list. I have tried to search the 
> list's archives to see if this has been discussed 
> for ideas, and I do not see anything related to this.
>
> I am working on a MPC8548 platform, which has a 
> PLX 8532 PCI-Express chip on it. 
>
> I am using a 2.6.18.x linux kernel (x=6 at the moment)
>
> I saw there are patches for linux kernel for 2.6.11.x 
> (via freescale), but I am hoping you guys know of something
> a little 'newer' than that (so I can patch a 2.6.18.6 kernel)
>
> Also,l PLX supplies a linux driver, but it is module driven. 
> I could put the module and associated 'loader' into the InitRD image 
> (and load it up), but it would be 'neater' to have the support
> built-in to the kernel. Would you guys have any suggestions 
> and/or experience with this?
>
> Any/all suggestions and experiences shared are more than welcomed. 
>
> All the best~!
>
> Tom Morrison
> tmorrison@empirix.com 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>   

      reply	other threads:[~2006-12-29  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 20:04 MPC8548 PCI Express Support Morrison, Tom
2006-12-29  2:21 ` Zhang Wei [this message]

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=45947BA7.7000704@freescale.com \
    --to=wei.zhang@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tmorrison@empirix.com \
    /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.