From: Marc Leeman <marc.leeman@barco•com>
To: "Cordes, Aaron M" <aaron.m.cordes@lmco•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: Linux 2.4.27-pre6-bk hangs on MPC8540 board
Date: Thu, 12 Aug 2004 15:09:14 +0200 [thread overview]
Message-ID: <20040812130914.GR4594@smtp.barco.com> (raw)
In-Reply-To: <EE7CAF713952AC4A970DD7CD8B4C12A042DCA7@emss09m06.us.lmco.com>
> seen similar behavior, or have any suggestions of things I might try?
no, only that 2.4.26 is running rock solid on an MPC8245 based board.
-marc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-12 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 12:47 Linux 2.4.27-pre6-bk hangs on MPC8540 board Cordes, Aaron M
2004-08-12 13:09 ` Marc Leeman [this message]
2004-08-12 14:07 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 19:34 Cordes, Aaron M
2004-08-12 19:38 Cordes, Aaron M
2004-08-12 22:11 ` Kumar Gala
2004-08-12 22:18 ` Conor McLoughlin
2004-08-12 22:07 Cordes, Aaron M
2004-08-13 14:30 ` Kumar Gala
2004-08-14 14:40 ` Chris Zimman
2004-08-12 22:14 Swarthout Edward L-SWARTHOU
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=20040812130914.GR4594@smtp.barco.com \
--to=marc.leeman@barco$(echo .)com \
--cc=aaron.m.cordes@lmco$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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