From wolfram at the-dreams.de  Wed Aug  4 17:09:27 2010
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Wed, 04 Aug 2010 19:09:27 +0200
Subject: Who would attend a developer room / meeting at FrOSCon ?
In-Reply-To: <20100420093229.GS18200@prithivi.gnumonks.org>
References: <20100420093229.GS18200@prithivi.gnumonks.org>
Message-ID: <4C599EC7.2070902@the-dreams.de>


> I've been offered a 'developer room' at FrOSCon 2010 (http://www.froscon.de/)
> which will be at FH Bonn-Rhein-Sieg (http://www.fh-brs.de/) in Sankt Augustin
> from August 21/22 this year.

If I read programm.froscon.org correctly, the developer room didn't 
happen. Still, anyone besides me going there? Should I bring my mobiles 
with me?

Regards,

    Wolfram




From laforge at gnumonks.org  Wed Aug  4 17:58:38 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 4 Aug 2010 19:58:38 +0200
Subject: Who would attend a developer room / meeting at FrOSCon ?
In-Reply-To: <4C599EC7.2070902@the-dreams.de>
References: <20100420093229.GS18200@prithivi.gnumonks.org>
	<4C599EC7.2070902@the-dreams.de>
Message-ID: <20100804175838.GD1460@prithivi.gnumonks.org>

On Wed, Aug 04, 2010 at 07:09:27PM +0200, Wolfram Sang wrote:
> 
> >I've been offered a 'developer room' at FrOSCon 2010 (http://www.froscon.de/)
> >which will be at FH Bonn-Rhein-Sieg (http://www.fh-brs.de/) in Sankt Augustin
> >from August 21/22 this year.
> 
> If I read programm.froscon.org correctly, the developer room didn't
> happen. Still, anyone besides me going there? Should I bring my
> mobiles with me?

No, nobody has ever responded and thus there is no develoepr room.

Whether or not you want to do something with your mobile phones thus
depends entirely on you, sorry.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From bouchtaoui at gmail.com  Mon Aug  2 07:27:09 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Mon, 02 Aug 2010 09:27:09 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <20100730165851.GW13645@prithivi.gnumonks.org>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
Message-ID: <4C56734D.5030808@gmail.com>

Hello list,

What do you think about this, see attachment.
On the left side the MS, on the right side the switch (network side) and 
in the middle is the antenna that interconnects those two worlds.
Also it looks like an umbrella that covers all the projects :)

It's just a sketch, we can add colors to it and make the lines 
symmetrical, stretch the hight (to iconize) better etc.



On 30-7-2010 18:58, Harald Welte wrote:
> Hi!
>
> It's about time that we find some kind of graphical project logo for the
> Osmocom project.
>
> Osmocom is intended as an umbrella project for software like OpenBSC, OsmoSGSN,
> OsmocomBB and others.
>
> So it might even be interesting to have some kind of 'family' of logos that
> all have the same general theme.... At least the bigger projects like OpenBSC
> and OsmocomBB definitely deserve their own incarnation within that family.
>
> If you want to contribute to our project but are not a die-hard C developer,
> this is your option to contribute!
>
> The logo must be under a license that permits use+modification for the
> Osmocom project itself.  Editability for the general public is not important.
>
> With regard to formats, I would prefer something as SVG that we can then
> render into pngs of various sizes whenever there is demand for it.
>
> If you have a proposal, simply send it (or a link to a URL) to the
> openbsc at lists.gnumonks.org mailing list.
>
> Thanks in advance for any submissions!
>
>    

-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_logo.PNG
Type: image/png
Size: 3428 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100802/b8e59008/attachment.png>

From steve at steve-m.de  Mon Aug  2 23:08:21 2010
From: steve at steve-m.de (Steve Markgraf)
Date: Tue, 03 Aug 2010 01:08:21 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
Message-ID: <4C574FE5.6020303@steve-m.de>

Hi,

On 02.08.2010 14:36, Sylvain Munaut wrote:

>   A nice typo with just 'osmocom' and a free space to put the suffix
> ('bb' 'sgsn' ...) either in another typo or just using the bold face
> and then just some _discrete_ graphical element added to the typo ...
>
>   But IMHO certainly not some complex graphical only element.

Ack, that's what I'd suggest as well, something clean and simple.

So here's my RFC:
I've taken the wireless symbol Kevin posted, and added a lettering.

The font used is "Yanone Kaffeesatz" [1], which is licensed under the 
Open Font License.

I attached osmocom_inkscape.svg, for which you need to have the font 
installed, and can then play around and edit the text, and a 
"object-to-path" converted osmocom_paths.svg, which is just a plain 
vector graphic.

If anyone has an idea how to decently make the difference between 
osmocomBB and BSC more clear, or even has a completely different idea, 
let us hear/see them :)

Regards,
Steve

[1] http://www.yanone.de/typedesign/kaffeesatz/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_paths.svg
Type: image/svg+xml
Size: 95149 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/c942d2e8/attachment.svg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_inkscape.svg
Type: image/svg+xml
Size: 60999 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/c942d2e8/attachment-0001.svg>

From sweisman at pobox.com  Mon Aug  2 23:20:05 2010
From: sweisman at pobox.com (Scott Weisman)
Date: Tue, 3 Aug 2010 02:20:05 +0300
Subject: Wanted: Osmocom logo
In-Reply-To: <4C574FE5.6020303@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de>
Message-ID: <AANLkTimKQXg6+YYCKT-m8G8crsEzK_oo5mu_XUSsO-Jv@mail.gmail.com>

Riffing on the GSM bars suggestion, how about bars that go to 11 (:-)?

Scott

On Tue, Aug 3, 2010 at 2:08 AM, Steve Markgraf <steve at steve-m.de> wrote:

> Hi,
>
> On 02.08.2010 14:36, Sylvain Munaut wrote:
>
>   A nice typo with just 'osmocom' and a free space to put the suffix
>> ('bb' 'sgsn' ...) either in another typo or just using the bold face
>> and then just some _discrete_ graphical element added to the typo ...
>>
>>  But IMHO certainly not some complex graphical only element.
>>
>
> Ack, that's what I'd suggest as well, something clean and simple.
>
> So here's my RFC:
> I've taken the wireless symbol Kevin posted, and added a lettering.
>
> The font used is "Yanone Kaffeesatz" [1], which is licensed under the Open
> Font License.
>
> I attached osmocom_inkscape.svg, for which you need to have the font
> installed, and can then play around and edit the text, and a
> "object-to-path" converted osmocom_paths.svg, which is just a plain vector
> graphic.
>
> If anyone has an idea how to decently make the difference between osmocomBB
> and BSC more clear, or even has a completely different idea, let us hear/see
> them :)
>
> Regards,
> Steve
>
> [1] http://www.yanone.de/typedesign/kaffeesatz/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/da0d7a93/attachment.htm>

From peter at stuge.se  Tue Aug  3 01:00:25 2010
From: peter at stuge.se (Peter Stuge)
Date: Tue, 3 Aug 2010 03:00:25 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C574FE5.6020303@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de>
Message-ID: <20100803010025.2192.qmail@stuge.se>

Steve Markgraf wrote:
> So here's my RFC:
> I've taken the wireless symbol Kevin posted, and added a lettering.
>
> The font used is "Yanone Kaffeesatz" [1], which is licensed under the
> Open Font License.

I for one like this suggestion very much.


> If anyone has an idea how to decently make the difference between
> osmocomBB and BSC more clear, or even has a completely different
> idea, let us hear/see them :)

Write BB or BSC using the same bluegrayish tone as the icon. I
strongly prefer lowercase osmocom and uppercase non-inverted BB/BSC.
(ie. the two topmost ones.)


//Peter



From openbsc at mail.tsaitgaist.info  Tue Aug  3 08:36:10 2010
From: openbsc at mail.tsaitgaist.info (Kevin)
Date: Tue, 03 Aug 2010 10:36:10 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C574FE5.6020303@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de>
Message-ID: <4C57D4FA.20107@mail.tsaitgaist.info>

nice font and drawing
the original tower is here :
https://secure.wikimedia.org/wikipedia/commons/wiki/File:Gnome-network-wireless.svg.
(just to know)

I also replaced the "m" of mobile with a reception antenna.
Does not look very good, but it's just a nice idea.

Kevin

