From: M. R. B. <mr...@0x...> - 2001-12-15 20:05:53
|
* Adrian McMenamin <ad...@mc...> on Sat, Dec 15, 2001: >=20 > To be honest I still don't know enough about Linux development to know wh= at=20 > "unaligned access" is other than it sounds like a linker fix up problem. = Is=20 > this the sort of problem that I should expect because of bugs in the tool= =20 > chain, or it is because of some error I may have made? >=20 The SH4 expects all 16-bit accesses on 16-bit boundaries, and all 32-bit accesses on 32-bit boundaries. Check and make sure your driver is accessing RAM, registers, whatever like it's supposed to. Not a linker issues, and it's a possibility that it's a toolchain bug - given the quality of GCC's SH backend, you can't rule that out. It's also possible that sox does unaligned accesses, so don't rule that out either. Start with your driver first. View the assembler output via gcc -s, (kbuild 2.5 is useful in this regard). M. R. |