Historically filesystem designers knew what legal values of the
various parameters were and they simply looked for legal values. If
they found any illegal values, they reset them to a legal value.
In many cases, that missed bit-rot situations they wanted to find, so
with many modern filesystems,
On Wed, May 29, 2013 at 09:02:22AM +0800, lx wrote:
> hi all:
> They are some asm codes in the kernel like:
>
> #define set_bit(nr,addr) ({\
> register int res __asm__("ax"); \
> __asm__ __volatile__("btsl %2,%3\n\tsetb %%al": \
> "=a" (res):"0" (0),"r" (nr),"m" (*(addr))); \
> res;})
>
>
>
Hi,
I was implementing a file system and ran into the following problem.
I wanted to replicate the super block data in order to recover from
occasional Hard disk failures (bit rot problem etc.). While replicating was
easy i could not find a way to detect the errors in the first place.
Any ideas a
On Fri, May 24, 2013 at 02:58:24PM -0400, Brian Magnuson wrote:
> Hi,
>
> I'm attempting to export three regions of memory out to userspace via
> mmap and I've run into a total block. Of the three regions two are
> reserved areas of DRAM and the last is in IO space and represents
> configuration
Hi Jean,
Le 24/05/2013 14:20, Jean Delvare a écrit :
> On Fri, 24 May 2013 11:52:54 +0200, Mylene Josserand wrote:
>> - an audio codec tlv320aic3204 : There is a driver for this device but
>> for some reasons, we did not use it. Did not find a "SMBus compliant" in
>> its datasheet.
>
> The tlv320a
