Searched hist:e62cac1f (Results 1 – 6 of 6) sorted by relevance
/openbmc/linux/arch/sparc/include/asm/ |
H A D | openprom.h | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net> e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char(). This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls. Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | oplib_32.h | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net> e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char(). This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls. Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | oplib_64.h | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/arch/sparc/prom/ |
H A D | console_32.c | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net> e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char(). This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls. Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | printf.c | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net> e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char(). This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls. Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | console_64.c | e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char().
This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls.
Signed-off-by: David S. Miller <davem@davemloft.net> e62cac1f Tue Nov 30 16:33:29 CST 2010 David S. Miller <davem@davemloft.net> sparc: Pass buffer pointer all the way down to prom_{get,put}char(). This gets us closer to being able to eliminate the use of dynamic and stack based buffers, so that we can adhere to the "no buffer addresses above 4GB" rule for PROM calls. Signed-off-by: David S. Miller <davem@davemloft.net>
|