All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch]resubmit PPC440EPx: Make Sequoia boot vxWorks
Date: Thu, 10 Jan 2008 19:09:05 +0100	[thread overview]
Message-ID: <200801101909.06113.sr@denx.de> (raw)
In-Reply-To: <200801101850.33131.niklausgiger@gmx.ch>

On Thursday 10 January 2008, Niklaus Giger wrote:
> Signed-off-by: Niklaus Giger <niklaus.giger@netstal.com>
> ---
> vxWorks expects in
> TLB 0 a entry for the Machine Check interrupt
> TLB 1 a entry for the RAM
> TLB 2 a entry for the EBC
> TLB 3 a entry for the boot flash
>
> After changing the baudrate to 9600 I had no problems to boot the
> vxWorks image as distributed by WindRiver (Revision 2.0/1 from
> June 18, 2007)

Niklaus, you moved the patch description again below the "---". This way it 
will not be added to the commit text. I changed this manually and commited 
the patch now.

Please add "ppc4xx:" to the beginning of all ppc4xx related patches in the 
email subject. Example:

ppc4xx: Fix dflush() to restore DVLIM register

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-01-10 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 17:50 [U-Boot-Users] [Patch]resubmit PPC440EPx: Make Sequoia boot vxWorks Niklaus Giger
2008-01-10 18:09 ` Stefan Roese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-03 16:48 Niklaus Giger
2007-12-04  7:35 ` Stefan Roese

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=200801101909.06113.sr@denx.de \
    --to=sr@denx.de \
    --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 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.