[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: findfree
From: |
Pawel Kot |
Subject: |
Re: findfree |
Date: |
Sun, 22 Feb 2009 09:27:48 +0100 |
Hi,
On Fri, Feb 20, 2009 at 21:58, W. de Hoog <address@hidden> wrote:
> I am trying to add support for my phone (samsung sgh-m150).
>
> The current way findfree is implemented is by walking the list until an
> empty slot is found. My phone does not report an empty slot as being empty
> but the requested index as being invalid (error: 21). Invalid indices
> (outside the 1-500 range) get the same response so it is not clear if the
> phone is full or an empty slot is reached.
>
> What should I do? Hardcode the barrier (500) or fetch it (AT+CPBR=?)?
> Anything else or did I just miss something?
Well, that's the thing I've never had time to implement. Obviously the
right way to go is the fetch the limit - and it should be stored in
the drives dynamic structures (just to fetch it once).
take care,
--
Pawel Kot
- findfree, W. de Hoog, 2009/02/20
- Re: findfree,
Pawel Kot <=