On 03.08.2010 01:08, Steve Markgraf wrote:
> Hi,
> 
> On 02.08.2010 14:36, Sylvain Munaut wrote:
> 
>>   A nice typo with just 'osmocom' and a free space to put the suffix
>> ('bb' 'sgsn' ...) either in another typo or just using the bold face
>> and then just some _discrete_ graphical element added to the typo ...
>>
>>   But IMHO certainly not some complex graphical only element.
> 
> Ack, that's what I'd suggest as well, something clean and simple.
> 
> So here's my RFC:
> I've taken the wireless symbol Kevin posted, and added a lettering.
> 
> The font used is "Yanone Kaffeesatz" [1], which is licensed under the
> Open Font License.
> 
> I attached osmocom_inkscape.svg, for which you need to have the font
> installed, and can then play around and edit the text, and a
> "object-to-path" converted osmocom_paths.svg, which is just a plain
> vector graphic.
> 
> If anyone has an idea how to decently make the difference between
> osmocomBB and BSC more clear, or even has a completely different idea,
> let us hear/see them :)
> 
> Regards,
> Steve
> 
> [1] http://www.yanone.de/typedesign/kaffeesatz/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_inkscape.svg
Type: image/svg+xml
Size: 36194 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/7b16c1c8/attachment.svg>

From squalyl at gmail.com  Tue Aug  3 09:07:06 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 3 Aug 2010 11:07:06 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C57D4FA.20107@mail.tsaitgaist.info>
References: <20100730165851.GW13645@prithivi.gnumonks.org> 
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com> 
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
Message-ID: <AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>

I personnaly like the signal indicator in place of the M :-)

On Tue, Aug 3, 2010 at 10:36 AM, Kevin <openbsc at mail.tsaitgaist.info> wrote:

> nice font and drawing
> the original tower is here :
>
> https://secure.wikimedia.org/wikipedia/commons/wiki/File:Gnome-network-wireless.svg
> .
> (just to know)
>
> I also replaced the "m" of mobile with a reception antenna.
> Does not look very good, but it's just a nice idea.
>
> Kevin
>
> On 03.08.2010 01:08, Steve Markgraf wrote:
> > Hi,
> >
> > On 02.08.2010 14:36, Sylvain Munaut wrote:
> >
> >>   A nice typo with just 'osmocom' and a free space to put the suffix
> >> ('bb' 'sgsn' ...) either in another typo or just using the bold face
> >> and then just some _discrete_ graphical element added to the typo ...
> >>
> >>   But IMHO certainly not some complex graphical only element.
> >
> > Ack, that's what I'd suggest as well, something clean and simple.
> >
> > So here's my RFC:
> > I've taken the wireless symbol Kevin posted, and added a lettering.
> >
> > The font used is "Yanone Kaffeesatz" [1], which is licensed under the
> > Open Font License.
> >
> > I attached osmocom_inkscape.svg, for which you need to have the font
> > installed, and can then play around and edit the text, and a
> > "object-to-path" converted osmocom_paths.svg, which is just a plain
> > vector graphic.
> >
> > If anyone has an idea how to decently make the difference between
> > osmocomBB and BSC more clear, or even has a completely different idea,
> > let us hear/see them :)
> >
> > Regards,
> > Steve
> >
> > [1] http://www.yanone.de/typedesign/kaffeesatz/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/ac1ed53c/attachment.htm>

From openbsc at mail.tsaitgaist.info  Wed Aug  4 12:03:13 2010
From: openbsc at mail.tsaitgaist.info (Kevin)
Date: Wed, 04 Aug 2010 14:03:13 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
Message-ID: <4C595701.50708@mail.tsaitgaist.info>

Here some ideas to improve the "m"
Another idea would be to make the "O" like the waves (in term of colors)

On 03.08.2010 11:07, S?bastien Lorquet wrote:
> I personnaly like the signal indicator in place of the M :-)
> 
> On Tue, Aug 3, 2010 at 10:36 AM, Kevin <openbsc at mail.tsaitgaist.info
> <mailto:openbsc at mail.tsaitgaist.info>> wrote:
> 
>     nice font and drawing
>     the original tower is here :
>     https://secure.wikimedia.org/wikipedia/commons/wiki/File:Gnome-network-wireless.svg.
>     (just to know)
> 
>     I also replaced the "m" of mobile with a reception antenna.
>     Does not look very good, but it's just a nice idea.
> 
>     Kevin
> 
>     On 03.08.2010 01:08, Steve Markgraf wrote:
>     > Hi,
>     >
>     > On 02.08.2010 14:36, Sylvain Munaut wrote:
>     >
>     >>   A nice typo with just 'osmocom' and a free space to put the suffix
>     >> ('bb' 'sgsn' ...) either in another typo or just using the bold face
>     >> and then just some _discrete_ graphical element added to the typo ...
>     >>
>     >>   But IMHO certainly not some complex graphical only element.
>     >
>     > Ack, that's what I'd suggest as well, something clean and simple.
>     >
>     > So here's my RFC:
>     > I've taken the wireless symbol Kevin posted, and added a lettering.
>     >
>     > The font used is "Yanone Kaffeesatz" [1], which is licensed under the
>     > Open Font License.
>     >
>     > I attached osmocom_inkscape.svg, for which you need to have the font
>     > installed, and can then play around and edit the text, and a
>     > "object-to-path" converted osmocom_paths.svg, which is just a plain
>     > vector graphic.
>     >
>     > If anyone has an idea how to decently make the difference between
>     > osmocomBB and BSC more clear, or even has a completely different idea,
>     > let us hear/see them :)
>     >
>     > Regards,
>     > Steve
>     >
>     > [1] http://www.yanone.de/typedesign/kaffeesatz/
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_inkscape.svg
Type: image/svg+xml
Size: 80052 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100804/a36bd433/attachment.svg>

From openbsc at mail.tsaitgaist.info  Tue Aug 10 15:37:10 2010
From: openbsc at mail.tsaitgaist.info (Kevin)
Date: Tue, 10 Aug 2010 17:37:10 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C595701.50708@mail.tsaitgaist.info>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
Message-ID: <4C617226.30403@mail.tsaitgaist.info>

some more designs

On 04.08.2010 14:03, Kevin wrote:
> Here some ideas to improve the "m"
> Another idea would be to make the "O" like the waves (in term of colors)
> 
> On 03.08.2010 11:07, S?bastien Lorquet wrote:
>> I personnaly like the signal indicator in place of the M :-)
>>
>> On Tue, Aug 3, 2010 at 10:36 AM, Kevin <openbsc at mail.tsaitgaist.info
>> <mailto:openbsc at mail.tsaitgaist.info>> wrote:
>>
>>     nice font and drawing
>>     the original tower is here :
>>     https://secure.wikimedia.org/wikipedia/commons/wiki/File:Gnome-network-wireless.svg.
>>     (just to know)
>>
>>     I also replaced the "m" of mobile with a reception antenna.
>>     Does not look very good, but it's just a nice idea.
>>
>>     Kevin
>>
>>     On 03.08.2010 01:08, Steve Markgraf wrote:
>>     > Hi,
>>     >
>>     > On 02.08.2010 14:36, Sylvain Munaut wrote:
>>     >
>>     >>   A nice typo with just 'osmocom' and a free space to put the suffix
>>     >> ('bb' 'sgsn' ...) either in another typo or just using the bold face
>>     >> and then just some _discrete_ graphical element added to the typo ...
>>     >>
>>     >>   But IMHO certainly not some complex graphical only element.
>>     >
>>     > Ack, that's what I'd suggest as well, something clean and simple.
>>     >
>>     > So here's my RFC:
>>     > I've taken the wireless symbol Kevin posted, and added a lettering.
>>     >
>>     > The font used is "Yanone Kaffeesatz" [1], which is licensed under the
>>     > Open Font License.
>>     >
>>     > I attached osmocom_inkscape.svg, for which you need to have the font
>>     > installed, and can then play around and edit the text, and a
>>     > "object-to-path" converted osmocom_paths.svg, which is just a plain
>>     > vector graphic.
>>     >
>>     > If anyone has an idea how to decently make the difference between
>>     > osmocomBB and BSC more clear, or even has a completely different idea,
>>     > let us hear/see them :)
>>     >
>>     > Regards,
>>     > Steve
>>     >
>>     > [1] http://www.yanone.de/typedesign/kaffeesatz/
>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_inkscape.svg
Type: image/svg+xml
Size: 75097 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100810/a57ee853/attachment.svg>

From kevin.granade at gmail.com  Tue Aug 10 18:14:50 2010
From: kevin.granade at gmail.com (kevin granade)
Date: Tue, 10 Aug 2010 13:14:50 -0500
Subject: Wanted: Osmocom logo
In-Reply-To: <4C617226.30403@mail.tsaitgaist.info>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
	<4C617226.30403@mail.tsaitgaist.info>
Message-ID: <AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>

On Tue, Aug 10, 2010 at 10:37 AM, Kevin <openbsc at mail.tsaitgaist.info> wrote:
> some more designs

