On Thu, 2012-01-19 at 11:12 -0600, Dan Williams wrote:
> On Tue, 2012-01-17 at 11:26 +0100, Aleksander Morgado wrote:
> > >>> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> > >>> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or
> > >>> POTS)
> > >
On Tue, 2012-01-17 at 11:26 +0100, Aleksander Morgado wrote:
> >>> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> >>> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> >>> bearer. This property would be redundant for 3GPP-only, CDMA-only or
>>> I believe we need a MMBearerType enum in the 0.6 API, so that we can
>>> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
>>> bearer. This property would be redundant for 3GPP-only, CDMA-only or
>>> POTS-only modems, but would be mandatory if we have a mixe
Hi Aleksander,
> > I believe we need a MMBearerType enum in the 0.6 API, so that we can
> > tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> > bearer. This property would be redundant for 3GPP-only, CDMA-only or
> > POTS-only modems, but would be mandatory if
>> I believe we need a MMBearerType enum in the 0.6 API, so that we can
>> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
>> bearer. This property would be redundant for 3GPP-only, CDMA-only or
>> POTS-only modems, but would be mandatory if we have a mixed
>>
> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> bearer. This property would be redundant for 3GPP-only, CDMA-only or
> POTS-only modems, but would be mandatory if we have a mixed
>
On Mon, 2012-01-16 at 16:19 -0600, Dan Williams wrote:
> On Fri, 2012-01-13 at 11:58 +0100, Marcel Holtmann wrote:
> > Hi Aleksander,
> >
> > > >> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> > > >> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> >
On Fri, 2012-01-13 at 12:34 +0100, Aleksander Morgado wrote:
> Hey Marcel,
>
> >
> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> bearer. This property would be redundant for 3GPP-only,
On Fri, 2012-01-13 at 11:58 +0100, Marcel Holtmann wrote:
> Hi Aleksander,
>
> > >> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> > >> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> > >> bearer. This property would be redundant for 3GPP-only, CDMA-
Hey Marcel,
>
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a m
Hi Aleksander,
> >> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> >> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> >> bearer. This property would be redundant for 3GPP-only, CDMA-only or
> >> POTS-only modems, but would be mandatory if we have a m
>> I believe we need a MMBearerType enum in the 0.6 API, so that we can
>> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
>> bearer. This property would be redundant for 3GPP-only, CDMA-only or
>> POTS-only modems, but would be mandatory if we have a mixed
>> 3GPP(LTE)+CDMA
On Wed, 2012-01-11 at 17:29 +0100, Aleksander Morgado wrote:
> Hey,
>
> I believe we need a MMBearerType enum in the 0.6 API, so that we can
> tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
> bearer. This property would be redundant for 3GPP-only, CDMA-only or
> POTS-only mo
Hey,
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer. Th
14 matches
Mail list logo