linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 5/10 v2] Add 8641 CPU and i8259 Setup
Date: Fri, 09 Jun 2006 11:05:30 -0500	[thread overview]
Message-ID: <E1FojUI-0004N5-E7@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 09 Jun 2006 14:23:09 +1000." <1149826989.12687.50.camel@localhost.localdomain>

So, like, the other day Benjamin Herrenschmidt mumbled:
> 
> [A bunch of SMP issues.]
> 
> The above is wrong, it prevents using the same kernel image on another
> platform.

> Same comment above... #ifdef is bad. You are entering from 0x100 with
> address translation not disabled ?

> > +	bl	clear_bats
> >  	bl	load_up_mmu
> 
> Why do you need to call clear_bats here ? load_up_mmu should load BATs.
> If it doesn't handle the high BATs, then fix it :) 

> > +#ifdef CONFIG_I8259_LEVEL_TRIGGER
> > +	outb(0xfa, 0x4d0); /* level triggered */
> > +	outb(0xde, 0x4d1);
> > +#endif
> 
> Another change that breaks multiplatform... Can you explain precisely
> what you are trying to acheive here ? If necessary, we can add an
> argument to i8259_init. Or you could do the above in your platform
> code ... though I agree it would be a bit ugly :) 

OK.  I don't have direct answers in hand for some of
these questions and issues.  I'll get with original
authors and see what we can do clean this up!

Thanks!

jdl

  reply	other threads:[~2006-06-09 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 21:59 [PATCH 5/10 v2] Add 8641 CPU and i8259 Setup Jon Loeliger
2006-06-09  4:23 ` Benjamin Herrenschmidt
2006-06-09 16:05   ` Jon Loeliger [this message]
2006-06-09 17:16     ` Xianghua Xiao
2006-06-14 15:54     ` Jon Loeliger

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=E1FojUI-0004N5-E7@jdl.com \
    --to=jdl@jdl.com \
    --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).