1 Oct
2009
1 Oct
'09
8:08 p.m.
Hello again,
attached patch adds support for 1900MHz nanoBTS - use one bts_type
GSM_BTS_TYPE_NANOBTS to refer to all variants of nanoBTS, and rely on
the band specified in the config file when bounds-checking the specified
ARFCN.
At last getting the hang of git...
Best regards, Mike H.
2 Oct
2 Oct
3:29 a.m.
On Thursday 01 October 2009 22:08:49 Mike Haben wrote:
Hello again,
attached patch adds support for 1900MHz nanoBTS - use one bts_type
GSM_BTS_TYPE_NANOBTS to refer to all variants of nanoBTS, and rely on
the band specified in the config file when bounds-checking the specified
ARFCN.
Awesome.
6:42 a.m.
On Friday 02 October 2009 05:29:59 Holger Freyther wrote:
On Thursday 01 October 2009 22:08:49 Mike Haben
wrote:
Okay, git am can not apply the patch and says it is corrupted. Is it my ext4
playing tricks on me? could you help me with sending the patch again?
z.
Hello again,
attached patch adds support for 1900MHz nanoBTS - use one bts_type
GSM_BTS_TYPE_NANOBTS to refer to all variants of nanoBTS, and rely on
the band specified in the config file when bounds-checking the specified
ARFCN.
Awesome.
7:28 a.m.
Hi Mike,
thanks for your patch.
On Thu, Oct 01, 2009 at 09:08:49PM +0100, Mike Haben wrote:
attached patch adds support for 1900MHz nanoBTS - use
one bts_type
GSM_BTS_TYPE_NANOBTS to refer to all variants of nanoBTS, and rely
on the band specified in the config file when bounds-checking the
specified ARFCN.
At last getting the hang of git...
Thanks this makes sense, but....
In fact, we could even go beyond that at some point and inquire the band
capabilities from the BTS. I'm quite sure i've once seen something like this
in the ip.access protocol while working with the wireshark dissector for it.
We will definitely have to differentiate the old 1800/1900 (round like the
850/900 models) and the new 1800/1900 models in some way, as the latter support
edge and the former don't.
But I suppose that can also be read through OML from the BTS. The hardware
type is 178U for the non-edge version and 165AU for the EDGE capable version,
at least on all my units.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
7:45 a.m.
But I suppose that can also be read through OML from
the BTS. The hardware
type is 178U for the non-edge version and 165AU for the EDGE capable
version,
at least on all my units.
fyi, mine is model number 139 (it's a round 1800 version, without EDGE, see
internal pictures in the wiki).
It would probably be useful to make a complete list of all known version
numbers on the wiki. That's 3 version already. Anyone has other versions ?
Sylvain
5744
days inactive
5745
days old
5 comments
5 participants
participants (5)
-
246tnt＠gmail.com -
Harald Welte -
Holger Freyther -
Mike Haben -
Nordin