I didn't like that I couldn't clearly see both the "signal bars" and
the 'm', so I applied a few adjustments to the last set of designs.
Specifically I decreased the length of the initial stroke to separate
the first "bar" from the antenna symbol, made the antenna symbol fill
with the background color to hide the corner of the "m" that was
peeking through, and reversed the colors of the background and
foreground strokes.  I think the bars need to be a different color,
but I'm abysmal at choosing colors, so someone else can tweak that if
they think it's an improvement.

Kevin

P.S. This IS a different Kevin.

>
> On 04.08.2010 14:03, Kevin wrote:
>> Here some ideas to improve the "m"
>> Another idea would be to make the "O" like the waves (in term of colors)
>>
>> On 03.08.2010 11:07, S?bastien Lorquet wrote:
>>> I personnaly like the signal indicator in place of the M :-)
>>>
>>> On Tue, Aug 3, 2010 at 10:36 AM, Kevin <openbsc at mail.tsaitgaist.info
>>> <mailto:openbsc at mail.tsaitgaist.info>> wrote:
>>>
>>> ? ? nice font and drawing
>>> ? ? the original tower is here :
>>> ? ? https://secure.wikimedia.org/wikipedia/commons/wiki/File:Gnome-network-wireless.svg.
>>> ? ? (just to know)
>>>
>>> ? ? I also replaced the "m" of mobile with a reception antenna.
>>> ? ? Does not look very good, but it's just a nice idea.
>>>
>>> ? ? Kevin
>>>
>>> ? ? On 03.08.2010 01:08, Steve Markgraf wrote:
>>> ? ? > Hi,
>>> ? ? >
>>> ? ? > On 02.08.2010 14:36, Sylvain Munaut wrote:
>>> ? ? >
>>> ? ? >> ? A nice typo with just 'osmocom' and a free space to put the suffix
>>> ? ? >> ('bb' 'sgsn' ...) either in another typo or just using the bold face
>>> ? ? >> and then just some _discrete_ graphical element added to the typo ...
>>> ? ? >>
>>> ? ? >> ? But IMHO certainly not some complex graphical only element.
>>> ? ? >
>>> ? ? > Ack, that's what I'd suggest as well, something clean and simple.
>>> ? ? >
>>> ? ? > So here's my RFC:
>>> ? ? > I've taken the wireless symbol Kevin posted, and added a lettering.
>>> ? ? >
>>> ? ? > The font used is "Yanone Kaffeesatz" [1], which is licensed under the
>>> ? ? > Open Font License.
>>> ? ? >
>>> ? ? > I attached osmocom_inkscape.svg, for which you need to have the font
>>> ? ? > installed, and can then play around and edit the text, and a
>>> ? ? > "object-to-path" converted osmocom_paths.svg, which is just a plain
>>> ? ? > vector graphic.
>>> ? ? >
>>> ? ? > If anyone has an idea how to decently make the difference between
>>> ? ? > osmocomBB and BSC more clear, or even has a completely different idea,
>>> ? ? > let us hear/see them :)
>>> ? ? >
>>> ? ? > Regards,
>>> ? ? > Steve
>>> ? ? >
>>> ? ? > [1] http://www.yanone.de/typedesign/kaffeesatz/
>>>
>>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_inkscape.svg
Type: image/svg+xml
Size: 75984 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100810/3a8188e4/attachment.svg>

From nibbler at ccc.de  Thu Aug 12 00:55:12 2010
From: nibbler at ccc.de (Michael Horn)
Date: Thu, 12 Aug 2010 02:55:12 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
	<4C617226.30403@mail.tsaitgaist.info>
	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
Message-ID: <20100812025512.15a63386@minime.mobile.nibbler.de>

How about getting rid of the second antenna in the m of osmocom and
leaving the bars in a slightly different shade within the m?
it would aid the readability hugely.
i really like the idea of the bars but with the antenna triangle it
looks too overdone.
btw. what's the font? 

just my 0,02eur

nibbler



From laforge at gnumonks.org  Thu Aug 12 10:54:39 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 12 Aug 2010 18:54:39 +0800
Subject: Wanted: Osmocom logo
In-Reply-To: <20100812025512.15a63386@minime.mobile.nibbler.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
	<4C617226.30403@mail.tsaitgaist.info>
	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
	<20100812025512.15a63386@minime.mobile.nibbler.de>
Message-ID: <20100812105439.GI6510@prithivi.gnumonks.org>

Hi all,

On Thu, Aug 12, 2010 at 02:55:12AM +0200, Michael Horn wrote:

> How about getting rid of the second antenna in the m of osmocom and
> leaving the bars in a slightly different shade within the m?
> it would aid the readability hugely.
> i really like the idea of the bars but with the antenna triangle it
> looks too overdone.

I am also not quite happy with the readability yet.  The connection between
the vertical lines in the 'm' are so light colored that it is hard to
make out that it should actually read as an M, from my point of view.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From roh at hyte.de  Thu Aug 12 13:23:35 2010
From: roh at hyte.de (Joachim Steiger)
Date: Thu, 12 Aug 2010 15:23:35 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <20100812105439.GI6510@prithivi.gnumonks.org>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>	<4C574FE5.6020303@steve-m.de>
	<4C57D4FA.20107@mail.tsaitgaist.info>	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>	<4C595701.50708@mail.tsaitgaist.info>	<4C617226.30403@mail.tsaitgaist.info>	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>	<20100812025512.15a63386@minime.mobile.nibbler.de>
	<20100812105439.GI6510@prithivi.gnumonks.org>
Message-ID: <4C63F5D7.1070206@hyte.de>

Harald Welte wrote:
> Hi all,
> 
> On Thu, Aug 12, 2010 at 02:55:12AM +0200, Michael Horn wrote:
> 
>> How about getting rid of the second antenna in the m of osmocom and
>> leaving the bars in a slightly different shade within the m?
>> it would aid the readability hugely.
>> i really like the idea of the bars but with the antenna triangle it
>> looks too overdone.

ack

> I am also not quite happy with the readability yet.  The connection between
> the vertical lines in the 'm' are so light colored that it is hard to
> make out that it should actually read as an M, from my point of view.

imho the logo should be usable even without any colors
this means grayscale/ steps of gray and even black and white only.

i do not want to design another one when we want to print some on boxes ;)

--

roh



From bouchtaoui at gmail.com  Fri Aug 13 07:54:07 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Fri, 13 Aug 2010 09:54:07 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C63F5D7.1070206@hyte.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>	<4C574FE5.6020303@steve-m.de>	<4C57D4FA.20107@mail.tsaitgaist.info>	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>	<4C595701.50708@mail.tsaitgaist.info>	<4C617226.30403@mail.tsaitgaist.info>	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>	<20100812025512.15a63386@minime.mobile.nibbler.de>	<20100812105439.GI6510@prithivi.gnumonks.org>
	<4C63F5D7.1070206@hyte.de>
Message-ID: <4C64FA1F.3030006@gmail.com>


> i do not want to design another one when we want to print some on boxes ;)
>    

Why not, than we have more to choose.




From laforge at gnumonks.org  Tue Aug  3 09:43:04 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 3 Aug 2010 11:43:04 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C57D4FA.20107@mail.tsaitgaist.info>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
Message-ID: <20100803094304.GJ9698@prithivi.gnumonks.org>

First of all, thanks to everyone who has contributed to this discussion.

On Tue, Aug 03, 2010 at 10:36:10AM +0200, Kevin wrote:
 
> I also replaced the "m" of mobile with a reception antenna.
> Does not look very good, but it's just a nice idea.

yes, the idea is good, but the readability is bad, if you don't already know
the project name and can thus 'interpolate' in your brain.

So my preference would be the first one.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From squalyl at gmail.com  Tue Aug  3 12:05:16 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 3 Aug 2010 14:05:16 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <20100803094304.GJ9698@prithivi.gnumonks.org>
References: <20100730165851.GW13645@prithivi.gnumonks.org> 
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com> 
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info> 
	<20100803094304.GJ9698@prithivi.gnumonks.org>
Message-ID: <AANLkTim5ZMGoYPH1KrnhNvXLndGrzp283Y27J13LOfnC@mail.gmail.com>

A shadowed and aligned "m" as a background to this power indicator letter
might improve readability, don't you think?

I also like the inverted project name.

Regards
Sebastien

On Tue, Aug 3, 2010 at 11:43 AM, Harald Welte <laforge at gnumonks.org> wrote:

> First of all, thanks to everyone who has contributed to this discussion.
>
> On Tue, Aug 03, 2010 at 10:36:10AM +0200, Kevin wrote:
>
> > I also replaced the "m" of mobile with a reception antenna.
> > Does not look very good, but it's just a nice idea.
>
> yes, the idea is good, but the readability is bad, if you don't already
> know
> the project name and can thus 'interpolate' in your brain.
>
> So my preference would be the first one.
>
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                  (ETSI EN 300 175-7 Ch. A6)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100803/6b294407/attachment.htm>

