Re: [RFC PATCH] sparc32,leon: always include leon code in build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Sam Ravnborg wrote:

> Konrad / Daniel - any inputs on why LEON uses a different ASI?
> As we uses this in head_32.S this is really annoying...

It is not difficult to change the MMU reg ASI from 0x19 to 0x4
(as defined in the SRMMU spec). However, all available LEON2/3/4
chips in production uses 0x19 due to a decision take about 10
years ago. ASI 4 was used for uncached access in the original
MMU-less LEON2, hence the choice to use 0x19. In current LEON3/4
cores, ASI 4 is no longer used, so 0x19 could easily be replaced
with 4. But removing the use of ASI 0x19 in the kernel will make
it incompatible with all present chips. I will change the LEON3/4
IP's to double map the MMU ASI to both 4 and 0x19, but then we have
to wait an other 10 years until the present chips are out of use
before we can remove 0x19 from the kernel ...

Jiri.


> 
> 	Sam
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux