On 12:47 Tue 05 Apr     , Jamie Iles wrote:

On Tue, Apr 05, 2011 at 01:21:02PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:

quoted

On 11:49 Tue 05 Apr     , Jamie Iles wrote:

quoted

On Tue, Apr 05, 2011 at 12:28:42PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:

quoted

work fine on 9263ek except the IP version detection.

the at91 macb ip version is supposed to be at 0x0601010C but it's not.
At least on 9263 it's 0x0001010C. So we can not detect the arch at runtime
but we can detect that it's a macb.

So could keep the ifdef for 2 archs but use the ip version on arm

OK, well I think my patches are already doing that so should be OK as 
they are.

Russell, are you able to take these through your tree (I think they 
count as consolidation work) or should I ask Stephen for a tree in 
linux-next for a while first?

no please do not us the is_gem but the same way as I did in the ip detection
keep the version register and then check it.

as this ip can be used on other arch we do not want to see thousands 
of is_xxx

But GEM isn't an architecture/machine type, it's a new Cadence Ethernet 
controller that follows on from MACB, not some arch specific tweaks so 
we really only have two options - MACB or GEM.

I agree but you can have this ip in other soc so we need to try to make it
as generic as possible
and socs can have specific tweaks
So use the version register and mask it is better in my mind and more flexible
It's a shame that we can not detect the diff between avr32 and at91 via ip
version.

I hope that ip variation could be detected via version register.
Next time.

Still, if it's important to you then I'll make the change.

If you don't ming please

Best Regards,
J.