On Mon, Dec 22, 2014 at 7:47 PM, Doug Anderson wrote:
> I was seeing cases where I was losing interrupts when inserting and
> removing SD cards. Sometimes the card would get "stuck" in the
> inserted state.
>
> I believe that the problem was related to the code to handle the case
> where we
On Mon, Dec 22, 2014 at 7:47 PM, Doug Anderson diand...@chromium.org wrote:
I was seeing cases where I was losing interrupts when inserting and
removing SD cards. Sometimes the card would get stuck in the
inserted state.
I believe that the problem was related to the code to handle the case
Am Montag, 22. Dezember 2014, 10:47:29 schrieb Doug Anderson:
> I was seeing cases where I was losing interrupts when inserting and
> removing SD cards. Sometimes the card would get "stuck" in the
> inserted state.
>
> I believe that the problem was related to the code to handle the case
> where
Am Montag, 22. Dezember 2014, 10:47:29 schrieb Doug Anderson:
I was seeing cases where I was losing interrupts when inserting and
removing SD cards. Sometimes the card would get stuck in the
inserted state.
I believe that the problem was related to the code to handle the case
where we
I was seeing cases where I was losing interrupts when inserting and
removing SD cards. Sometimes the card would get "stuck" in the
inserted state.
I believe that the problem was related to the code to handle the case
where we needed both rising and falling edges. This code would
disable the
I was seeing cases where I was losing interrupts when inserting and
removing SD cards. Sometimes the card would get stuck in the
inserted state.
I believe that the problem was related to the code to handle the case
where we needed both rising and falling edges. This code would
disable the
6 matches
Mail list logo