On Thu, Oct 6, 2016 at 11:55 AM, Jagan Teki wrote:
> On Thu, Oct 6, 2016 at 9:21 PM, George McCollister
> wrote:
>> On Thu, Oct 6, 2016 at 10:27 AM, Jagan Teki wrote:
>>> On Thu, Oct 6, 2016 at 8:32 PM, George McCollister
>>> wrote:
I'm looking into adding a sub-command to sf to protect st
On Thu, Oct 6, 2016 at 9:21 PM, George McCollister
wrote:
> On Thu, Oct 6, 2016 at 10:27 AM, Jagan Teki wrote:
>> On Thu, Oct 6, 2016 at 8:32 PM, George McCollister
>> wrote:
>>> I'm looking into adding a sub-command to sf to protect status
>>> registers on Winbond SPI flash parts via the status
On Thu, Oct 6, 2016 at 10:27 AM, Jagan Teki wrote:
> On Thu, Oct 6, 2016 at 8:32 PM, George McCollister
> wrote:
>> I'm looking into adding a sub-command to sf to protect status
>> registers on Winbond SPI flash parts via the status register protect
>> bits SRP0, SRP1. I propose the sub-command b
On Thu, Oct 6, 2016 at 8:32 PM, George McCollister
wrote:
> I'm looking into adding a sub-command to sf to protect status
> registers on Winbond SPI flash parts via the status register protect
> bits SRP0, SRP1. I propose the sub-command be named sr-protect.
>
> My use case is simple, I want to ma
I'm looking into adding a sub-command to sf to protect status
registers on Winbond SPI flash parts via the status register protect
bits SRP0, SRP1. I propose the sub-command be named sr-protect.
My use case is simple, I want to make the SPI flash read-only when the
/WP pin is low. To do this I mus
5 matches
Mail list logo