linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull upstream branch of linux-2.6-PQ.git...
Date: Wed, 4 Oct 2006 02:24:05 +0400	[thread overview]
Message-ID: <20061004022405.45e26c26@localhost.localdomain> (raw)
In-Reply-To: <4522BC0F.7060001@smiths-aerospace.com>

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

On Tue, 03 Oct 2006 15:37:51 -0400
Jerry Van Baren wrote:

> Vitaly Bordug wrote:
> > Paul,
> > 
> > Please do a pull from
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/vitb/linux-2.6-PQ.git,
> > upstream branch.
> > 
> > Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com>
> > 
> > 
> > To receive the updated 8272 addition to the  arch/powerpc.
> > All the comments have been addressed, and it has a minor bugfix
> > addressed too in order to make both pq2 and pq3 co-exist happily in
> > fsl_soc.c. CPM PIC now has "compatible" property that could be
> > "CPM2" or "CPM1" for PQ/8xx.
> > 
> > I think it should go to rc1, because relevant stuff in ppc/ is more
> > or less broken now, with new irq engine. 
> 
> Hi Vitaly,
> 
> I've been following your -PQ progress with a lot of interest.  I have
> a PQ2FADS board (8272) and your changes should apply to it too.  I
> pulled a copy of your repository last week and had a couple of minor
> build errors.  I made a couple of minor fixes and it built OK but I
> didn't run it - I need a compatible boot loader, which leads into my
> question...
> 
> What are you using for booting your 8272ADS board?  I have been using 
> u-boot with the "bd" structure but am looking to switch to the
> flattened OF tree.  I made a half-hearted attempt to switch my u-boot
> build to the flattened OF tree but it didn't work and then I got
> distracted by other things instead of debugging it. :-(
> 

Well I use latest u-boot + OF patches submitted to the u-boot list+ couple of minor fixes on top.
I was about to set up git repo for Wolfgang to pull, meanwhile there are a couple of existing
trees you may want to take a look: on http://www.jdl.com and http://opensource.freescale.com .

Both are holding uboot trees with OF additions, but are targeted to specific platforms apparently (and waiting to be
merged too).

I'll keep you posted while get the stuff available.
--

-Vitaly

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-03 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 18:30 Please pull upstream branch of linux-2.6-PQ.git Vitaly Bordug
2006-10-03 18:43 ` Kumar Gala
2006-10-03 19:05   ` Vitaly Bordug
2006-10-03 19:14     ` Kumar Gala
2006-10-03 19:37 ` Jerry Van Baren
2006-10-03 22:24   ` Vitaly Bordug [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-22  2:37 Vitaly Bordug
2006-09-22 17:24 ` Jon Loeliger

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=20061004022405.45e26c26@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=gerald.vanbaren@smiths-aerospace.com \
    --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 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).