linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir A. Gurevich" <vag@paulidav.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Microcode patches for mpc8xx
Date: Mon, 23 May 2005 06:46:23 -0700	[thread overview]
Message-ID: <4291DEAF.1080705@paulidav.org> (raw)
In-Reply-To: <20050523082816.774E4C1512@atlas.denx.de>

Dear Wolfgang,

Wolfgang Denk wrote:

>>since we are on this topic here: look like SMC relocation is explicitly not supported and I can't see the SPI driver as well (unless it reuses 8260 driver). 
>>    
>>
>In our CVS tree? See the old linux-2.4 tree. We don't see  many  uses of 8xx systems recently with ucode requirements.
>  
>
I am completely puzzled now.  It looks like your stable, but old 
linux-2.4 tree has a much better selection of 8xx drivers compared to 
the linuxppc_2_4_devel. Why is that? What do you recommend for a new 
MPC852T-based development? Can the drivers be dropped into the newer 
tree or more serious backporting effort is needed?

Thanks,
Vladimir

       reply	other threads:[~2005-05-23 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050523082816.774E4C1512@atlas.denx.de>
2005-05-23 13:46 ` Vladimir A. Gurevich [this message]
2005-05-23 20:30   ` Microcode patches for mpc8xx Wolfgang Denk

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=4291DEAF.1080705@paulidav.org \
    --to=vag@paulidav.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wd@denx.de \
    /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).