Total: 0,00 €



  • Sunday, July 28, 2013 - 09:11
    Sean Moss-Pultz: Involve the user in the design


    In 1974, Enzo Mari published “Autoprogettazione” – a book of plans that can only be described as open source furniture. In it’s final form, the book was sent, for free, to anyone that asked for it. Really it was more of a project than a book, though. The purpose, says Mari, was to teach how to “judge current production with a critical eye”.

    How is it possible to change the state of things? This is what I ask myself. How is it possible to accomplish the deconditioning of form as a value rather than as strictly corresponding to contact? The only way I know, in that it belongs to my field experience, is what becomes possible when critical thought is based on practical work. Therefore the only way should be to involve the user of a consumer item in the design and realization of the item design. Only by actually touching the diverse contradictions of the job is it possible to start to be free from such deeply rooted conditioning. But how is it possible to expect such an effort when the production tools are lacking as is, above all, the technical know-how, the technical culture it would take a fairly long time to acquire?

    In the autumn months, I plan to adapt one of his table designs for an outdoor workbench.

  • Sunday, July 21, 2013 - 15:58
    Sean Moss-Pultz: This isn’t my fight… but

    Ever since OK Computer, I’ve loved Radiohead. I so admire how they’ve traveled their own path; and done so with immense commercial successful – selling over 30 million albums. I remember staying up late to support their pay-what-you-want release of “In Rainbows”. And then being inspired as hell when I learned they shot “House of Cards” (2008) using not cameras, but lasers. (The visualization was done using Processing. They even open sourced the data on Google Code!)

    This past week Nigel Godrich, their longtime engineer / producer / musician, went after Spotify:

    Streaming is obviously the music distribution model moving forward. I listen to Spotify. I think it’s an amazing product; but I totally agree with Nigel here, that doesn’t make it right for the channel to commodify artists to keep their share prices up.

    Something’s got to change. Our industry (tech) is terrible at this sort of thing (music, apps, newspapers, …). I can’t tell you how many times people have told me, “Content is king.” You know what? It’s total bullshit. It’s ludicrous to pretend that ones and zeros are all created equal. Kill-off the ability of the creatives to make a living, and we’ll see how that “content” sounds.

    I’m with Radiohead on this one. We need a rebellion.

  • Saturday, July 13, 2013 - 10:58
    Chris Lord: Getting healthy

    I’ve never really considered myself an unhealthy person. I exercise quite regularly and keep up with a reasonable amount of active hobbies (climbing, squash, tennis). That’s not really lapsed much, except for the time the London Mozilla office wasn’t ready and I worked at home – I think I climbed less during that period. Apparently though, that isn’t enough… After EdgeConf, I noticed in the recording of the session I participated in that I was looking a bit more plump than the mental image I had of myself. I weighed myself, and came to the shocking realisation that I was almost 14 stone (89kg). This put me well into the ‘overweight’ category, and was at least a stone heavier than I thought I was.

    I’d long been considering changing my diet. I found Paul Rouget’s post particularly inspiring, and discussing diet with colleagues at various work-weeks had put ideas in my head. You could say that I was somewhat of a diet sceptic; I’d always thought that exercise was the key to maintaining a particular weight, especially cardiovascular exercise, and that with an active lifestyle you could get away with eating what you like. I’ve discovered that, for the most part, this was just plain wrong.

    Before I go into the details of what I’ve done over the past 5 months, let me present some data:

  • Thursday, June 27, 2013 - 17:29
    Holger "zecke" Freyther: Using GNU autotest for running unit tests
    This is part of a series of blog posts about testing inside the OpenBSC/Osmocom project. In this post I am focusing on our usage of GNU autotest.

    The GNU autoconf ships with a not well known piece of software. It is called GNU autotest and we will focus about it in this blog post.

    GNU autotest is a very simple framework/test runner. One needs to define a testsuite and this testsuite will launch test applications and record the exit code, stdout and stderr of the test application. It can diff the output with expected one and fail if it is not matching. Like any of the GNU autotools a log file is kept about the execution of each test. This tool can be nicely integrated with automake's make check and make distcheck. This will execute the testsuite and in case of a test failure fail the build.

    The way we use it is also quite simple as well. We create a simple application inside the test/testname directory and most of the time just capture the output on stdout. Currently no unit-testing framework is used, instead a simple application is built that is mostly using OSMO_ASSERT to assert the expectations. In case of a failure the application will abort and print a backtrace. This means that in case of a failure the stdout will not not be as expected and the exit code will be wrong as well and the testcase will be marked as FAILED.

    The following will go through the details of enabling autotest in a project.

    Enabling GNU autotest

    The configure.ac file needs to get a line like this: AC_CONFIG_TESTDIR(tests). It needs to be put after the AC_INIT and AM_INIT_AUTOMAKE directives and make sure AC_OUTPUT lists tests/atlocal

    Integrating with the automake

    The next thing is to define a testsuite inside the tests/Makefile.am. This is some boilerplate code that creates the testsuite and makes sure it is invoked as part of the build process.

     # The `:;' works around a Bash 3.2 bug when the output is not writeable.  
    $(srcdir)/package.m4: $(top_srcdir)/configure.ac
    :;{ \
    echo '# Signature of the current package.' && \
    echo 'm4_define([AT_PACKAGE_NAME],' && \
    echo ' [$(PACKAGE_NAME)])' &&; \
    echo 'm4_define([AT_PACKAGE_TARNAME],' && \
    echo ' [$(PACKAGE_TARNAME)])' && \
    echo 'm4_define([AT_PACKAGE_VERSION],' && \
    echo ' [$(PACKAGE_VERSION)])' && \
    echo 'm4_define([AT_PACKAGE_STRING],' && \
    echo ' [$(PACKAGE_STRING)])' && \
    echo 'm4_define([AT_PACKAGE_BUGREPORT],' && \
    echo ' [$(PACKAGE_BUGREPORT)])'; \
    echo 'm4_define([AT_PACKAGE_URL],' && \
    echo ' [$(PACKAGE_URL)])'; \
    } &>'$(srcdir)/package.m4'
    EXTRA_DIST = testsuite.at $(srcdir)/package.m4 $(TESTSUITE)
    TESTSUITE = $(srcdir)/testsuite
    DISTCLEANFILES = atconfig
    check-local: atconfig $(TESTSUITE)
    installcheck-local: atconfig $(TESTSUITE)
    $(SHELL) '$(TESTSUITE)' AUTOTEST_PATH='$(bindir)' \
    test ! -f '$(TESTSUITE)' || \
    $(SHELL) '$(TESTSUITE)' --clean
    AUTOM4TE = $(SHELL) $(top_srcdir)/missing --run autom4te
    AUTOTEST = $(AUTOM4TE) --language=autotest
    $(TESTSUITE): $(srcdir)/testsuite.at $(srcdir)/package.m4
    $(AUTOTEST) -I '$(srcdir)' -o $@.tmp $@.at
    mv $@.tmp $@

    Defining a testsuite

    The next part is to define which tests will be executed. One needs to create a testsuite.at file with content like the one below:
    AT_BANNER([Regression tests.])
    cat $abs_srcdir/gsm0408/gsm0408_test.ok > expout
    AT_CHECK([$abs_top_builddir/tests/gsm0408/gsm0408_test], [], [expout], [ignore])
    This will initialize the testsuite, create a banner. The lines between AT_SETUP and AT_CLEANUP represent one testcase. In there we are copying the expected output from the source directory into a file called expout and then inside the AT_CHECK directive we specify what to execute and what to do with the output.

    Executing a testsuite and dealing with failure

    The testsuite will be automatically executed as part of make check and make distcheck. It can also be manually executed by entering the test directory and executing the following.

     $ make testsuite  
    make: `testsuite' is up to date.
    $ ./testsuite
    ## ---------------------------------- ##
    ## openbsc test suite. ##
    ## ---------------------------------- ##
    Regression tests.
    1: gsm0408 ok
    2: db ok
    3: channel ok
    4: mgcp ok
    5: gprs ok
    6: bsc-nat ok
    7: bsc-nat-trie ok
    8: si ok
    9: abis ok
    ## ------------- ##
    ## Test results. ##
    ## ------------- ##
    All 9 tests were successful.
    In case of a failure the following information will be printed and can be inspected to understand why things went wrong.
    2: db FAILED (testsuite.at:13)
    ## ------------- ##
    ## Test results. ##
    ## ------------- ##
    ERROR: All 9 tests were run,
    1 failed unexpectedly.
    ## -------------------------- ##
    ## testsuite.log was created. ##
    ## -------------------------- ##
    Please send `tests/testsuite.log' and all information you think might help:
    Subject: [openbsc] testsuite: 2 failed
    You may investigate any problem if you feel able to do so, in which
    case the test suite provides a good starting point. Its output may
    be found below `tests/testsuite.dir'.
    You can go to tests/testsuite.dir and have a look at the failing tests. For each failing test there will be one directory that contains a log file about the run and the output of the application. We are using GNU autotest in libosmocore, libosmo-abis, libosmo-sccp, OpenBSC, osmo-bts and cellmgr_ng.
  • Saturday, June 8, 2013 - 17:30
    Marcin "hrw" Juszkiewicz: ARMology

    When last time I was in Cambridge we had a discussion about ARM processors. Paweł used term “ARMology” then. And with recent announcement of Cortex-A12 cpu core I thought that it may be a good idea to write a blog post about it.

    Please note that my knowledge of ARM processors started in 2003 so I can make mistakes in everything older. Tried to understand articles about old times but sometimes they do not keep one version of story.

    Ancient times

    ARM1 got released in 1985 as CPU add-on to BBC Micro manufactured by Acorn Computers Ltd. as result of few years of research work. They wanted to have new processor to replace ageing 6502 used in BBC Micro and Acorn Electron and none of existing ones did not fit their requirements. Note that it was not market product but rather development tool made available for selected users.

    But it was ARM2 which landed in new computers — Acorn Archimedes (1987 year). Had multiply instructions added so new version of instruction set was created: ARMv2. Just 8MHz clock but remember that it was first computer with new CPU…

    Then ARM3 came — with cache controller integrated and 25MHz clock. ISA was bumped to ARMv2a due to SWP instruction added. And it was released in another Acorn computer: A5000. This was also used in Acorn A4 which was first ARM powered laptop (but term “ARM Powered” was created few years later). I hope that one day I will be able to play with all those old machines…

    There was also ARM250 processor with ARMv2a instruction set like in ARM3 but no cache controller. But it is worth mentioning as it can be seen as first SoC due to ARM, MEMC, VIDC, IOC chips integrated in one piece of silicon. This allowed to create budget versions of computers.

    ARM Ltd.

    In 1990 Acorn, Apple and VLSI co-founded Advanced RISC Machines Ltd. company which took over research and development of ARM processors. Their business model was simple: “we work on cpu cores and other companies pay us license costs to make chips”.

    Their first cpu was ARM60 with new instruction set: ARMv3. It had 32bit address space (compared to 26bit in older versions), was endian agnostic (so both big and little endian was possible) and there were other improvements.

    Please note lack of ARM4 and ARM5 processors. I heard some rumours about that but will not repeat them here as some of them just do not fit when compared against facts.

    ARM610 was powering Apple Newton PDA and first Acorn RiscPC machines where it was replaced by ARM710 (still ARMv3 instruction set but ~30% faster).

    First licensees

    You can create new processor cores but someone has to buy them and manufacture… In 1992 GEC Plessey and Sharp licensed ARM technology, next year added Cirrus Logic and Texas Instruments, then AKM (Asahi Kasei Microsystems) and Samsung joined in 1994 and then others…

    From that list I recognize only Cirrus Logic (used their crazy EP93xx family), TI and Samsung as vendors of processors ;D


    One of next cpu cores was ARM7TDMI (Thumb+Debug+Multiplier+ICE) which added new instruction set: Thumb.

    The Thumb instructions were not only to improve code density, but also to bring the power of the ARM into cheaper devices which may primarily only have a 16 bit datapath on the circuit board (for 32 bit paths are costlier). When in Thumb mode, the processor executes Thumb instructions. While most of these instructions directly map onto normal ARM instructions, the space saving is by reducing the number of options and possibilities available — for example, conditional execution is lost, only branches can be conditional. Fewer registers can be directly accessed in many instructions, etc. However, given all of this, good Thumb code can perform extremely well in a 16 bit world (as each instruction is a 16 bit entity and can be loaded directly).

    ARM7TDMI landed nearly everywhere – MP3 players, cell phones, microwaves and any place where microcontroller could be used. I heard that few years ago half of ARM Ltd. income was from license costs of this cpu core…


    But ARM7 did not ended at ARM7TDMI… There was ARM7EJ-S core which used ARMv5TE instruction set and also ARM720T and ARM740T with ARMv4T. You can run Linux on Cirrus Logic CLPS711x/EP721x/EP731x ones ;)

    According to ARM Ltd. page about ARM7 the ARM7 family is the world’s most widely used 32-bit embedded processor family, with more than 170 silicon licensees and over 10 Billion units shipped since its introduction in 1994.


    I heard that ARM8 is one of those things you should not ask ARM Ltd. people about. Nothing strange when you look at history…

    ARM810 processor made use of ARMv4 instruction set and had 72MHz clock. At same time DEC released StrongARM with 200MHz clock… 1996 was definitively year of StrongARM.

    In 2004 I bought my first Linux/ARM powered device: Sharp Zaurus SL-5500.


    Ah ARM9… this was huge family of processor cores…

    ARM moved from a von Neumann architecture (Princeton architecture) to a Harvard architecture with separate instruction and data buses (and caches), significantly increasing its potential speed.

    There were two different instruction sets used in this family: ARMv4T and ARMv5TE. Also some kind of Java support was added in the latter one but who knows how to use it — ARM keeps details of Jazelle behind doors which can be open only with huge amount of money.


    Here we have ARM9TDMI, ARM920T, ARM922T, ARM925T and ARM940T cores. I mostly saw 920T one in far too many chips.

    My collection includes:

    • ep93xx from Cirrus Logic (with their sick VFP unit)
    • omap1510 from Texas Instruments
    • s3c2410 from Samsung (note that some s3c2xxx processors are ARMv5T)


    Note: by ARMv5T I mean every cpu never mind which extensions it has built-in (Enhanced DSP, Jazelle etc).

    I consider this one to be most popular one (probably after ARM7TDMI). Countless companies had own processors based on those cores (mostly on ARM926EJ-S one). You can get them even in QFP form so hand soldering is possible. CPU frequency goes over 1GHz with Kirkwood cores from Marvell.

    In my collection I have:

    • at91sam9263 from Atmel
    • pxa255 from Intel
    • st88n15 from ST Microelectronics

    Had also at91sam9m10, Kirkwood based Sheevaplug and ixp425 based NSLU2 but they found new home.


    Another quiet moment in ARM history. ARM1020E, ARM1022E, ARM1026EJ-S cores existed but did not looked popular.

    UPDATE: Conexant uses ARM10 core in their next generation DSL CPE systems such as bridge/routers, wireless DSL routers and DSL VoIP IADs.


    Released in 2002 as four new cores: ARM1136J, ARM1156T2, ARM1176JZ and ARM11 MPCore. Several improvements over ARM9 family including optional VFP unit. New instruction set: ARMv6 (and ARMv6K extensions). There was also Thumb2 support in arm1156 core (but I do not know did someone made chips with it). arm1176 core got TrustZone support.

    I have:

    • omap2430 from Texas Instruments
    • i.mx35 from Freescale

    Currently most popular chip with this family is BCM2835 GPU which got arm1136 cpu core on die because there was some space left and none of Cortex-A processor core fit there.


    New family of processor cores was announced in 2004 with Cortex-M3 as first cpu. There are three branches:

    • Aplication
    • Realtime
    • Microcontroller

    All of them (with exception of Cortex-M0 which is ARMv6) use new instruction sets: ARMv7 and Thumb-2 (some from R/M lines are Thumb-2 only). Several cpu modules were announced (some with newer cores):

    • NEON for SIMD operations
    • VFP3 and VFP4
    • Jazelle RCT (aka ThumbEE).
    • LPAE for more then 4GB ram support (Cortex A7/12/15)
    • virtualization support (A7/12/15)
    • big.LITTLE
    • TrustZone

    I will not cover R/M lines as did not played with them.


    Announced in 2006 single core ARMv7a processor core. Released in chips by Texas Instruments, Samsung, Allwinner, Apple, Freescale, Rockchip and probably few others.

    Has higher clocks than ARM11 cores and achieves roughly twice the instructions executed per clock cycle due to dual-issue superscalar design.

    So far collected:

    • am3358 from Texas Instruments
    • i.mx515 from Freescale
    • omap3530 from Texas Instruments


    First multiple core design in Cortex family. Allows up to 4 cores in one processor. Announced in 2007. Looks like most of companies which had previous cores licensed also this one but there were also new vendors.

    There are also single core Cortex-A9 processors on a market.

    I have products based on omap4430 from Texas Instruments and Tegra3 from NVidia.


    Announced around the end of 2009 (I remember discussion about something new from ARM with someone at ELC/E). Up to 4 cores, mostly for use in all designs where ARM9 and ARM11 cores were used. In other words new low-end cpu with modern instruction set.


    The fastest (so far) core in ARMv7a part of Cortex family. Up to 4 cores. Announced in 2010 and expanded ARM line with several new things:

    • 40-bit LPAE which extends address range to 1TB (but 32-bit per process)
    • VFPv4
    • Hardware virtualization support
    • TrustZone security extensions

    I have Chromebook with Exynos5250 cpu and have to admit that it is best device for ARM software development. Fast, portable and hackable.


    Announced in 2011. Younger brother of Cortex-A15 design. Slower but eats much less power.


    Announced in 2013 as modern replacement for Cortex-A9 designs. Has everything from Cortex-A15/A7 and is ~40% faster than Cortex-A9 at same clock frequency. No chips on a market yet.


    That’s interesting part which was announced in 2011. It is not new core but combination of them. Vendor can mix Cortex-A7/12/15 cores to have kind of dual-multicore processor which runs different cores for different needs. For example normal operation on A7 to save energy but go up for A15 when more processing power is needed. And amount of cores in each of them does not even have to match.

    It is also possible to make use of all cores all together which may result in 8-core ARM processor scheduling tasks on different cpu cores.

    There are few implementations already: ARM TC2 testing platform, HiSilicon K3V3, Samsung Exynos 5 Octa and Renesas Mobile MP6530 were announced. They differ in amount of cores but all (except TC2) use the same amount of A7/A15 cores.


    In 2011 ARM announced new 64-bit architecture called AArch64. There will be two cores: Cortex-A53 and Cortex-A57 and big.LITTLE combination will be possible as well.

    Lot of things got changed here. VFP and NEON are parts of standard. Lot of work went into making sure that all designs will not be so fragmented like 32-bit architecture is.

    I worked on AArch64 bootstrapping in OpenEmbedded build system and did also porting of several applications.

    Hope to see hardware in 2014 with possibility to play with it to check how it will play compared to current systems.

    Other designs

    ARM Ltd. is not the only company which releases new cpu cores. That’s due to fact that there are few types of license you can buy. Most vendors just buy licence for existing core and make use of it in their designs. But some companies (Intel, Marvell, Qualcomm, Microsoft, Apple, Faraday and others) paid for ‘architectural license’ which allows to design own cores.


    Probably oldest one was StrongARM made by DEC, later sold to Intel where it was used as a base for XScale family with ARMv5TEJ instruction set. Later IWMMXT got added in PXA27x line.

    In 2006 Intel sold whole ARM line to Marvell which released newer processor lines and later moved to own designs.

    There were few lines in this family:

    • Application Processors (with the prefix PXA).
    • I/O Processors (with the prefix IOP)
    • Network Processors (with the prefix IXP)
    • Control Plane Processors (with the prefix IXC).
    • Consumer Electronics Processors (with the prefix CE).

    One day I will undust my Sharp Zaurus c760 just to check how recent kernels work on PXA255 ;D


    Their Feroceon/PJ1/PJ4 cores were independent ARMv5TE implementations. Feroceon was Marvell’s own ARM9 compatible CPU in Kirkwood and others, while PJ1 was based on that and replaced XScale in later PXA chips. PJ4 is the ARMv7 compatible version used in all modern Marvell designs, both the embedded and the PXA side.


    Company known mostly from wireless networks (GSM/CDMA/3G) released first ARM based processors in 2007. First ones were based on ARM11 core (ARMv6 instruction set) and in next year also ARMv7a were available. Their high-end designs (Scorpion and Krait) are similar to Cortex family but have different performance. Company also has Cortex-A5 and A7 in low-end products.

    Nexus 4 uses Snapdragon S4 Pro and I also have S4 Plus based Snapdragon development board.


    Faraday Technology Corporation released own processors which used ARMv4 instruction set (ARMv5TE in newer cores). They were FA510, FA526, FA626 for v4 and FA606TE, FA626TE, FMP626TE and FA726TE for v5te. Note that FMP626TE is dual core!

    They also have license for Cortex-A5 and A9 cores.

    Project Denver

    Quoting Wikipedia article about Project Denver:

    Project Denver is an ARM architecture CPU being designed by Nvidia, targeted at personal computers, servers, and supercomputers. The CPU package will include an Nvidia GPU on-chip.

    The existence of Project Denver was revealed at the 2011 Consumer Electronics Show. In a March 4, 2011 Q&A article CEO Jen-Hsun Huang revealed that Project Denver is a five year 64-bit ARM architecture CPU development on which hundreds of engineers had already worked for three and half years and which also has 32-bit ARM architecture backward compatibility.

    The Project Denver CPU may internally translate the ARM instructions to an internal instruction set, using firmware in the CPU.


    AppliedMicro announced that they will release AArch64 processors based on own cores.

    Final note

    If you spotted any mistakes please write in comments and I will do my best to fix them. If you have something interesting to add also please do a comment.

    I used several sources to collect data for this post. Wikipedia articles helped me with details about Acorn products and ARM listings. ARM infocenter provided other information. Dates were taken from Wikipedia or ARM Company Milestones page. Ancient times part based on The ARM Family and The history of the ARM CPU articles. The history of the ARM architecture was interesting and helpful as well.

    Please do not copy this article without providing author information. Took me quite long time to finish it.


    8 June evening

    Thanks to notes from Arnd Bergmann I did some changes:

    • added ARM7, Marvell, Faraday, Project Denver, X-Gene sections
    • fixed Cortex-A5 to be up to 4 cores instead of single.
    • mentioned Conexant in ARM10 section.
    • improved Qualcomm section to mention which cores are original ARM ones, which are modified.

    David Alan Gilbert mentioned that ARM1 was not freely available on a market. Added note about it.

    All rights reserved © Marcin Juszkiewicz
    ARMology was originally posted on Marcin Juszkiewicz website

  • Thursday, June 6, 2013 - 12:13
    SlyBlog: OpenPhoenux LinuxTag 2013 Impressions

    The LinuxTag 2013 is over, and I want to share some brief impressions I got during our stay in Berlin.

    The LinuxTag is a nice and well organized FOSS exhibition in Germany, attracting more than 10.000 visitors during 4 days.

    We gave a talk about the OpenPhoenux project at the 2nd evening and had about 60 listeners. Some of them got very interested and followed us to the booth afterwards. For everyone who couldn’t participate, the slides are available online: Slides.pdf

    We shared a booth with some other “Linux & Embedded” projects, namely: OpenEmbedded, Ethernut, Nut/OS, Oswald/Metawatch. Our Booth was professionally looking and I think we got quite some people interested in the project. Basically we had a constant flow of people at the booth during our 3 days stay and the overall feedback was rather positive!

    OpenPhoenux LinuxTag 2013 (1) OpenPhoenux LinuxTag 2013 (2) OpenPhoenux LinuxTag 2013 (3)

    We got interviewed by the “GNU funzt!” team, as well. The (german) video is now available on Youtube (OpenPhoenux interview is starting at 5:00):

    All in all it was a very nice stay in Berlin. I especially enjoyed meeting and chatting with guys who already owned a GTA04. It looks like the community is growing again!


  • Wednesday, June 5, 2013 - 04:00
    Harald "LaF0rge" Welte: Attending HITCON and COSCUP in Taipei

    It is my pleasure to attend the HITCON
    and COSCUP 2013
    conferences in July/August this year. They are both in Taipei. HITCON
    is a hacker/security event, while COSCUP is a pure Free/Open Source
    Software conference.

    At both events I will be speaking at the growing list of GSM related
    tools that are available these days, like OpenBSC, OsmcoomBB, SIMtrace,
    OsmoSGSN, OsmoBTS, OsmoSDR, etc. As they are both FOSS projects and
    useful in a security context, this fits well within the scope of both

    Given that I'm going to be back to Taiwan, I'm looking very much forward
    to meeting old friends and former colleagues from my Openmoko days in
    Taipei. God, do I miss those days. While terribly stressful, they
    still are the most exciting days of my career so far.

    And yes, I'm also going to use the opportunity for a continuation of my
    motorbike riding in this beautiful country.

  • Friday, May 31, 2013 - 10:16

    THSF 2013, C'est fini

    RE(Merci) A Toutes et Tous !!! A l'année prochaine !

    Partagez vos photos et vidéos en rajoutant un lien sur ce pad: pad.tetalab.org/p/thsf-2013-medias

    Venez prendre un verre jeudi 13 juin pour la sortie du numéro 26 du magazine Multiprise dans lequel un article est consacré au THSF.


    >>> Prochains RDV Tetalab : Tous les Mercredi Soir et le reste de la semaine !

    Qui ? Ouvert à tous le mercredi (apporter des bières ou autres goodies à partager) et aux membres le reste de la semaine. Inscriptions ouvertes, RTFM Tetalab : rtfm.tetalab.org.

    Quoi ? Au programme : 3D Print (initiation, discussions), Arduino & Servos, Oscillo, Processing, Firefox OS, LeapMotion, Eagle, Prism, PureData, Raspberry Pi, Le Bit et le Couteau, Retrogaming, OHM2013, La Novela, neutralité du net, Hadopi, Wikileaks, ...

    Pourquoi ? Pour apprendre, partager, se rencontrer, faire connaissance avec Tetaneutral.net, avancer sur des projets, ...

    Quand ? Tous les mercredi soirs à partir de 21h, et Samedi 15 Juin 2013 à partir de 10h.

    Comment ? Apportez vos milliards de neuronnes, un laptop, des croissants, un smile.

    Où ? Au container à Mix'Art Myrys , 12 rue Ferdinand Lassalle, 31200 Toulouse

  • Tuesday, April 23, 2013 - 20:34
    Compte-rendu de l'Hardware Freedom Day 2013

    Le samedi 20 avril 2013, nous avons reçu une cinquantaine de personnes à l'occasion du Premier HFDAY
    . De quoi faire une étincelle de plus en France au sujet de l'Open-Source Hardware (Matériel Libre).



    Un grand Merci à tous ceux qui sont venu ou ont soutenu la journée en relayant l'information. tTh, Philippe, Léon (le cyborg), EricDuino (merci pour les photos ci-dessous d'ailleurs), Seb pour la RepRap blanche, Mix'Art-Myrys pour l'espace et le soutien moral.

    P1020410RepRap-France.com est passé faire un tour. Merci pour les discussions sur les business-models et le futur de l'impression 3D. Franck à droite, à monté avec Guilhem (pas là) une des premières entreprises françaises basée sur les imprimantes "open hardware" REPRAP.

    Img 0131Img 0133bImg 0134

    Img 0135Img 0138Img 0140

    A l'année prochaine pour une deuxième édition bien mieux préparée ! =)

    -David Venancio / [340]metabaron

  • Wednesday, April 17, 2013 - 16:49
    Première Journée Internationale du Matériel Libre / Open-Source Hardware

    Hfd Banner2 Oshw Logo 200 Px

    A l'initiative de la Digital Freedom Foundation, 66 Hackerspaces organisent une journée portes-ouvertes le Samedi 20 Avril 2013 sur le Matériel Libre ou Open-Source Hardware, concept novateur qui ouvre à tous et toutes, la possibilité de construire librement ses propres outils.

    Le Tetalab soutenu par Mix'Art-Myrys présentera de 10h à 18h plusieurs imprimantes 3D RepRap, des vidéo projections et documents sur le sujet. Curieux en tous genres, passionnés d'Open-Source, bricoleurs et bricoleuses hi-tech, ou low-tech, vous êtes tous et toutes bienvenues.

    Hfd A4 Fr

    Hfd 470x60

  • Thursday, January 24, 2013 - 13:03
    THSF 2013 - Appel à Participation - Call For Participation
    ========== THSF 2013 ==========
    ======== Appel à Projet =======
    =========== Tetalab ===========
    Canal de discussion : #tetalab sur irc.freenode.net
    THEME : >>> Re(code) Re(art) Re(boot) Re(mix) Re(verse) <<<
    # À propos du THSF
    Depuis 2010, la Toulouse Hacker Space Factory est une rencontre annuelle autour de conférences et ateliers.
    L'objectif est de créer des rencontres entre hackers, makers, artistes et visiteurs curieux d'apprendre, tester ou tout simplement s'amuser avec la technologie.
    Ce mouvement initié au /tmp/lab à Paris se poursuit depuis 3 éditions à Toulouse
    C'est un événement ouvert et tout le monde est le bienvenu, sans barrière financière.
    Plus que la geekitude, on attend des esprits ouverts, des gens curieux, , le partage des savoirs et de la technologie. 
    # 17-24 Mai 2013 - Ateliers + Rencontre entre les participants + Barbecues.
    # 24-26 Mai 2013 - Ouverture au Public avec Ateliers + Conférences + Performances
    # Sujets
    RE(utilisation) de la technologie
    Minitel / Arduino / imprimante 3D
    Old goodies & Big Irons
    Matériel et Logiciel libre
    Neutralité du Net
    DIY (Faites-le vous même)
    Vidéo / Art numérique
    Soudure et planches à pain
    GSM Opensource
    Radio logicielle (SDR)
    Porcelaine, céramiques, émaux, l'union de la terre et du feu
    Pads collaboratifs
    Le Bit et le Couteau
    Radio en ligne
    Serveur Internet «collectivisé»
    Supercalculateurs Cray
    Ouverts à d'autres propositions
    # Proposer un projet
    Inscrivez-vous à la mailing-list THSF 2013 : http://lists.tetalab.org/listinfo/thsf-2013
    Soumission par mail: thsf-2013@lists.tetalab.org
    # Défraiement des artistes/conférenciers
    Hébergement à Toulouse,
    Remboursement du voyage dans la limite des possibles,
    Beaucoup de respect, de la bonne bouffe et du data love 
    # Deadline
    Nous devons préparer un dossier pour la fin du mois de janvier, vous aurez plus de chance d'être retenu si vous proposez votre projet avant cette date.
    *** Informations Générales conférences:
    * Nom ou pseudo
    * Votre nom ou votre pseudo (IRC/Jabber/...)
    * Démo [Oui/Non]
    * Nombre de lignes de code écrites dans votre projet ?
    * Besoin d'aide pour votre visa? [Oui/Non]
    * Résumé
    * Biographie
    * Email
    * nick IRC sur freenode
    * Adresse
    * Site internet
    * Téléphone
    * Nom de l'entreprise ou Indépendant ?
    * Besoins additionnels: Internet ? Autre ?
    *** Format Conférence:
    * Titre de la présentation
    * Résumé
    Veuillez choisir le format de votre conférence:
    [ ] Standard (30min+10min Q&Réponses)
    [ ] Long (80min+10min Q&Réponses)
    *** Pièces jointes:
    Précisez si votre conférence nécessite :
    * Outils     [Oui/Non]
    * Slides   [Oui/Non]
    *** Format Artistique: performance / concert / ...
    * Dossier décrivant la démarche artistique (Inclure vidéo ou photos représentatives du travail)
    * Type d'intervention
    * Veuillez fournir votre fiche technique en pièce jointe

    ========== THSF 2013 ==========
    === Call For Participations ===
    =========== Tetalab ===========
    THEME >>> Re(code) Re(art) Re(boot) Re(mix) Re(verse) <<<
    # About THSF
    Toulouse Hacker Space Factory is an annual meeting started in 2010 around conferences and workshops.
    The goal is to create encounters between hackers, makers and curious people in order to learn, test or simply have fun with technologies.
    /tmp/lab in Paris initiated the movement and we wanted to bring such an event to southern France.
    It is an open event and everyone is welcome without financial barrier.
    More than leetness we expect open minds, sharing, technology for nothing, technology for something.
    # When
    # 17-24 May 2013 - Workshops and meetings between participants
    # 24-26 May 2013 - Public event with Workshops + Confs + Exhibits
    # Topics
    RE(use) of Technology
    Minitel / Arduino / 3D Printing 
    Oldies but goodies
    Open Hardware and Open Source Software
    Network Neutrality by doing it
    Internet Media Politics
    Video / Numeric Art
    Opensource GSM
    Collaborative edition
    Le Bit et le Couteau
    Online radio
    Open to other propositions
    # Submitting Content
    Subscribe to THSF 2013 mailing-list: http://lists.tetalab.org/listinfo/thsf-2013
    Submit you content by mail: thsf-2013@lists.tetalab.org
    # Speaker benefits:
    Accommodation in Toulouse,
    travel reimbursement,
    Much respect and love.
    # Deadline
    We'll have to prepare 'something' for the end of january, so you'll have more chance to be included if you submit your content before this date.
                  [ CFP ANSWER TEMPLATE ]
    *** General information:
    * Speakers name or alias (IRC/Jabber/...)
    * Demo [Y/N]
    * Number of lines of code written during your project ?
    * I need help with visas [Y/N]
    * Presentation Title
    * Abstract
    * Biography
    * Email
    * Website
    * Address
    * Phone
    * Company (name) or Independent?
    * additional requirements: Internet? Others?
    *** Talk Format:
    Please chose your talk format:
    [ ] Standard (30min+10min Q&A)
    [ ] Extended (80min+10min Q&A)
    *** Attachments:
    Specify if your submission contains any of the following information:
    * Tool     [Y/N]
    * Slides   [Y/N]
    *** Art performance, concert format :
    * Artistical intention abstract (video, picture, texte or website)
    * Type of performance / concert
    * Technical requirements
  • Thursday, January 17, 2013 - 14:19
    Petit POV : update 2

    Apres quelques remarques, j'ai effectué 4 modifications dans le sketch du montage petit POV

    1.  1 Correction des boucles for qui, à cause d'une erreur, affichait a la fin des message un point ou un caractère bizarre !!! (cf photo ci dessous)
    2. 2 Utilisation de Progmem http://arduino.cc/en/Reference/PROGMEM
        afin d'économiser de la RAM et de faciliter un futur portage sur ATTINY85.... à suivre !!
    3. 3 Utilisation d'un fichier font7x5.h pour facilité la lecture du code (et en plus le détail de la police une fois que c'est bon, on s'en fout un peu....)
    4. 4 Utilisation de for pour les init et alloff histoire de faire un peu plus small...

    Voici la nouvelle version Pov05.zip

    En bonus le code est passé de 4120 bytes à 2838 bytes. Voila qui va aider pour le futur portage sur ATTINY !!!

    Voila... A plus

  • Wednesday, January 9, 2013 - 13:26
    Le Bit et le Couteau : Compilation 2012

    Tous les génériques et les sons de 2012 du Bit et du Couteau, l'émission du Tetalab sur Canal Sud le premier mercredi du mois à 13h sont disponible sur:


    Bonne écoute!

  • Tuesday, January 8, 2013 - 13:47
    Librairie IR NEC pour ATTINY85

    1 Introduction

    Le but de cette adaptation est de pouvoir utiliser la librairie IR sur des Attiny85.
    La base de cette librairie est le fruit du travail de Ken Shirriff  (http://www.arcfn.com/2009/08/multi-protocol-infrared-remote-library.html)
    Un portage a été fait par Nick Gammon sur le forum Arduino (http://arduino.cc/forum/index.php?topic=91488.msg687101#msg687101) . Il a fait la partie la plus difficile c'est-à-dire adapter la lib de Ken Shirriff en fonction des caractéristiques des ATTINY. En effet, il y a de nombreuses différences entre ATMEGA et ATTINY comme les timers et d’autres trucs encore auxquels je ne comprends pas grand-chose. Quoi qu’il en soit la librairie adapté est disponible ici http://gammon.com.au/Arduino/IRremote_Attiny.zip

    Le problème de ce portage c’est que la librairie en l’état est « difficile » à utiliser. En effet, dans l’exemple donnée par Nick Gammon, il est impossible d’utiliser un « digital.write » c’est trop consommateur de mémoire… C’est dire si cela va être difficile de faire quelque chose de simple…

    J’ai donc décidé de ne pas me prendre la tête et de faire un grand ménage pour libérer des ressources sur les ATTINY.
    2 axes de nettoyages :
    1 – Séparation en deux librairies une pour l’émission et l’autre pour la réception
    2 – Gestion du protocole NEC uniquement
    Voila la marche à suivre pour installer et utiliser la (les) librairie(s) pour Attiny85

    2 Matériel utilisé

    3 Préparation

    3-1 Installation des libraires IRTinyTR et IRTinyRX

    En premier lieu télécharger la librairie modifié ici

    Cette librairie s’installe dans le répertoire « libraries » du sketchbook arduino comme toutes les autres lib.
    A la racine du répertoire « libraries » il doit y avoir donc deux répertoires : IRTinyTX et IRTinyRX

    2 Install Lib

    Dans la capture d’écran ci-dessus le skectchbook s’appelle « ardval »

    3-2 Ajouter les Attiny dans les hardware supporté par l’IDE arduino

    Pour ce faire, rien de plus simple il suffit de telecharger le fichier arduino-tiny-0100-0015.zip ici =>  http://code.google.com/p/arduino-tiny/downloads/list

    Ensuite localiser le repertoire hardware de votre sketchbook et dezipper le contenu de l’archive
    3 Install Lib

    4 Install Lib

    Ça doit ressembler à ça. (pour que cela fonctionne, il faut redémarrer l’IDE Arduino)

    3-3 Uploder le code arduinoAsIsp dans un Arduino (Duemilanove dans mon cas)

    5 Arduinoas Isp

    Sélection bonne board et bon programmateur

    6 Arduinoas Isp

    7 Arduinoas Isp

    Utiliser l’Arduino avec le sketch Arduino as ISP pour programmer un ATTINYPour la partie hardware, je vous renvoie sur le site du MIT qui décrit très bien cette partie : http://hlt.media.mit.edu/?p=1695

    Par contre n’utilisez pas ATtiny zip (from this GitHub repository https://github.com/damellis/attiny/archive/master.zip)

    3-4 Modifier le bootolader de l’ATTINY

    Une fois le hardware décrit plus haut en place, il suffit de sélectionner la board ATtiny85 @ 8 Mhz (internal oscillator ; BOD disabled) et le programmer Arduino as ISP. Cette manip est nécessaire, la lib ne fonctionnant qu’a une fréquence d’horloge de 8 Mhz

    9 Burnbootloader

    10 Burnbootloader

    Enfin faire un « Burn Bootloader » (c’est assez rapide en général)

    11 Burnbootloader

    4 - Montage pour les deux sktechs de demo

    4 - 1 montage basique : sketch SimpleIRTinyTX.ino et SimpleIRTinyRX.ino

    Partie TX

    Ce montage est composé donc de

    • 1 ATTINY 85 (@ 8 Mhz)
    • 1 LED IR (BL-L513-IR)
    • 1 bouton poussoir avec sa résistance de pull up
    • Une pile
    • Un switch (ON/OFF)

    13 Simple Tx

    Partie RX

    Ce montage est composé donc de

    • 1 ATTINY 85 (@ 8 Mhz)
    • 1 récepteur IR TSOP341
    • 1 led basique avec une resistance
    • Une pile
    • Un switch (ON/OFF)

    12 Simple Rx

    Le fonctionnement des deux montages est simple : Si on appuie sur le outon de la partie TX, la led s’allume sinon elle s’éteint…

    NEC IR with Attiny 85 from phil teta on Vimeo.

    4-2 montage avancé : sketch FourLedsIRTinyRX.ino et AnalogIRtinyTX.ino

    Partie TX

    • 1 ATTINY 85 (@ 8 Mhz)
    • 1 LED IR (BL-L513-IR)
    • 1 bouton poussoir avec sa résistance de pull up
    • 1 potar 40 kohms (valeur sans importance du moment que c’est supérieur à 10 k…)
    • Une pile
    • Un switch (ON/OFF)

    14 Tx

    Parie RX

    • 1 ATTINY 85 (@ 8 Mhz)
    • 1 récepteur IR TSOP341
    • 4 leds basiques avec résistance
    • Une pile
    • Un switch (ON/OFF)

    15 Rx

    Le fonctionnement de ces montages est le suivant

    En fonction de la position du potar, un code IR est émis. Il y a 8 codes : tout éteint, Led 1 on, Led1 + Led2 on, Led2 on, Led2 + led3 on, Led3 on, Led 3 + Led 4 on, Led4 on.
    Si on appuis sur le bouton poussoir, un code IR est transmis pour allumer toutes les leds…

    NEC IR with Attiny 85 (2) from phil teta on Vimeo.

  • Thursday, November 22, 2012 - 12:08
    Prototypage rapide sur Android avec Processing

    En m'intéressant au prototypage rapide d'application sur android, et j'ai trouvé une solution simple avec Processing (ça a l'air assez simple en Java aussi).


    Sur Mac, avec la device Android pluggée en USB et le mode USB debug activé:

    1. Télécharger la dernière version de Processing (2.0b6) : http://processing.org/download/
    2. 2. Télécharger le SDK Android et le placer dans /Applications
    3. 3. Exécuter /Applications/android-sdk-macosx/tools/android et installer: Tools, Android 4.2 (API 17), Android 2.3.3 (API 10)
    4. 4. Lancer Processing
    5. 5. Sélection "Android" dans Processing, disponible en haut à droite dela fenêtre en appuyant sur "Java"
    6. 6. Une nouvelle fenêtre s'ouvre, charger un example (dispo dans le menu "File")
    7. 7. Dans le menu "Sketch", compiler et exécuter l'app en choisissant "Run on Device"

    Hier, les exemples (Particle, compass, ...) ont fonctionné de suite sans aucune modification.

    Le wiki est rempli de bonne info - http://wiki.processing.org/w/Android - et une large contribution a été apportée par la librairie Ketai: https://code.google.com/p/ketai/

    Un bouquin est aussi dispo sur PragProg, avec une introduction à Ketai et 20 projets basés dessus: http://pragprog.com/book/dsproc/rapid-android-development

  • Thursday, November 22, 2012 - 08:30
    Lavage de LED en famille

    Résumé de la soirée du 21/11/2012 au Tetalab.

    Que se passe t'il quand des geek rencontrent une machine à laver? Il y mettent des led dedans...



    Des leds dans une machine à laver - lavage from rataflo on Vimeo.


    Des leds dans une machine à laver - vidange from rataflo on Vimeo.

    Essorage :

    Des leds dans une machine à laver - rincage from rataflo on Vimeo.

    Et après y'en a qui s'embêtent à monter des systèmes de POV de la mort qui tue alors qu'il n'y as besoin que d'une machine à laver.

    La POV (Persistence Of Vision ou Persistance retinienne) permet de faire ce genre de choses :

  • Wednesday, November 14, 2012 - 22:41
    Le tetalab n'est pas mort

    Hé oui nous consommons encore des biéres le mercredi à partir de 21h à Mixart Myrys.

    Que c'est il passé depuis Mars:

    THSF :


    Construction d'un dôme géodésique.

    Émission radiophonique mensuelle "Le bit et le couteau". Toutes les émissions sont dispo la.

    Novela avec Add it :

    On a rangé le container!! Nous pouvons nous asseoir.

    On a cassé l'Ultimaker.

    Festival du film Grolandais avec install Minitel.


    On a plein de raspberry pi. Brice allume des led avec.

    Thierry retrouve les joies du TRS80

  • Friday, October 19, 2012 - 00:00
    Packages debian/ubuntu for Rivendell 2.2.0

    Rivendell 2.2.0

    Les paquets de Rivendell 2.2.0 pour Debian and Ubuntu sont maintenant disponibles sur le dépôt Debian Tryphon pour :

    • Debian : squeeze/stable, wheezy/testing, sid/unstable
    • Ubuntu : lucid/10.04(LTS), natty/11.04, oneiric/11.10 et precise/12.04(LTS)

    Les plateformes i386 et amd64 sont, comme toujours, supportées.

    Support de Wheezy & Sid

    La librairie Qt3 n’étant plus supportée officiellement par Debian, nous fournissons maintenant les packages Qt3 pour wheezy et sid [en].

    Rivendell est donc maintenant à nouveau disponible sur Debian wheezy (la future version stable) et sid.


    RdAirPlay a besoin d’un fichier fourni par le paquet libqt3-headers. Ce paquet est maintenant suggéré et non requis, car il installe énormément de dépendences.


    Vous pouvez obtenir un Rivendell fonctionnel en quelques minutes :

    Etape 1 : Ajoutez le dépôt Debian Tryphon à vos sources Debian/Ubuntu

    Etape 2 : Installez un serveur MySQL : sudo apt-get install mysql-server

    Etape 3 : Installez à la fois Rivendell “server” et “station” : sudo apt-get install rivendell-server rivendell

    Etape 4 : Ajoutez l’utilisateur qui doit utiliser Rivendell dans le groupe du même nom. Par exemple, pour vous ajouter vous-même : sudo adduser $USER rivendell

    Au passage, vérifiez que le même utilisateur est indiqué dans /etc/rd.conf à la ligne AudioOwner. Si vous utilisez sudo pour l’installation, cela sera le cas. Cette information sera bientôt (à nouveau) paramétrable à l’installation.

    Etape 5 : Quittez et relancez votre session (Gnome, KDE, etc …) pour prendre en compte le nouveau groupe et les permissions données au groupe rivendell lors de l’installation

    Etape 6 : Lancez rdadmin qui va créer la base en vous demandant le login de l’administrateur MySQL (root) et le mot de passe (choisi pendant l’installation de mysql-server).

    Etape 7 : Lancez rdairplay et le cart Test et appréciez


    Comme l’ensemble des projets Tryphon, les sources de ces paquets sont accessibles sur http://projects.tryphon.eu/projects/rivendell2-debian.

    Le wiki du projet donne quelques indications pour reconstruire les paquets.

  • Sunday, August 19, 2012 - 00:00
    Formation Rivendell à Rennes


    En partenariat avec Radio Campus Rennes, nous organisons du 20 au 23 août 2012 une formation au logiciel de gestion d’antenne Rivendell.

    Découvrir Rivendell

    La première demi-journée est l’occasion de présenter à toutes et tous l’ensemble des possibilités offertes par la suite logicielle Rivendell.

    Cette présentation/démonstration/discussion a donc lieu le lundi 20 août à 14h à Radio Campus Rennes. Comptez deux bonnes heures pour faire le tour de Rivendell et en discuter.

    Cet après-midi est ouvert à toutes et tous. Mais, par politesse pour nos hôtes et pour être sûr que tout le monde trouve une place, contactez l’équipe de Tryphon ou celle de Campus Rennes si vous êtes intéressés.


    Tous nos supports de formation sont publiés sous licence libre Creative Commons by-nc-sa 3.0 :

  • Tuesday, July 10, 2012 - 00:00
    RivendellBoxes en production

    Pour les auditeurs de Radio Grésivaudan le 29 juin dernier marquait le passage à la grille d’été. Pour l’équipe de la radio, c’était aussi le passage à un nouveau système de gestion d’antenne : Rivendell.

    RivendellAirBox dans le studio principal de Radio Grésivaudan

    Le besoin d’une solution clé-en-main pour Rivendell

    En novembre dernier, le congrès de la CNRA s’est ouvert par une scéance plénière consacrée à l’utilisation des logiciels libres. Tout le monde (ou presque) s’accordait sur l’intérêt des logiciels libres dans un monde de la radio de plus en plus informatisé et en réseau. Mais le constat était aussi qu’il est difficile de réunir les compétences en interne pour mettre en place des outils libres en production, en particulier pour des systèmes “complexes” comme Rivendell.

    Fort de notre expérience dans la mise en oeuvre de solutions libres clé-en-main, nous avons donc concentré nos efforts sur la mise au point d’une solution dédiée à Rivendell. Après un hiver productif, nous avons pu proposer au printemps à Radio Grésivaudan d’expérimenter une nouvelle gamme de Boxes Tryphon : les RivendellBoxes.

    L’équipe de Radio Grésivaudan avait repéré Rivendell depuis plusieurs années. En janvier 2011, ils organisaient une présentation de Rivendell aux radios environnantes. En juillet de la même année, ils participaient à la formation Rivendell donnée sur les hauteurs de Milau chez Radio Larzac.

    Comme beaucoup de radios, Radio Grésivaudan devait remplacer un système de diffusion vieillisant, dont l’usure du matériel devenait une menace.

    Les premières RivendellBoxes sont donc deployées en mars 2012 à Crolles. Les Boxes ont été prises en main rapidement par l’équipe. Grâce à leur retour, une (unique) mise à jour a été réalisée pour apporter les quelques modifications nécessaires.

    4500 sons plus tard (remplissant prêt d’un demi tera-octet), tout était prêt le 29 juin pour gérer entièrement l’antenne grâce à Rivendell.


    Pour l’équipe de Tryphon, Rivendell est une vieille connaissance. Nous l’utilisons depuis 2004 dans le cadre des radios éphèmeres d’Autres(M)Ondes.

    Depuis sa création, notre société nous permet de continuer nos contributions au profit de la communauté des utilisateurs du logiciel, notamment en mettant à disposition les paquets facilitant l’installation sous Debian et Ubuntu ou en hébergeant le wiki de Rivendell.

    Mais la communauté francophone est maintenant aussi un soutien de choix. La liste de discussion rivendell-fr est un lien d’échange qui permet à tous de tirer le meilleur de Rivendell.


    Rivendell fonctionne en réseau. Plusieurs stations peuvent être réparties dans la radio : dans les studios pour la diffusion ou la production, dans les bureaux pour l’administration.

    Les RivendellBoxes s’utilisent donc en réseau :

    • une RivendellNasBox qui assure le stockage sécurisé des sons et des données,
    • autant de RivendellAirBoxes que nécessaire pour utiliser les applications de Rivendell aux différents endroits de la radio
    • un réseau gigabit pour relier l’ensemble

    RivendellAirBox dans le studio principal de Radio Campus Montpellier

    Un modèle particulier RivendellAllBox propose en une seule Box un système Rivendell complet, permettant par exemple une utilisation mobile.

    Comme nos autres Boxes, les RivendellBoxes sont utilisables dès l’allumage. Mais Rivendell est un logiciel complet qui nécessite une phase de prise en main.

    Pour faciliter celle-ci nous proposons des formations (communément sur 3 jours), ainsi qu’une assistance de 2 jours à la mise en route de Rivendell dans votre radio.

    Rivendell, à qui le tour ?

    Vendredi dernier, c’était au tour de l’équipe de Radio Campus Montpellier. Le mois d’août prochain verra encore trois autres mises en production.

    A noter que les lecteurs de la Lettre Pro de la Radio ont pu lire une présentation de Rivendell dans le numéro 21.

    La prochaine session de formation a lieu à Rennes du 20 au 23 aout. Elle sera l’occasion d’une présentation de Rivendell le 20 août à 14h ouverte à toutes et tous (dans la mesure des places disponibles). Contactez-nous pour y assister.

    Et comme les logiciels libres ne seraient rien sans leurs utilisateurs, les radios qui suivent ont fait le choix de Rivendell, demandez leur avis : Radio Grille Ouverte, Hit Radio Namur, RUN, Radio Campus Amiens, DivergenceFM, Radio Larzac, Radio MDM, Radio PAC, Graf’Hit, Radio Grésivaudan, Radio Fil de l’Eau, Radio Campus Montpellier, Radio Campus Rennes, …

    Et vous ?