From 246tnt at gmail.com  Tue Aug  3 09:15:22 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 3 Aug 2010 11:15:22 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C574FE5.6020303@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de>
Message-ID: <AANLkTik560Pj-QXR9fz7DmfVAAxG8AnjY-0gEU3fF2uR@mail.gmail.com>

> If anyone has an idea how to decently make the difference between osmocomBB
> and BSC more clear, or even has a completely different idea, let us hear/see
> them :)

Two comments:
 - I like the 'inverted' suffix
 - I'm wondering if that suffix shouldn't be on the next line
   (right aligned). It's to avoid a too elongated aspect ratio that
   can sometime make it hard to use/integrate the logo when a more
   'square' one is expected.
   (doesn't need to be square, just not too elongated. And currently
    the antenna + 'osmocom' + 'sgsn' is pretty long :)

Sylvain



From laforge at gnumonks.org  Tue Aug  3 09:45:17 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 3 Aug 2010 11:45:17 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <AANLkTik560Pj-QXR9fz7DmfVAAxG8AnjY-0gEU3fF2uR@mail.gmail.com>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de>
	<AANLkTik560Pj-QXR9fz7DmfVAAxG8AnjY-0gEU3fF2uR@mail.gmail.com>
Message-ID: <20100803094517.GK9698@prithivi.gnumonks.org>

On Tue, Aug 03, 2010 at 11:15:22AM +0200, Sylvain Munaut wrote:
> > If anyone has an idea how to decently make the difference between osmocomBB
> > and BSC more clear, or even has a completely different idea, let us hear/see
> > them :)
> 
> Two comments:
>  - I like the 'inverted' suffix
>  - I'm wondering if that suffix shouldn't be on the next line
>    (right aligned). It's to avoid a too elongated aspect ratio that
>    can sometime make it hard to use/integrate the logo when a more
>    'square' one is expected.
>    (doesn't need to be square, just not too elongated. And currently
>     the antenna + 'osmocom' + 'sgsn' is pretty long :)

I don't mind that it is more horizontal than veryical.  fits nice with
the trac logo approach in the upper left corner.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From chekov at riseup.net  Mon Aug 23 22:17:34 2010
From: chekov at riseup.net (chekov)
Date: Tue, 24 Aug 2010 00:17:34 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <20100730165851.GW13645@prithivi.gnumonks.org>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
Message-ID: <4C72F37E.10805@riseup.net>

hi

sorry for beeing late, but i had one more idea.
if you like it i can create the different versions(just some more letters)

On 30.07.2010 18:58, Harald Welte wrote:
> Hi!
> 
> It's about time that we find some kind of graphical project logo for the
> Osmocom project.
> 
> Osmocom is intended as an umbrella project for software like OpenBSC, OsmoSGSN, 
> OsmocomBB and others.
> 
> So it might even be interesting to have some kind of 'family' of logos that
> all have the same general theme.... At least the bigger projects like OpenBSC
> and OsmocomBB definitely deserve their own incarnation within that family.
> 
> If you want to contribute to our project but are not a die-hard C developer,
> this is your option to contribute!
> 
> The logo must be under a license that permits use+modification for the
> Osmocom project itself.  Editability for the general public is not important.
> 
> With regard to formats, I would prefer something as SVG that we can then
> render into pngs of various sizes whenever there is demand for it.
> 
> If you have a proposal, simply send it (or a link to a URL) to the
> openbsc at lists.gnumonks.org mailing list.
> 
> Thanks in advance for any submissions!
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Osmocom.svg
Type: image/svg+xml
Size: 10600 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100824/47e5d873/attachment.svg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100824/47e5d873/attachment.bin>

From squalyl at gmail.com  Mon Aug 23 22:49:00 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 24 Aug 2010 00:49:00 +0200
Subject: Wanted: Osmocom logo
In-Reply-To: <4C72F37E.10805@riseup.net>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C72F37E.10805@riseup.net>
Message-ID: <AANLkTikEjgV-RguQCH=W+svAOdNs_qG9t7syPAfMMvkN@mail.gmail.com>

Hi,

I think this is cellular-nice, except the "s" :)

Regards
Sebastien

On Tue, Aug 24, 2010 at 12:17 AM, chekov <chekov at riseup.net> wrote:

> hi
>
> sorry for beeing late, but i had one more idea.
> if you like it i can create the different versions(just some more letters)
>
> On 30.07.2010 18:58, Harald Welte wrote:
> > Hi!
> >
> > It's about time that we find some kind of graphical project logo for the
> > Osmocom project.
> >
> > Osmocom is intended as an umbrella project for software like OpenBSC,
> OsmoSGSN,
> > OsmocomBB and others.
> >
> > So it might even be interesting to have some kind of 'family' of logos
> that
> > all have the same general theme.... At least the bigger projects like
> OpenBSC
> > and OsmocomBB definitely deserve their own incarnation within that
> family.
> >
> > If you want to contribute to our project but are not a die-hard C
> developer,
> > this is your option to contribute!
> >
> > The logo must be under a license that permits use+modification for the
> > Osmocom project itself.  Editability for the general public is not
> important.
> >
> > With regard to formats, I would prefer something as SVG that we can then
> > render into pngs of various sizes whenever there is demand for it.
> >
> > If you have a proposal, simply send it (or a link to a URL) to the
> > openbsc at lists.gnumonks.org mailing list.
> >
> > Thanks in advance for any submissions!
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100824/7eb25892/attachment.htm>

From peter at stuge.se  Sun Aug  1 01:07:51 2010
From: peter at stuge.se (Peter Stuge)
Date: Sun, 1 Aug 2010 03:07:51 +0200
Subject: OsmocomBB, Problem , prospects discussed.. with Mr. Spaar..
In-Reply-To: <543977.87673.qm@web114204.mail.gq1.yahoo.com>
References: <543977.87673.qm@web114204.mail.gq1.yahoo.com>
Message-ID: <20100801010751.27587.qmail@stuge.se>

Hi Dev,

Dev Purohit wrote:
> i will share my source codes with you ?once finish my work.

Please reconsider this position. "once finished" is way too late to
be useful, unless you plan on creating a product that you will sell.

If you want cooperation and feedback from the community then I rather
strongly suggest sharing source code immediately when you start the
work.


Kind regards

//Peter



From laforge at gnumonks.org  Sun Aug  1 12:57:14 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 1 Aug 2010 14:57:14 +0200
Subject: [ANNOUNCE] planet.osmocom.org
Message-ID: <20100801125714.GK13645@prithivi.gnumonks.org>

Hi!

We now have a planet (RSS feed aggregator) for the Osmcoom project,
it's running at http://planet.osmocom.org/

Please let me know if you think I should add any feeds to it.  There is
no strict requirement for contributions to the Osmocom project, but
it should be technical and related to protocols / hacking / development
of mobile telephony systems.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From gentoo.lubomir at googlemail.com  Sun Aug  1 23:00:48 2010
From: gentoo.lubomir at googlemail.com (Lubomir Schmidt)
Date: Mon, 2 Aug 2010 01:00:48 +0200
Subject: sorry, my e-mail got hacked...
Message-ID: <AANLkTikp30FkO08Ph=2ygEKYZMMJM4uNRK-P+-mP+Nrm@mail.gmail.com>

sorry for the spam mails. My e-mail got hacked...



From devpurohit19 at yahoo.com  Mon Aug  2 02:36:09 2010
From: devpurohit19 at yahoo.com (Dev Purohit)
Date: Sun, 1 Aug 2010 19:36:09 -0700 (PDT)
Subject: OsmocomBB, Problem , prospects discussed
Message-ID: <745617.413.qm@web114208.mail.gq1.yahoo.com>






Hello Peter,
?
>Please reconsider this position. "once finished" is way too late to
be useful, unless you plan on creating a product that you will sell.

If you want cooperation and feedback from the community then I rather
strongly suggest sharing source code immediately when you start the
>work.

Thanks you for your concerns,
?
But as i have clearly ? mentioned that i have implemented Frequency Hoping, 
on DATA communication device ( telemetry?on ?ISM Band) and Hardware Platform ,communication schemes , protocols and modulation technique were very different, so source can't be integrated with OsmocomBB at this stage?, even patching also not that easy i estimated, and most difficult thing is i have very limited knowledge of G.S.M , my mostly ?time is consuming to study specifications .. Ohh, very lengthy subject.. anyways , I'm trying to deploy for cyclic FH first , choosing right algorithm. i have no problem or commercial value for sharing my work with great people , but it at least relevant and use full to this project.
?
I'm?neither developing any equipment?not planning to sell it..? MatLab is simulation platform and codes cant be implemented in real-time or live environment, also it support TI DSP's long range. so we can debug change to C header after wards.
?
Kind regards,
Dev
?
?
? 


