linux-kernel - Re: [RFC PATCHv2 4/4] drivers/otp: convert bfin otp to generic OTP

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikzoNDaaz+4MAb7WzQ09+A4=7r=gpdt0ojc3Q2G@mail.gmail.com>
Date:	Thu, 24 Mar 2011 14:52:20 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	Jamie Iles <jamie@...ieiles.com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [RFC PATCHv2 4/4] drivers/otp: convert bfin otp to generic OTP

On Thu, Mar 24, 2011 at 11:21, Jamie Iles wrote:
> +config BFIN_OTP_WRITE_ENABLE
> +       bool "Enable writing support of OTP pages"
> +       depends on BFIN_OTP
> +       default n
> +       help
> +         If you say Y here, you will enable support for writing of the
> +         OTP pages.  This is dangerous by nature as you can only program
> +         the pages once, so only enable this option when you actually
> +         need it so as to not inadvertently clobber data.

if the generic layer is providing write enable access now, is this
still necessary ?  we could have a common OTP Kconfig i think for
"enable OTP write support".
-mike
--
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/