linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: fabien <fabien.fb@gmail.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ppcboot and powerpc branch question
Date: Fri, 30 Nov 2007 16:57:01 +0100	[thread overview]
Message-ID: <f8f856500711300757g43afe43era3ae692946421d32@mail.gmail.com> (raw)
In-Reply-To: <475027B9.4060804@anagramm.de>

Thanks for yours advices Scott and Clemens i'll read the docs given
Best regards

2007/11/30, Clemens Koller <clemens.koller@anagramm.de>:
> fabien schrieb:
> > hi all,
> >
> > After some problem with my custom board and kernel 2.6.19 about the
> > init process, i've moved
> > on 2.6.23 and that had fixed my problems. (related to this post :
> > http://marc.info/?l=3Dlinuxppc-embedded&m=3D119609022221017&w=3D2)
> > Apparently it was a problem with cpm_uart on SMC1.
> > (http://lkml.org/lkml/2007/9/23/99)
> > the patch have been integrated in 2.6.23. Now i use this kernel and
> > busybox works.
> > I want to migrated my board in powerpc branch instead of ppc (i plan
> > to use xenomai but in 2.6.23
> > there is only an adeos patch for piowerpc branch), but i see the use
> > of a device tree
> > instead of bd_t struct. I'm a bit disappointed because i also see that
> > older u-boot (in my case
> > ppcboot 1.1.5) aren't capable to pass dts to kernel.
> > Is there a way to keep my old bootloader to boot a powerpc branch kerne=
l ?
>
> please read linux/Documentation/powerpc/booting-without-of.txt
>
> To get a cuImage, you
> - need to adjust your <platform>.dts and configure your kernel to use it.
> - need the latest dtc (device tree compiler),
> - need the latest mkimage (from the latest u-boot tree)
> - and build your cuImage by building the target zImage (make zImage)
> -> your cuImage then rests in i.e. arch/powerpc/boot/cuImage.<platform>
>
> Aside of no good documentation, I ran into the problem that the
> embedded device tree doesn't get updated by the bd_t struct properly
> (the mac addresses) in the latest versions of the kernel. This might be
> a bug or a configuration error on my side. I didn't check yet.
> U-Boot with full device tree support will hopfully fix that, when it's
> out.
>
> Regards,
>
> --
> Clemens Koller
> __________________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Stra=DFe 45/1
> Linhof Werksgel=E4nde
> D-81379 M=FCnchen
> Tel.089-741518-50
> Fax 089-741518-19
> http://www.anagramm-technology.com
>
>

  reply	other threads:[~2007-11-30 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 13:33 ppcboot and powerpc branch question fabien
2007-11-30 13:43 ` Grant Likely
2007-11-30 14:45   ` fabien
2007-11-30 15:04     ` Scott Wood
2007-11-30 15:09 ` Clemens Koller
2007-11-30 15:57   ` fabien [this message]
2007-11-30 22:15 ` Wolfgang Denk
2007-11-30 22:25   ` Pagnotta, Chris
2007-11-30 23:10     ` Cannot login via tinylogin on sequoia Leonid
2007-12-03 20:25       ` Leonid
2007-12-01 22:54     ` ppcboot and powerpc branch question 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=f8f856500711300757g43afe43era3ae692946421d32@mail.gmail.com \
    --to=fabien.fb@gmail.com \
    --cc=clemens.koller@anagramm.de \
    --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).