--- On Sun, 8/1/10, baseband-devel-request at lists.osmocom.org <baseband-devel-request at lists.osmocom.org> wrote:


From: baseband-devel-request at lists.osmocom.org <baseband-devel-request at lists.osmocom.org>
Subject: baseband-devel Digest, Vol 7, Issue 1
To: baseband-devel at lists.osmocom.org
Date: Sunday, August 1, 2010, 10:00 AM


Send baseband-devel mailing list submissions to
??? baseband-devel at lists.osmocom.org

To subscribe or unsubscribe via the World Wide Web, visit
??? https://lists.osmocom.org/mailman/listinfo/baseband-devel
or, via email, send a message with subject or body 'help' to
??? baseband-devel-request at lists.osmocom.org

You can reach the person managing the list at
??? baseband-devel-owner at lists.osmocom.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of baseband-devel digest..."

Today's Topics:

???1. OsmocomBB, Problem , prospects discussed.. with Mr. Spaar.. 
? ? ? (Dev Purohit)
???2. Re: OsmocomBB, Problem , prospects discussed.. with Mr.
? ? ? Spaar..? (Dieter Spaar)
???3. Re: OsmocomBB, Problem , prospects discussed.. with Mr.
? ? ? Spaar.. (Peter Stuge)

_______________________________________________
baseband-devel mailing list
baseband-devel at lists.osmocom.org
https://lists.osmocom.org/mailman/listinfo/baseband-devel



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100801/15df45d0/attachment.htm>

From spaar at mirider.augusta.de  Fri Aug 13 10:40:43 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Fri, 13 Aug 2010 10:40:43 CEST
Subject: Status of Traffic channel
Message-ID: <4c65212b.mirider@mirider.augusta.de>

Hello,

here is some information about the current status of traffic
channel support in Layer-1:

  - first of all its not yet complete and considered "alpha"
    because there are some stability problems which have to
    be solved and some further enhancments for a more general
    approach are needed.

  - What works: Signalling (FACCH/SACCH) for a Full Rate Traffic
    channel and voice (Full Rate or Enhanced Full Rate Codec).

  - TODO: The Layer-1 API has to be extended to allow switching
    the channel mode (e.g. Signalling only) or the Voice Codec.
    Also turning the audio path on and off is needed.

  - TODO: The Rx/Tx TPU Window has been modified to support Rx and Tx
    operation in the same frame. This always happens for a Traffic
    Channel but can sometimes also happen for other channels. For
    those cases its necessary that the Tx TPU Window is set
    differently. Some sort of state information that Rx is happening
    in the same frame has to be implemented, this currently only
    works for traffic channels.

If you want to try it out you have to use the "dieter/tch_f" branch
for Layer-1 and the Master branch for Layer-23 from Andreas (really
great work, Andreas).

With this combination you can use it with OpenBSC. Some minor
adjustment is needed: The Layer-1 code currently sets the voice
Codec to "Full Rate", however OpenBSC expects "Enhanced Full Rate"
You either have to modify OpenBSC to set "Full Rate" or change
"TCH_FS_MODE" to "TCH_EFR_MODE" in "layer1/prim_rx_nb.c", there
is only one line which has to be changed.

What you can do now is a MOC/MTC between OsmocomBB and another
phone. Sometimes it can happen that the firmware hangs, you have
to restart the phone in this case. However if you have a connected
call, its working pretty good (one of the test calls was over 20
minutes).

Maybe Andreas can give a short introduction how to use Layer-23
for this, I am not sure if there is some information in the Wiki
yet.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From Andreas.Eversberg at versatel.de  Mon Aug 16 07:55:39 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Mon, 16 Aug 2010 09:55:39 +0200
Subject: assignment command / status of RR
Message-ID: <B16317F2B1592B4492FC414114171CE603CFB6CC@FLBVEXCH01.versatel.local>

hi,

as you can see in the git log, i checked in the "ASSIGNMENT COMMAND"
processing. it modifies timeslot, subslot, and hopping sequence. this is
required when the network assigns an SDCCH before the actual TCH is
allocated: after receiving the "ASSIGNMENT COMMAND", the layer2 is
release locally (without sending anything), the dedicated mode is
released and established with a new parameters (e.g. TCH/F), and the
layer2 is established again, finally the "ASSIGNMENT COMPLETE" is sent
to the network. this process is incomplete, but it should work in most
cases. (no "starting time" processing).

in my local copy of the git, i already completed the assignment process.
additionally "FREQUENCY REDEFINITION" is completed, "IMMEDIATE
ASSIGNMENT" supports "starting time", MDL-error processing is added, and
"HANDOVER COMMAND" parsing is done. the handover process is not
completed, because it depends on unimplemented layer1 features, like
RX-only channels or "4 successive HANDOVER ACCESS bursts on DCCH".
except the handover process, the RR protocol for basic phone calls is
complete now.

before i can check it in, it depends on two things. first, there are
additional messages to be defined in osmocore:
"[osmocore] Adding handover and frequency redefiniton message headers"
http://home.eversberg.eu/osmocore.patch

second, it depends on "starting time" support for layer1:
http://home.eversberg.eu/modify.patch
it adds a L1CTL message to store modified frequency allocations (ma,
ma_len, HSN, MAIO, TSC) for hopping and a "starting time". this starting
time is the frame number at which the modified frequencies are used. if
the frame number lies in the past, the new modified frequencies are used
after the L1CTL message is received. 

sylvain already noted, that the event of "starting time" should be
triggered by the scheduler. since i don't know how the scheduler exactly
works, i would ask someone to change my patch. note that the dedicated
mode can be released before the "starting time" elapses.

as soon as both things above are in the master branch, i will commit my
latest work on RR.

regards,

andreas


 




From Andreas.Eversberg at versatel.de  Mon Aug 16 11:08:27 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Mon, 16 Aug 2010 13:08:27 +0200
Subject: layer1: crash after receiving TX data
Message-ID: <B16317F2B1592B4492FC414114171CE603CFB8CE@FLBVEXCH01.versatel.local>

hi,
 
me and maybe some of you experiences sudden freeze of the layer1 firmware. it happens sometimes when sending L1CTL_DATA_REQ from layer2 to layer1. i found a way to reproduce it. see http://home.eversberg.eu/data.patch for testing it. just apply this patch and uncomment the "?#define" line.
 
this patch will transmit idle frames, if there is no frame in the tx-queue of lapdm. (DCCH) even if there is a frame to be sent, the lapdm process will wait until the data is confirmed by layer1 until sendig the next frame. this confirm is sent when the data has been transmitted by layer1 (i think). this is why the queue inside layer1 cannot overflow.
 
this patch does not work correctly somehow. when sending the idle frame, the location update seems not to work. the lapdm fails. but this doesn't matter for the crash-test. until then, more than 20 frames are transmitted. if the mobile application is restarted, more frames will be transmitted. between 45 and 60 frames later the layer1 freezes. the display gets a little darker also.
 
andreas
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100816/7dbbfa6f/attachment.htm>

From Andreas.Eversberg at versatel.de  Tue Aug 17 15:33:53 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Tue, 17 Aug 2010 17:33:53 +0200
Subject: sim client
Message-ID: <B16317F2B1592B4492FC414114171CE603D91DC6@FLBVEXCH01.versatel.local>

hi,
 
i like to write the sim client protocol. i do not mean the code of the
"sim reader" which is part of layer1 inside the phone. before i start, i
would like to know what you think about my api idea. the api is not the
low-level api between layer1 and the mobile application (APDU layer). it
describes a higher layer for application or protocol processes which
need to request IMSI, do key generation, or store location area
information.
 
one important thing is that different processes must be able request
"read", "write", or other operations like key generation simultaniously.
in order to handle multiple requests after each other, a queue inside
sim client must exist. afterwar processing each request, the result must
be sent only to the requesting process (if it still exists). a state
machine watches over the current DF (current selected file area of the
sim) and changes current "DF" if required, before processing read or
write job. also it triggers the next job in the queue, if finished with
the current one.
 
int handle = sim_open(void (*cb)(...))
 
will add a new user instance. cb is the function to be called for
response, handle is a unique id of the process (not a memory pointer,
unique at all times after starting phone).
 
void sim_job(struct msgb *msg)
 
struct sim_job_hdr {
    int handle;
    uint8_t job_type;
    uint16_t file;
};
 
will add a new job. the type defines the job type. examples are "READ"
"WRITE" or "GSMKEY" requests. the handle is used to assign the
read/write job to an instance. the file is used to select the correct
data file of the sim. the data and len represent the data to be written.
 
void cb(struct msgb *msg)
 
