| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1281381548.22777.39.camel@maxim-laptop> Date: Mon, 09 Aug 2010 22:19:08 +0300 From: Maxim Levitsky <maximlevitsky@...il.com> To: Alex Dubov <oakad@...oo.com> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/2] MEMSTICK: Add driver for Ricoh R5C592 Card reader. About INT bits, I still don't understand them exactly. First of all we have 4 meaningful bits. In parallel mode these are exposed on data lines, in serial mode only MEMSTICK_INT_CED is. And I can always send MS_TPC_GET_INT or just read the registers. #define MEMSTICK_INT_CMDNAK 0x01 #define MEMSTICK_INT_BREQ 0x20 #define MEMSTICK_INT_ERR 0x40 #define MEMSTICK_INT_CED 0x80 Now, I send a command to device, say MS_CMD_BLOCK_READ. What bits I need to poll until I can be sure that command is completed? Also the MEMSTICK_INT_BREQ tells that input is available in firmware buffer (to read using TPC_READ_LONG_DATA)? Is that true that MEMSTICK_INT_BREQ is a summary of fifo full/empty bits in status0? And same about MEMSTICK_INT_ERR and status1. I try my best to create a driver that actually works, simple, and error free, even in unusual conditions. Thats why I am asking all these questions. Thanks for help, Best regards, Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists