All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xianghua Xiao <x.xiao@freescale.com>
To: Sam Song <samlinuxppc@yahoo.com.cn>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8641(D) software status
Date: Thu, 11 May 2006 09:08:01 -0500	[thread overview]
Message-ID: <44634541.3040109@freescale.com> (raw)
In-Reply-To: <20060511135328.25523.qmail@web15706.mail.cnb.yahoo.com>

Sam,

We have patches for 8641D against 2.6.15/2.6.16 and it works well in lab
in the last three months along with u-boot code. I think a patch against
2.6.17 or later will be released in the future. However if you need the
2.6.15/2.6.16 patch now, you can contact Freescale directly. In fact,
for all 8641D boards we will ship, we will include the kernel/u-boot
source code on the SATA hard drive directly as well, or you can also
download them from freescale's website.

Hope this helps,
Xianghua


Sam Song wrote:

>Dear all,
>
>Could anyone kindly disclose any info on
>its boot code and kernel support?
>
>Mass production is under way if I am not 
>wrong but less info on software. Just out of
>interest to know that... Maybe I could have 
>the luck to touch it.
>
>Thanks in advance,
>
>Sam
>
>
>	
>
>	
>		
>___________________________________________________________ 
>雅虎免费邮箱-3.5G容量，20M附件
>http://cn.mail.yahoo.com/
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

  reply	other threads:[~2006-05-11 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 13:53 MPC8641(D) software status Sam Song
2006-05-11 14:08 ` Xianghua Xiao [this message]
2006-05-11 19:02   ` Wolfgang Denk
2006-05-11 19:24     ` Xianghua Xiao
2006-05-11 19:55       ` Wolfgang Denk
2006-05-12  1:31       ` Sam Song

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=44634541.3040109@freescale.com \
    --to=x.xiao@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /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.