public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can U-boot Autodetect arch/ppcversusarch/powerpc from info in the uImage?
Date: Fri, 7 Dec 2007 07:55:56 +0100	[thread overview]
Message-ID: <00b401c8389e$37636c30$02ac10ac@Jocke> (raw)
In-Reply-To: <20071207005741.91EAA2430C@gemini.denx.de>

> -----Original Message-----
> From: wd at denx.de [mailto:wd at denx.de] 
> Sent: den 7 december 2007 01:58
> To: Joakim Tjernlund
> Cc: u-boot-users at lists.sourceforge.net; 'Darcy Watkins'
> Subject: Re: [U-Boot-Users] Can U-boot Autodetect 
> arch/ppcversusarch/powerpc from info in the uImage?
> 
> In message <00aa01c83859$77863cb0$02ac10ac@Jocke> you wrote:
> >
> > The extension I made can just as easily be a function that 
> returns a dev. tree.
> > 
> > - One can have a dev. tree update procedure similar to
> >   rendundant env. The funktion then selects which dev. tree 
> is valid and passes
> >   that back.
> > 
> > - The function can construct a dev. tree from builtin rules/code.
> > 
> > - One can even make it tftp a tree at boot and pass that back. Great
> >   in a development env. especially if you are debugging the 
> dev. tree.
> > 
> > and the kicker is that you can still override this tree at 
> runtime by passing
> > a dev. tree argument to bootm.
> > 
> > All this will be possible by the simple patch I posted 
> earlier, included
> > below.
> 
> Um... and which of these cannot be done without your patch?

The kicker part, override the tree at runtime. It is
also a bit easier do the above my way than messing with
a env variable.

 Jocke

  reply	other threads:[~2007-12-07  6:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 18:49 [U-Boot-Users] Can U-boot Autodetect arch/ppc versus arch/powerpc from info in the uImage? Darcy Watkins
2007-12-03 21:36 ` Wolfgang Denk
2007-12-03 23:33   ` [U-Boot-Users] Can U-boot Autodetect arch/ppc versusarch/powerpc " Joakim Tjernlund
2007-12-04  0:23     ` Wolfgang Denk
2007-12-04  1:06       ` Joakim Tjernlund
2007-12-06 22:43         ` [U-Boot-Users] Can U-boot Autodetect arch/ppcversusarch/powerpc " Joakim Tjernlund
2007-12-07  0:57           ` Wolfgang Denk
2007-12-07  6:55             ` Joakim Tjernlund [this message]
2007-12-07 11:11               ` Wolfgang Denk
2007-12-07 13:14           ` Jerry Van Baren
2007-12-09 13:12             ` Joakim Tjernlund
2007-12-09 15:00               ` Wolfgang Denk
2007-12-09 17:32                 ` Joakim Tjernlund
2007-12-09 19:28                   ` Wolfgang Denk
2007-12-09 21:14                     ` Joakim Tjernlund
2007-12-09 21:36                       ` Wolfgang Denk
2007-12-09 21:59                         ` Joakim Tjernlund
2007-12-09 22:47                           ` [U-Boot-Users] Can U-boot Autodetect arch/ppcversusarch/powerpcfrom " Joakim Tjernlund
2007-12-13 18:49                 ` [U-Boot-Users] Can U-boot Autodetect arch/ppcversusarch/powerpc from " Jerry Van Baren
2007-12-13 23:03                   ` Joakim Tjernlund
2007-12-14 15:53                     ` Joakim Tjernlund
2007-12-16 20:14                       ` Wolfgang Denk
2007-12-16 21:27                         ` Joakim Tjernlund
2007-12-17 14:42                           ` Joakim Tjernlund

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='00b401c8389e$37636c30$02ac10ac@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=u-boot@lists.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