Prev: [BUG] 2.6.26-rc1 lost half the RAM on UltraSPARC 5
Next: avoid kobject name conflict with different namespaces
From: Michal Simek on 7 May 2008 14:40
Hi Steve,

you are right. Microblaze don't need CONFIG_PPC_something but
I keep this in files because it will be easier to move this to better place.
I wanted to sort what Microblaze don't use.

I need to talk with people from sparc and powerpc what we can move and where.
I see the best way to push these files to microblaze/kernel/ and then sychronize
them with one patch - all archs together.

M

>> +#ifdef CONFIG_PPC_PSERIES
>> +#include <asm/rtas.h>
>> +#include <asm/kdump.h>
>> +#include <asm/smp.h>
>> +#include <asm/iommu.h>
>> +#include <asm/btext.h>
>> +#include <asm/machdep.h>
>> +#include <asm/pSeries_reconfig.h>
>> +#include <asm/phyp_dump.h>
>> +#include <asm/kexec.h>
>> +#endif
>
> I don't think we need CONFIG_PPC_PSERIES (multiple times)
>
>> +#ifdef CONFIG_PPC64
>> +int __initdata iommu_is_off;
>> +int __initdata iommu_force_on;
>> +unsigned long tce_alloc_start, tce_alloc_end;
>> +#endif
>
> or PPC64 (multiple times
>
>> +#ifdef CONFIG_PPC32
>
> or PPC32
>
> Steve
>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux(a)itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Michal Simek on 7 May 2008 15:20
Hi Grant,

you understand I use of_device, of_platform and prom_parse. If you do diff
between them they will almost the same. One small difference is in prom.c file.

I hope we will move these files to drivers/of.
This is not only question to me.

Paul, Steve and David: Can I moved these three files to drivers/of?

Michal

>> Hi Steve,
>>
>> you are right. Microblaze don't need CONFIG_PPC_something but
>> I keep this in files because it will be easier to move this to better place.
>> I wanted to sort what Microblaze don't use.
>>
>> I need to talk with people from sparc and powerpc what we can move and where.
>> I see the best way to push these files to microblaze/kernel/ and then sychronize
>> them with one patch - all archs together.
>
> I would disagree. I think its better to push (and get merged) patches
> to move the files first; then add microblaze on top of that. You can
> start getting stuff merged piecemeal that way instead of relying on
> getting your entire patch series merged at once.
>
> However, that's just my opinion, others may look at it differently.
>
> Cheers,
> g.
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [BUG] 2.6.26-rc1 lost half the RAM on UltraSPARC 5
Next: avoid kobject name conflict with different namespaces