is called back by the sim client when job is done. the handle is given,
so multiple user  instances may use the same callback.
 
void sim_close(int handle)
 
will remove user instance. outstanding jobs will finish, but no result
is given, because cb is now unregistered.
 
 
the coding and decoding of SIM files must be done by the application or
protocol layer that use the sim client.
 
 
andreas
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100817/cae49e5e/attachment.htm>

From squalyl at gmail.com  Tue Aug 17 16:20:27 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 17 Aug 2010 18:20:27 +0200
Subject: sim client
In-Reply-To: <B16317F2B1592B4492FC414114171CE603D91DC6@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE603D91DC6@FLBVEXCH01.versatel.local>
Message-ID: <AANLkTikwpAGtMAPZWRJV0uLpEv7amw2RqR+szw=Rn_6s@mail.gmail.com>

Hi,

I am OK with your ideas, with some remarks:

- please rename WRITE to UPDATE. Writing is the process of flipping bits
from "0" to "1" in a file, resulting in a logical OR between the old data
and the new data (AND-writing also exists). An erase is needed to flip these
bits to zero. Update is the process of overwriting old data with new data.
The concepts are clearly separated in ISO7816, and the GSM 11.11 spec does
not support writing to a SIM but only updating (which is good :)). This is
only a wording issue, and I will not kill a kitten if someone prefers to
keep the "write" wording.

- the uint16_t file shall be a path, ie uint16_t path[MAX_SIM_PATH_LENGTH]
where MAX_SIM_PATH_LENGTH is a small constant, ie 4 or 6.
rationale: normal UICCs only have a single telecom and a single gsm DF. But
we might want to develop multi-DF SIMs, ie one DF for the normal carrier,
and another one for an OpenBSC network. Storing a file_id and a df_id is
another option, but DFs can be nested so I don't like it because it's too
restrictive.

-what about incoming data? This should be stored inside the job. On an
update job, the callback will tell you that the update was completed, but
you have to send the data anyway. Let's call that the job payload.
Unfortunately GSM11.11 tells that updates can be 255 bytes long, which is
annoying if such a long buffer is needed, I agree. Something smaller may
fit, we will never update 255 bytes at once. The offset at which to update
must be also stored. GSMKEY and PIN operations will also need this incoming
data.

-what about PIN presentation? This should be a separate job type, with the
PIN code as job payload. Okay, this is not needed in a first version.

-there are two file types. Transparent and record files. The first one are
"classic" files, the other are typically accessed one record at a time (e.g.
phonebook entries) What about these access differences? We can abstract this
differences if we know the record size via a separate call or job type.

Regards
Sebastien

On Tue, Aug 17, 2010 at 5:33 PM, Andreas.Eversberg <
Andreas.Eversberg at versatel.de> wrote:

>  hi,
>
> i like to write the sim client protocol. i do not mean the code of the "sim
> reader" which is part of layer1 inside the phone. before i start, i would
> like to know what you think about my api idea. the api is not the low-level
> api between layer1 and the mobile application (APDU layer). it describes a
> higher layer for application or protocol processes which need to request
> IMSI, do key generation, or store location area information.
>
> one important thing is that different processes must be able request
> "read", "write", or other operations like key generation simultaniously. in
> order to handle multiple requests after each other, a queue inside sim
> client must exist. afterwar processing each request, the result must be sent
> only to the requesting process (if it still exists). a state machine
> watches over the current DF (current selected file area of the sim) and
> changes current "DF" if required, before processing read or write job. also
> it triggers the next job in the queue, if finished with the current one.
>
> *int handle = sim_open(void (*cb)(...))*
>
> will add a new user instance. cb is the function to be called for response,
> handle is a unique id of the process (not a memory pointer, unique at all
> times after starting phone).
>
> *void sim_job(struct msgb *msg)*
> **
> *struct sim_job_hdr {*
> *    int handle;*
> *    uint8_t job_type;*
> *    uint16_t file;*
> *};*
>
> will add a new job. the type defines the job type. examples are "READ"
> "WRITE" or "GSMKEY" requests. the handle is used to assign the read/write
> job to an instance. the file is used to select the correct data file of the
> sim. the data and len represent the data to be written.
>
> *void cb(struct msgb *msg)*
>
> is called back by the sim client when job is done. the handle is given, so
> multiple user  instances may use the same callback.
>
> *void sim_close(int handle)*
>
> will remove user instance. outstanding jobs will finish, but no result is
> given, because cb is now unregistered.
>
>
> the coding and decoding of SIM files must be done by the application or
> protocol layer that use the sim client.
>
>
> andreas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100817/940baae8/attachment.htm>

From Andreas.Eversberg at versatel.de  Thu Aug 19 09:42:44 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Thu, 19 Aug 2010 11:42:44 +0200
Subject: AW: sim client
Message-ID: <B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>

hi sebastien,
 
thanx for you advice. i will have job names like SIM_JOB_READ, SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path array. i always thought that each EF has a unique ID. the DF where it is located, can be determined by the first byte of the EF ID. but if it is possible to have a sim with multiple DFgsm, then a path is required of course.
 
for PIN handling, i will use result codes that gives cause of an error. if a PIN is required (to read the IMSI for example), the error code would show that. then the sim reading process prompts for PIN. the SIM can be unlocked ("enabled") by a message like SIM_JOB_ENABLE_CHV1.
 
outgoing data (UPDATE) is located behind the header. incomming data is also located behind the header when the job returns (callback fn is called). but the READ job must be triggered.
 
when my code must deal with record types, i will expand the header. i will create the API step by step.
 
regards
 
andreas
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100819/945a5fe3/attachment.htm>

From laforge at gnumonks.org  Thu Aug 19 11:40:35 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 19 Aug 2010 13:40:35 +0200
Subject: sim client
In-Reply-To: <B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>
Message-ID: <20100819114035.GZ4849@prithivi.gnumonks.org>

On Thu, Aug 19, 2010 at 11:42:44AM +0200, Andreas.Eversberg wrote:
> hi sebastien,
>  
> thanx for you advice. i will have job names like SIM_JOB_READ,
> SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path array. i
> always thought that each EF has a unique ID. the DF where it is located, can
> be determined by the first byte of the EF ID. but if it is possible to have a
> sim with multiple DFgsm, then a path is required of course.

I think it isn't good to just think of a normal SIM, but keep it as flexible
with regard to smartcards compliant to 7816-4.  Adding a path will not really
make things terribly more complex, so I'd also agree with Sebastien to include
tha path and be more flexible as a result.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From squalyl at gmail.com  Thu Aug 19 11:49:56 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Thu, 19 Aug 2010 13:49:56 +0200
Subject: sim client
In-Reply-To: <20100819114035.GZ4849@prithivi.gnumonks.org>
References: <B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>
	<20100819114035.GZ4849@prithivi.gnumonks.org>
Message-ID: <AANLkTin8DR5SiH0B_o8vxCYN-sCjLp2CN6RPLBSh9cnY@mail.gmail.com>

Hi,

Well the reply from Harald tells me I didn't get Andreas' response in full,
and it seems some replies have to be made.

Can someone forward it to the list?

Regards
Sebastien

On Thu, Aug 19, 2010 at 1:40 PM, Harald Welte <laforge at gnumonks.org> wrote:

> On Thu, Aug 19, 2010 at 11:42:44AM +0200, Andreas.Eversberg wrote:
> > hi sebastien,
> >
> > thanx for you advice. i will have job names like SIM_JOB_READ,
> > SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path
> array. i
> > always thought that each EF has a unique ID. the DF where it is located,
> can
> > be determined by the first byte of the EF ID. but if it is possible to
> have a
> > sim with multiple DFgsm, then a path is required of course.
>
> I think it isn't good to just think of a normal SIM, but keep it as
> flexible
> with regard to smartcards compliant to 7816-4.  Adding a path will not
> really
> make things terribly more complex, so I'd also agree with Sebastien to
> include
> tha path and be more flexible as a result.
>
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                  (ETSI EN 300 175-7 Ch. A6)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100819/9f931d15/attachment.htm>

From squalyl at gmail.com  Thu Aug 19 13:09:14 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Thu, 19 Aug 2010 15:09:14 +0200
Subject: sim client
In-Reply-To: <B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>
References: <Acs+KL94EuhRiiHOQ9aPXP98loxMXQBUXEqw>
	<B16317F2B1592B4492FC414114171CE603D92652@FLBVEXCH01.versatel.local>
Message-ID: <AANLkTinRAYO0OT_UEc6eCVpn72hAAObjZxzGwx8+0XdF@mail.gmail.com>

Hi,

I finally found your message. Don't know why it was routed to the spam by
google. Maybe the blue text reminds the color of viagra? Whatever...

The only identifier that can be card-unique is the SFI (short ID from 1 to
30) but it's not used by sim cards.

