From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "David A. Gatwood" <dgatwood@apple.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem serial.c on module
Date: Fri, 28 Sep 2001 20:53:30 +0200 [thread overview]
Message-ID: <20010928205330.A28288@suse.de> (raw)
In-Reply-To: <20010928113414.C30416@cpe-24-221-152-185.az.sprintbbd.net>
On Fri, Sep 28, Tom Rini wrote:
> On Fri, Sep 28, 2001 at 11:26:20AM -0700, David A. Gatwood wrote:
> > On Friday, September 28, 2001, at 11:05 AM, Tom Rini wrote:
> >
> > >On Fri, Sep 28, 2001 at 10:41:23AM -0700, David A. Gatwood wrote:
> > >>On Friday, September 28, 2001, at 08:15 AM, Tom Rini wrote:
> > >>
> > >>>On Fri, Sep 28, 2001 at 02:33:01PM +0900, KOBAYASHI R. Taizo wrote:
> > >>>
> > >>>>I examined this problem and had a question.
> > >>>>Dose it need following branch?
> > >>>>================L5375==
> > >>>>#ifdef CONFIG_ALL_PPC
> > >>>> /* early PowerMacs would machine check */
> > >>>> if (_machine == _MACH_Pmac) {
> > >>>> printk(KERN_INFO "serial.c: nothing to do on
> > >>>>PowerMacs.\n");
> > >>>> return 0;
> > >>>> }
> > >>>>#endif
> > >>>>=======================
> > >>>
> > >>>Some older machines apparently do. The current 'workaround' in 2_4 is
> > >>>#if defined(CONFIG_ALL_PPC) && !defined(MODULE).
> > >>
> > >>That's disgusting. This should be doing the Linux equivalent of setjmp
> > >>and trapping the machine check and returning 0. Hardware probes
> > >>shouldn't need hacks like this. Just my $0.02.
> > >
> > >Thats what should be happening. But apparently it still doesn't on a
> > >few
> > >older machines. Or it didn't the last time I got an answer out of
> > >Olaf@SuSE.
> >
> > Sounds like a lowmem_vectors problem or similar. What machine and
> > processor?
>
> I think it was a 7x00 with a 601. But I'm not sure. Olaf? Is this a problem
> still even?
I will try it again, later.
That hunk wasnt supposed to go into Bens tree.
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-28 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 5:33 Problem serial.c on module KOBAYASHI R. Taizo
2001-09-28 15:15 ` Tom Rini
2001-09-28 17:41 ` David A. Gatwood
2001-09-28 18:05 ` Tom Rini
2001-09-28 18:26 ` David A. Gatwood
2001-09-28 18:34 ` Tom Rini
2001-09-28 18:53 ` Olaf Hering [this message]
2001-09-29 11:50 ` Benjamin Herrenschmidt
2001-10-01 0:12 ` Paul Mackerras
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=20010928205330.A28288@suse.de \
--to=olh@suse.de \
--cc=dgatwood@apple.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).