linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Glisse <j.glisse@gmail.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linuxppc64-dev@ozlabs.org
Subject: Re: Classic PPC specific ASM (CONFIG_6XX)
Date: Mon, 10 Jan 2005 20:31:29 +0100	[thread overview]
Message-ID: <4240b91605011011314bb06814@mail.gmail.com> (raw)
In-Reply-To: <20050110191248.GB3391@smtp.west.cox.net>

On Mon, 10 Jan 2005 12:12:48 -0700, Tom Rini <trini@kernel.crashing.org> wr=
ote:
> On Mon, Jan 10, 2005 at 07:59:50PM +0100, Jerome Glisse wrote:
> > > I have a feeling CONFIG_6xx isn't selected for a good reason.  Can yo=
u
> > > try, as a kludge, removing define_bool PPC_PREP from arch/ppc/Kconfig
> > > and seeing if you can build / boot ?  Thanks.
> > >
> > > --
> > > Tom Rini
> > > http://gate.crashing.org/~trini/
> > >
> >
> > Seems that this flags is linked to many things :) I tried removing PPC_=
PREP
> > bool but the kernel fail to compile with again new errors :
> >
>=20
> One last thing before we just do what you suggested originally, can you
> hack it so that PPC_PREP is still set, but on 970 we still set
> CONFIG_6xx?  Thanks again.
>=20
> --
> Tom Rini
> http://gate.crashing.org/~trini/
>=20

This issue must be strongly linked with the Murphy Law.
Got another compile error when y a add CONFIG_6xx=3Dy
to my kernel config.

  LD      .tmp_vmlinux1
ld: arch/ppc/kernel/idle_6xx.o: No such file: Aucun fichier ou
r=E9pertoire de ce type

Unfortunetly i've got to move (some trip for my study) and i won't be
able to have access any g5 or PPC970 with linux on it until i came back
friday or saturday. Anyway i may access my mail until then.

Does this disable_6xx_mmu function do something that we should really
have on PPC970 ? I hadn't get enought time to look at this function and
understand it.

By the way, even if i pretty sure this is not related, my kernel is patched
with one of my patch (i posted it on this mailling list) that add support o=
f U3
agp bridge on G5.

This patch only affect few file and if i remember well, i have tested witho=
ut
it too with no success.

Files affected by my patch pciids.h, uninorth.c(char/driver/agp),=20
uninorth.h(asm-ppc&64). and some change in Kconfig of (char/driver/agp)

One strange things is that no one except me report error on compilation ?
No one use linux with g5, am i alone :) ?

best,
Jerome Glisse

  reply	other threads:[~2005-01-10 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 15:40 Classic PPC specific ASM (CONFIG_6XX) Jerome Glisse
2005-01-09 21:03 ` Paul Mackerras
2005-01-10 14:52   ` Tom Rini
2005-01-10 16:39     ` Christoph Hellwig
2005-01-10 16:44       ` Tom Rini
2005-01-10 18:14     ` Jerome Glisse
2005-01-10 18:29       ` Tom Rini
2005-01-10 18:59         ` Jerome Glisse
2005-01-10 19:12           ` Tom Rini
2005-01-10 19:31             ` Jerome Glisse [this message]
     [not found]               ` <4240b91605011211101ed322a8@mail.gmail.com>
     [not found]                 ` <20050120231442.GE2626@smtp.west.cox.net>
2005-01-21 11:22                   ` Jerome Glisse
2005-01-21 12:36                     ` Geert Uytterhoeven

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=4240b91605011011314bb06814@mail.gmail.com \
    --to=j.glisse@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.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).