> >> If you get a request for an odd length you should write an extra word > >> containing the last byte and one other. See how the standard methods > >> handle this. > > > OK. > > I don't think you need to bother doing that with CF. Look at it the other way around is the best thing to do given an odd sized I/O (eg if a CF format ATAPI drive comes along) to crash the machine. > > Perhaps it would be better to fix the problem at the source. > > I don't think there's a problem there. The string versions of the > functions treat memory as a string of bytes. Double checking the docs you are right. How dumb, but dumb or not that is what it is specified to do. > > Probably nothing. I will try to sort it out. > > It's the need for the tasklet that seems doubtful to me... I was wondering but assumed it was some kind of hardware feature where the end of IRQ occurs too early to do some of the cleanup.
