All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Probe Efika platform before CHRP.
Date: Tue, 19 Dec 2006 12:55:36 +0100	[thread overview]
Message-ID: <4587D338.7060906@246tNt.com> (raw)
In-Reply-To: <1166528379.19254.69.camel@localhost.localdomain>

Benjamin Herrenschmidt wrote:
> On Tue, 2006-12-19 at 09:54 +0000, David Woodhouse wrote:
>   
>> The Efika matches chrp_probe() too, so put its own probe first to make
>> sure we get it right in a multiplatform build.
>>     
>
> Hrm... I told them to remove that from their device-tree ... dammit !
>   
Yes, I told them to do some other changes to their device-tree, but no
luck so far.

I think I'll end up with a bunch of device-tree fix in the efika probe
function. (Either
that, or force the user to have a nvramrc for the firmware that makes
the appropriate
changes, but that's kindof an hassle for the user)

That won't solve the problem with chrp though.
I've seen that pseries will also match chrp. And in the pseries probe
function,
the Cell blades are explicitely 'refused'.

Maybe instead of putting 52xx first, it would be "better" to put chrp
and pseries
last as they seem more "generic". So that anything that match before
that has
priority.


    Sylvain


>> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
>>
>> --- linux-2.6.19.ppc/arch/powerpc/platforms/Makefile~	2006-12-17 14:55:49.000000000 +0000
>> +++ linux-2.6.19.ppc/arch/powerpc/platforms/Makefile	2006-12-17 17:16:52.000000000 +0000
>> @@ -5,9 +5,9 @@ ifeq ($(CONFIG_PPC64),y)
>>  obj-$(CONFIG_PPC_PMAC)		+= powermac/
>>  endif
>>  endif
>> +obj-$(CONFIG_PPC_MPC52xx)	+= 52xx/
>>  obj-$(CONFIG_PPC_CHRP)		+= chrp/
>>  obj-$(CONFIG_4xx)		+= 4xx/
>> -obj-$(CONFIG_PPC_MPC52xx)	+= 52xx/
>>  obj-$(CONFIG_PPC_83xx)		+= 83xx/
>>  obj-$(CONFIG_PPC_85xx)		+= 85xx/
>>  obj-$(CONFIG_PPC_86xx)		+= 86xx/
>>
>>     
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>   

  reply	other threads:[~2006-12-19 11:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  6:23 Bug fixes for 2.6.20 Paul Mackerras
2006-12-19  9:54 ` [PATCH] Probe Efika platform before CHRP David Woodhouse
2006-12-19 11:39   ` Benjamin Herrenschmidt
2006-12-19 11:55     ` Sylvain Munaut [this message]
2006-12-19 14:29       ` David Woodhouse
2006-12-19 15:46         ` Grant Likely
2006-12-19 19:58         ` Benjamin Herrenschmidt
2006-12-19 22:33           ` Sylvain Munaut
2007-01-02 21:29           ` David Woodhouse
2007-01-02 21:37             ` Benjamin Herrenschmidt
2007-01-02 22:04               ` David Woodhouse
2007-01-02 23:04                 ` Grant Likely
     [not found]                   ` <45A01416.6080401@genesi-usa.com>
2007-01-06 22:23                     ` Grant Likely
2007-01-06 23:13                       ` David Woodhouse
2007-01-06 23:37                         ` Grant Likely
2007-01-07  2:55                       ` Sylvain Munaut
2007-01-07  9:11                         ` Raquel Velasco and Bill Buck
2007-03-31 13:15                           ` David Woodhouse
2007-03-31 13:18                             ` Raquel Velasco and Bill Buck
2007-03-31 13:21                               ` David Woodhouse
2007-05-09 11:42                               ` Olaf Hering
2007-05-09 11:45                                 ` Raquel Velasco and Bill Buck
2007-01-07 20:09                       ` Matt Sealey
2007-01-07 20:24                         ` Segher Boessenkool
2007-01-07 22:10                           ` Matt Sealey
2007-01-07 22:35                             ` Benjamin Herrenschmidt
2007-01-07 22:35                             ` Sylvain Munaut
2007-01-07 23:04                               ` Segher Boessenkool
2007-01-07 23:07                               ` Matt Sealey
2007-01-07 23:38                                 ` Sylvain Munaut
2007-01-08  0:37                                 ` Benjamin Herrenschmidt
2007-01-07 22:32                           ` Matt Sealey
2007-01-07 22:39                           ` Matt Sealey
2007-01-07 23:27                             ` Segher Boessenkool
2007-01-07 21:16                         ` Benjamin Herrenschmidt
2007-01-08  2:17                         ` David Woodhouse
2007-01-08  9:18                           ` Matt Sealey
2007-01-08 12:52                             ` Sylvain Munaut
2007-01-08 13:16                               ` Sylvain Munaut
2007-01-08 17:25                                 ` Matt Sealey
2007-01-08 15:44                               ` Sylvain Munaut
2007-01-08 17:25                                 ` Matt Sealey
2007-01-08 17:24                               ` Matt Sealey
2007-01-08 17:59                                 ` Sylvain Munaut
2006-12-19 19:02 ` [PATCH] powerpc export rtas_set_slot_reset() Linas Vepstas
2006-12-19 22:08   ` Brian King
2006-12-19 19:06 ` [PATCH] powerpc fixup error message Linas Vepstas
2006-12-19 20:00 ` [PATCH] powerpc initialize pci device channel state Linas Vepstas

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=4587D338.7060906@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.