LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Joakim Tjernlund <joakim.tjernlund@lumentis.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel, rc1 and rc2 problem.
Date: Wed, 20 Nov 2002 08:23:02 -0700	[thread overview]
Message-ID: <20021120152302.GI779@opus.bloom.county> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLKECJFIAA.joakim.tjernlund@lumentis.se>


On Wed, Nov 20, 2002 at 12:55:01PM +0100, Joakim Tjernlund wrote:
>

> I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that
> may syslog had problems to start:
>
[snip]

> I then tried rc2(BK curr) and got the same problem. I am running a custom mpc860 board.
>
> Anyone else noticed this?

I haven't tried yet.  Have you tried 'porting' your custom board to
vanilla 2.4.x, which would make it easier to see which, if any of these
upsteram revisions introduced a problem?  The only 8xx-specific changes
in that time have been your i2c changes and a serial fixup.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-11-20 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200211191615.gAJGFVw09351@hofr.at>
2002-11-19 19:01 ` Fast HDLC driver Owen Green
2002-11-20 11:55   ` linuxppc_2_4_devel, rc1 and rc2 problem Joakim Tjernlund
2002-11-20 15:23     ` Tom Rini [this message]
2002-11-20 15:46       ` Joakim Tjernlund
2002-11-20 16:01         ` Tom Rini
2002-11-20 18:55           ` Joakim Tjernlund
2002-11-20 19:14             ` Tom Rini
2002-11-21 13:30               ` Joakim Tjernlund
2002-11-21 15:27               ` Joakim Tjernlund
2002-11-22  8:28                 ` Joakim Tjernlund
2002-11-22  9:31                   ` David Woodhouse
2002-11-22 10:14                     ` 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=20021120152302.GI779@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-dev@lists.linuxppc.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