linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/4] Add support for 750CL Holly board
Date: Tue, 08 May 2007 19:39:09 -0500	[thread overview]
Message-ID: <1178671149.3453.49.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <1178666385.14928.119.camel@localhost.localdomain>

On Wed, 2007-05-09 at 09:19 +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2007-05-04 at 21:44 +0200, Arnd Bergmann wrote:
> 
> > > +void holly_show_cpuinfo(struct seq_file *m)
> > > +{
> > > +	seq_printf(m, "vendor\t\t: IBM\n");
> > > +	seq_printf(m, "machine\t\t: PPC750 GX/CL\n");
> > > +}
> > 
> > If it's an IBM product, it should come with a product code like 123-4567,
> > which fits in here, instead of just listing the CPU.
> 
> Should probably come from the device tree anyway.

It will with some cleanup patches I'm planning on.

> > > +	const struct exception_table_entry *entry;
> > > +
> > > +	/* Are we prepared to handle this fault */
> > > +	if ((entry = search_exception_tables(regs->nip)) != NULL) {
> > > +		tsi108_clear_pci_cfg_error();
> > > +		regs->msr |= MSR_RI;
> > > +		regs->nip = entry->fixup;
> > > +		return 1;
> > > +	}
> > > +	return 0;
> > > +}
> > 
> > Are you sure that you can use the generic exception table mechanism
> > like this? I can't see why it doesn't work, but it's something I haven't
> > seen anyone do like this.
> 
> Also, can't the TSI be configured to not generate MCE in that case ?

Not that I'm aware of.  They should only occur on the initial PCI bus
scan.

josh

  reply	other threads:[~2007-05-09  0:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 18:13 [PATCH 0/4] Add support for 750CL Holly board Josh Boyer
2007-05-04 18:14 ` [PATCH 1/4] " Josh Boyer
2007-05-04 18:35   ` Kumar Gala
2007-05-04 19:11     ` Josh Boyer
2007-05-04 19:01   ` Olof Johansson
2007-05-04 19:18     ` Josh Boyer
2007-05-08 23:17       ` Benjamin Herrenschmidt
2007-05-04 19:44   ` Arnd Bergmann
2007-05-04 20:01     ` Josh Boyer
2007-05-05 11:08       ` Arnd Bergmann
2007-05-05 11:44         ` Josh Boyer
2007-05-05 14:41         ` Olof Johansson
2007-05-08 23:24         ` Benjamin Herrenschmidt
2007-05-08 23:20       ` Benjamin Herrenschmidt
2007-05-09  0:32         ` Josh Boyer
2007-05-05 14:39     ` Olof Johansson
2007-05-05 15:11       ` Josh Boyer
2007-05-06  0:09         ` Arnd Bergmann
2007-05-08 23:19     ` Benjamin Herrenschmidt
2007-05-09  0:39       ` Josh Boyer [this message]
2007-05-04 18:15 ` [PATCH 2/4] Holly defconfig Josh Boyer
2007-05-04 18:16 ` [PATCH 3/4] Holly DTS Josh Boyer
2007-05-04 23:51   ` David Gibson
2007-05-05  3:18     ` Josh Boyer
2007-05-04 18:16 ` [PATCH 4/4] Holly bootwrapper Josh Boyer

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=1178671149.3453.49.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).