Allen Curtis wrote:
+#define _128KB (128*1024U)
+#define _256MB (256*1024*1024U)
+#define is_size_ok(x) (!((x) < _128KB || (x) > _256MB))
I don't believe this is correct for all PowerPC processors that have BATs.
Can you verify this and ensure it works on everything? I know 601s have
different sized BATs, and the caller of this function really needs to know
what they are doing to ensure this works correctly.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
I don't believe this is correct for all PowerPC processors that have BATs.
Can you verify this and ensure it works on everything? I know 601s have
different sized BATs, and the caller of this function really needs to know
what they are doing to ensure this works correctly.
It is correct according to the comments for setbat(), I will double check.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
On Wed, 2002-08-28 at 09:35, Allen Curtis wrote:
quoted
I don't believe this is correct for all PowerPC processors that have BATs.
Can you verify this and ensure it works on everything? I know 601s have
different sized BATs, and the caller of this function really needs to know
what they are doing to ensure this works correctly.
It is correct according to the comments for setbat(), I will double check.
601 BATs only do 128KiB to 8 MiB. In fact setbat special-cases 601 and
limits it to 8MiB. I believe updating the setbat comment would be a good
idea...
-Hollis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/