The 2 bytes ED/DF identifier (LID, long id) is unique in a directory context
so that a select operation is not ambiguous.
The common LID MSB is a classic limitation (used in GSM) that allows to save
memory: Just save the LSB in the file descriptor and the MSB in the DF.
But it's an arbitrary limitation. According to ISO7816-4, LIDs can be
absolutely what you want.

Okay for the result codes to trigger a PIN request.

Sebastien

On Thu, Aug 19, 2010 at 11:42 AM, Andreas.Eversberg <
Andreas.Eversberg at versatel.de> wrote:

>  hi sebastien,
>
> thanx for you advice. i will have job names like SIM_JOB_READ,
> SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path array.
> i always thought that each EF has a unique ID. the DF where it is located,
> can be determined by the first byte of the EF ID. but if it is possible to
> have a sim with multiple DFgsm, then a path is required of course.
>
> for PIN handling, i will use result codes that gives cause of an error. if
> a PIN is required (to read the IMSI for example), the error code would show
> that. then the sim reading process prompts for PIN. the SIM can be unlocked
> ("enabled") by a message like SIM_JOB_ENABLE_CHV1.
>
> outgoing data (UPDATE) is located behind the header. incomming data is also
> located behind the header when the job returns (callback fn is called). but
> the READ job must be triggered.
>
> when my code must deal with record types, i will expand the header. i will
> create the API step by step.
>
> regards
>
> andreas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100819/84f7a742/attachment.htm>

From Andreas.Eversberg at versatel.de  Mon Aug 23 11:14:17 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Mon, 23 Aug 2010 13:14:17 +0200
Subject: using BTSAP from layer23
Message-ID: <B16317F2B1592B4492FC414114171CE603DF7BF6@FLBVEXCH01.versatel.local>

 
hi,
 
i am current writing the sim client for layer23. this client transforms
the read and update requests from layer 3 (imsi read, location update)
into several APDUs to be transferred via BTSAP interface. (interface to
layer 1) here are two questions:

how do i interface to this BTSAP? i see that there is another unix
socket for that. do i need to expand main.c of layer23?

i think that i cannot just start sending APDUs after starting layer23.
there might be something like an initialization sequence before:
- power on
- reset
- get atr
- ...
- send APDU
- receive APDU
- ...
is there a defined sequence or flow chart for that?

regards,

andreas




From squalyl at gmail.com  Mon Aug 23 11:42:45 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 23 Aug 2010 13:42:45 +0200
Subject: using BTSAP from layer23
In-Reply-To: <B16317F2B1592B4492FC414114171CE603DF7BF6@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE603DF7BF6@FLBVEXCH01.versatel.local>
Message-ID: <AANLkTikDdw-tfPWaH9XJK_1vN92o7ahQPudRhW85BDDo@mail.gmail.com>

Hi,

The startup is not complicated and no 'official' sequence is defined.
You must power up the card, then reset  it and read the ATR.
Then, a PPS exchange can optionally be done (please refer to ISO7816-3 or
GSM 11.11) to optimize the transfer speed with the SIM.

Please also include a provision for sending additional startup apdus (or at
least one), such as SELECT APPLICATION apdus. However, this is not required
for a standard SIM or in a preliminary version.

When this project started, we mentioned the ability to route the SIM
requests to a standard PCSC reader via pcsclite.
Please include this ability in your code, along with communication with the
embedded sim reader.
This will be very useful when we'll be ready to use our own sim cards (I'm
--part-part-time-- working on this).

Regards
Sebastien.

PS: don't forget that communication with a card is always part of exchanges.
The ATR always accompanies the reset operation, and the response apdu is
always linked to the command apdu.


On Mon, Aug 23, 2010 at 1:14 PM, Andreas.Eversberg <
Andreas.Eversberg at versatel.de> wrote:

>
> hi,
>
> i am current writing the sim client for layer23. this client transforms
> the read and update requests from layer 3 (imsi read, location update)
> into several APDUs to be transferred via BTSAP interface. (interface to
> layer 1) here are two questions:
>
> how do i interface to this BTSAP? i see that there is another unix
> socket for that. do i need to expand main.c of layer23?
>
> i think that i cannot just start sending APDUs after starting layer23.
> there might be something like an initialization sequence before:
> - power on
> - reset
> - get atr
> - ...
> - send APDU
> - receive APDU
> - ...
> is there a defined sequence or flow chart for that?
>
> regards,
>
> andreas
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100823/b677cf6c/attachment.htm>

From Andreas.Eversberg at versatel.de  Sun Aug 29 11:29:06 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Sun, 29 Aug 2010 13:29:06 +0200
Subject: SIM client
Message-ID: <B16317F2B1592B4492FC414114171CE603EE9704@FLBVEXCH01.versatel.local>

hi,
 
i committed the SIM client process for layer23. it turns reading and
writing jobs (from and to SIM files) into APDUs. because the SIM reader
is not yet finished, it cannot be tested yet.
 
after attaching the SIM card, a process in mobile/subscriber.c will
request all required files form that card before starting the network
selection process. (untested, as noted above)
 
the mobility management is now cleaned up: TODO comments in the source
code are replaced by SIM update commands to the SIM client.
 
in order to make mobile application work with public networks, we need
to perform the following steps:
 
- finish the SIM reader and interface in layer 1
- add BTSAP interface to layer23
- add measurement reports to both TCH and SDCCH4/8 (*)
- send updates for measurement report from layer23 via l23 api of layer
1
- add crpyto-key request to layer 1 and l1-l2 interface (dieter ?)
 
* tests showed that the measurement report on SDCCH4/8 is requred. if
not sent, the network releases a call (cleanly) after the mobile stays
for a some seconds on an SDCCH4/8 (probably waiting for measurements,
before completing the call). sending some dummy measurements completed
the call successfully.
 

beside that, the following issues need to be solved soon, in order to
make the layer 1 firmware usable and stable:
 
- additional structures for the libosmocore, see
http://home.eversberg.eu/osmocore.patch
<http://home.eversberg.eu/osmocore.patch> 
- freeze of layer 1 after about 40-60 data messages, see
http://home.eversberg.eu/data.patch
<http://home.eversberg.eu/data.patch>  for testing. after a few location
updates firmware freezes. (the location update will fail, because the
patch disturbs location updating process, but the bug show up.)
- syncing problem
- clock drifts away after sync
- subchannels 4..8 of SDCCH/8
and maybe
- tch mode l1ctl message to select signalling only / speech codec of
TCH/F / TCH/H. (including bearer capability processing in layer23)
 

regards,
 
andreas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100829/ebc76970/attachment.htm>

From spaar at mirider.augusta.de  Sun Aug 29 17:13:45 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Sun, 29 Aug 2010 17:13:45 CEST
Subject: SIM client
Message-ID: <4c7a9549.mirider@mirider.augusta.de>

Hello Andreas,

On Sun, 29 Aug 2010 13:29:06 +0200, "Andreas.Eversberg" <Andreas.Eversberg at versatel.de> wrote:
>
> - add crpyto-key request to layer 1 and l1-l2 interface (dieter ?)

I can take care of Encryption support in Layer-1. However I will
probably not find time for it before next weekend.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From squalyl at gmail.com  Mon Aug 30 05:27:19 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 30 Aug 2010 07:27:19 +0200
Subject: SIM client
In-Reply-To: <4c7a9549.mirider@mirider.augusta.de>
References: <4c7a9549.mirider@mirider.augusta.de>
Message-ID: <AANLkTikj8FxJNWx22u3cGJaVoB9giutOWY6379AdhCKQ@mail.gmail.com>

Hi,

As soon as it's possible, can someone send me samples for the apdus you send
to the card?

the reason is that I'm working on a javacard sim applet and that the status
words probably won't be the same as what is required per gsm 11.11.
So in order to support our own developments, it may be a good thing to
support 2 valid SW values on command return.

For example, i don't remember what does a SIM says when it has to reply
data, but javacards reply 61XX and not something that starts with 9YXX.

Regards
Sebastien

On Sun, Aug 29, 2010 at 4:13 PM, Dieter Spaar <spaar at mirider.augusta.de>wrote:

> Hello Andreas,
>
> On Sun, 29 Aug 2010 13:29:06 +0200, "Andreas.Eversberg" <
> Andreas.Eversberg at versatel.de> wrote:
> >
> > - add crpyto-key request to layer 1 and l1-l2 interface (dieter ?)
>
> I can take care of Encryption support in Layer-1. However I will
> probably not find time for it before next weekend.
>
> Best regards,
>  Dieter
> --
> Dieter Spaar, Germany                           spaar at mirider.augusta.de
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100830/2c127c49/attachment.htm>

