Uh, nm, sorry for the noise, it was my code that used the same message
and transfer struct. (Maybe if I posted before I'd find it sooner? ;-) )
Domen
On 16/12/08 10:42 +0100, Domen Puncer wrote:
> Hello!
>
> At least I think this is the reason.
>
> I'm doing
Hello!
At least I think this is the reason.
I'm doing spi_async transfers, and in the middle, I get an interrupt
which triggers another spi_async (presumably in the middle of spi
callback) , to read status register.
The resulting backtrace is:
[42949455.73] [ cut here ]-
Hello!
I'm writing a driver for a 2 Mbit/s wireless chip interfaced via SPI.
Now, transmit isn't a problem, I can push data out at full speed
(interrupt handler just signals with a semaphore that there's a free TX
buffer, then in process context I write the next one).
I'm having trouble with rece
Message size needs to be checked before copying, or bad
things could happen.
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
---
drivers/spi/spidev.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Index: work-powerpc.git/drivers/spi/sp