From spaar at mirider.augusta.de  Mon Aug 30 08:07:35 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Mon, 30 Aug 2010 08:07:35 CEST
Subject: SIM client
Message-ID: <4c7b66c7.mirider@mirider.augusta.de>

Hello Sebastien,

On Mon, 30 Aug 2010 07:27:19 +0200, "=?UTF-8?Q?S=C3=A9bastien_Lorquet?=" <squalyl at gmail.com> wrote:
> 
> For example, i don't remember what does a SIM says when it has to reply
> data, but javacards reply 61XX and not something that starts with 9YXX.

For GSM its 9Fxx (GSM11.11, 9.4. contains a list of all status codes).

Not sure if this trace here is usefull (at the same site there is also
one for an USIM):

  http://www.wrankl.de/UThings/SIM-ME-Communication.pdf

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From squalyl at gmail.com  Mon Aug 30 06:48:09 2010
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 30 Aug 2010 08:48:09 +0200
Subject: SIM client
In-Reply-To: <4c7b66c7.mirider@mirider.augusta.de>
References: <4c7b66c7.mirider@mirider.augusta.de>
Message-ID: <AANLkTinfO5BGjcwGyeMAfzyJ-J9F=HV9DUjng8QuBRDn@mail.gmail.com>

Hi,

thanks for the reminder and the trace.

Then, Andreas, when your code deals with 9FXX status codes, it shall also
accept with 61XX status codes, with the same behaviour.

regards
Sebastien

On Mon, Aug 30, 2010 at 7:07 AM, Dieter Spaar <spaar at mirider.augusta.de>wrote:

> Hello Sebastien,
>
> On Mon, 30 Aug 2010 07:27:19 +0200, "=?UTF-8?Q?S=C3=A9bastien_Lorquet?=" <
> squalyl at gmail.com> wrote:
> >
> > For example, i don't remember what does a SIM says when it has to reply
> > data, but javacards reply 61XX and not something that starts with 9YXX.
>
> For GSM its 9Fxx (GSM11.11, 9.4. contains a list of all status codes).
>
> Not sure if this trace here is usefull (at the same site there is also
> one for an USIM):
>
>  http://www.wrankl.de/UThings/SIM-ME-Communication.pdf
>
> Best regards,
>  Dieter
> --
> Dieter Spaar, Germany                           spaar at mirider.augusta.de
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100830/5c3104df/attachment.htm>

From sweisman at pobox.com  Tue Aug 31 13:41:48 2010
From: sweisman at pobox.com (Scott Weisman)
Date: Tue, 31 Aug 2010 16:41:48 +0300
Subject: problem starting out...please help
Message-ID: <AANLkTimGT7ay+r_Ync9uQXiFYs5DUx=USygaqh5SBP8F@mail.gmail.com>

Hi All,

I now have a V171 phone and cable so I thought I might get started with
this.

I checked out the code and started make. Osmocon built with no problem, but
I got this error next:

cd shared/libosmocore/build-target && ../configure \
                        --host=arm-elf-linux --disable-vty
--enable-panic-infloop \
                        --disable-shared --disable-talloc --disable-tests \
                CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I../../../../target/firmware/include"
configure: WARNING: if you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for arm-elf-linux-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-elf-linux-gcc... arm-elf-gcc
checking whether the C compiler works... no
configure: error: in
`/mnt/site/osmocom-bb/src/shared/libosmocore/build-target':
configure: error: C compiler cannot create executables
See `config.log' for more details
make: *** [shared/libosmocore/build-target/Makefile] Error 77

Checking config.log I can see it chokes here:

/usr/bin/arm-elf-ld: this linker was not configured to use sysroots
collect2: ld returned 1 exit status

I am running Arch Linux and have the packages cross-arm-elf-binutils
and cross-arm-elf-gcc-base installed. Does anyone have any suggestions to
fix this?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100831/a498c168/attachment.htm>

From peter at stuge.se  Tue Aug 31 14:04:57 2010
From: peter at stuge.se (Peter Stuge)
Date: Tue, 31 Aug 2010 16:04:57 +0200
Subject: problem starting out...please help
In-Reply-To: <AANLkTimGT7ay+r_Ync9uQXiFYs5DUx=USygaqh5SBP8F@mail.gmail.com>
References: <AANLkTimGT7ay+r_Ync9uQXiFYs5DUx=USygaqh5SBP8F@mail.gmail.com>
Message-ID: <20100831140457.22679.qmail@stuge.se>

Scott Weisman wrote:
> /usr/bin/arm-elf-ld: this linker was not configured to use sysroots
> collect2: ld returned 1 exit status

As always, it would be helpful to also see the last few commands that
were executed, to get more context.


> I am running Arch Linux and have the packages cross-arm-elf-binutils
> and cross-arm-elf-gcc-base installed. Does anyone have any
> suggestions to fix this?

Mh. My guess is that toolchain is intended for building Linux
systems, or in any case building "systems" with some packaging
support, and intent to install into a root filesystem - as opposed
to just cross-compiling bare metal sources with no filesystem ever
involved..

I assume you've googled for arch and this error and have found
https://bbs.archlinux.org/viewtopic.php?id=62644 - and since you're
an Arch user maybe you already know what PKGBUILD and ABS are and how
they are intended to operate. (I've never used Arch, but I guess ABS
is Arch Build System, which might support my other guess that your
toolchain is just not suitable for building osmocom-bb.)


//Peter



From sweisman at pobox.com  Tue Aug 31 14:15:29 2010
From: sweisman at pobox.com (Scott Weisman)
Date: Tue, 31 Aug 2010 17:15:29 +0300
Subject: problem starting out...please help
In-Reply-To: <20100831140457.22679.qmail@stuge.se>
References: <AANLkTimGT7ay+r_Ync9uQXiFYs5DUx=USygaqh5SBP8F@mail.gmail.com>
	<20100831140457.22679.qmail@stuge.se>
Message-ID: <AANLkTim1uRf31BUBXQA9PTvpk8t86LJfT6DF=-dfiKA2@mail.gmail.com>

This is very useful info. Thanks! I will look into building my own toolchain
then.

I'm looking forward to playing around with this.

Scott

On Tue, Aug 31, 2010 at 5:04 PM, Peter Stuge <peter at stuge.se> wrote:

> Scott Weisman wrote:
> > /usr/bin/arm-elf-ld: this linker was not configured to use sysroots
> > collect2: ld returned 1 exit status
>
> As always, it would be helpful to also see the last few commands that
> were executed, to get more context.
>
>
> > I am running Arch Linux and have the packages cross-arm-elf-binutils
> > and cross-arm-elf-gcc-base installed. Does anyone have any
> > suggestions to fix this?
>
> Mh. My guess is that toolchain is intended for building Linux
> systems, or in any case building "systems" with some packaging
> support, and intent to install into a root filesystem - as opposed
> to just cross-compiling bare metal sources with no filesystem ever
> involved..
>
> I assume you've googled for arch and this error and have found
> https://bbs.archlinux.org/viewtopic.php?id=62644 - and since you're
> an Arch user maybe you already know what PKGBUILD and ABS are and how
> they are intended to operate. (I've never used Arch, but I guess ABS
> is Arch Build System, which might support my other guess that your
> toolchain is just not suitable for building osmocom-bb.)
>
>
> //Peter
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100831/4c3b8050/attachment.htm>

From begy at online.de  Tue Aug 31 18:22:22 2010
From: begy at online.de (Begerad Stefan)
Date: Tue, 31 Aug 2010 20:22:22 +0200
Subject: Problems while building osmocomBB
Message-ID: <4C7D485E.8080700@online.de>

Hi guys,
I dunno if that is the right place for my concern about building the 
osmocomBB source. Here is what I already have done:

- downloading the sources for osmocomBB and GNU toolchain for ARM,
- setting the PATH for the arm-elf-* executables,
- calling make in the src directory.

Now, this appears as response of the make command in the terminal:


cd shared/libosmocore/build-host && ../configure
configure: error: cannot find install-sh, install.sh, or shtool in ".." 
"../.." "../../.."
make: *** [shared/libosmocore/build-host/Makefile] Error 1.


If you need details about my system, you can look at the following 
snippet from the config.log file:


This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by libosmocore configure UNKNOWN, which was
generated by GNU Autoconf 2.65.  Invocation command line was

   $ ../configure

## --------- ##
## Platform. ##
## --------- ##

hostname = ubuntu-stefan
uname -m = x86_64
uname -r = 2.6.32-24-generic
uname -s = Linux
uname -v = #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /home/stefan/osmocomBB/gnuarm-4.0.2/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2032: error: cannot find install-sh, install.sh, or shtool in 
".." "../.." "../../..".


So, I would be very glad, if someone could give me a hint to solve the 
problem. Thank you in advance.

Regards,
begy