Gentoo Archives: gentoo-embedded

From: wireless <wireless@×××××××××××.com>
To: gentoo-embedded@l.g.o
Subject: Re: [gentoo-embedded] Wind River Linux experience
Date: Wed, 23 Mar 2011 14:03:25
Message-Id: 4D89FA82.5090002@tampabay.rr.com
In Reply to: [gentoo-embedded] Wind River Linux experience by Kfir Lavi
1 On 03/23/11 05:46, Kfir Lavi wrote:
2
3 > I'm trying to migrate a big company to Gentoo.
4 > This company have a contract with Wind River for support and use.
5 > I don't have any experience with Wind River, so I would be happy to
6 > hear your experience with it, and what it's pros and cons.
7
8 > Regards,
9 > Kfir
10
11 All by yourself? That's a LARGE statement.
12
13 Wind River is the 600 lb Gorilla in the commercial
14 RTOS space. Everything from proprietary, to BSDish to embedded
15 Linux, state machines...... you name it they sell
16 (and mostly) support it.
17
18
19 Large companies use Wind River, because of many reasons,
20 but it is a "one stop shop" and Business managers
21 like that. Wind River can write (and often do) the
22 entire code for products or products lines, fast and
23 efficient. However, their "Achilles heal" is
24 they are EXPENSIVE to partner with; most often retaining
25 the intellectual property rights to all of the codes they
26 develop or sell.
27
28 Their business model is the "lock-in" and often, after years
29 of a relationship with a company, the victim (um, I mean customer)
30 finds out that WR is licensing the code to a competitor.....
31 Bad ju-ju, but legal and happens all the time.
32
33
34 So you are talking about helping a company take the "long road" to
35 freedom and profitability, via embedded Linux (Gentoo specifically).
36
37 Depending on the complexity of the of their codes, number of products,
38 etc, etc, you can easily be successful. However, be realistic. Pick
39 off the "low hanging fruit"; i.e. simple products to re-write the code
40 or new product offerings. WR will often get companies in a "tangled"
41 mess by the choices of processors, SOC, video chips etc etc where
42 NDAs and no published specifications make WR the only choice, or a
43 complete (hardware and software) redesign.
44
45 My advice:
46 Work smart, build a team (open source) that gradually assimilates
47 new products and the other easy "knock-off" and take your time.
48 Walking into a large company and pitching "kick WR out" is difficult
49 in many circumstances. Most of all, remember that in this company their
50 are managers that drink and eat and "sup" with WR and they have built
51 a career on a partnership with WR. They'll stab you in the back and
52 you'll never see it coming.
53
54 Also remember companies want to make a profit. So their management will
55 need "some sort of angle" as to what they have unique about their
56 product so other cannot just copy the code and sell it. When you
57 maintain proprietary source code, that is the lock for a company,
58 combined with patents. When you pitch open source solutions, you
59 and the company manager, must figure out a "unique" hook so as to
60 protect that company's investment and profit potential of the product
61 that is now open sources. YMMV.
62
63
64
65 Caveat Emptor!
66
67 But it is entirely doable depending on the "TEAM" you build as the
68 leader of this venture.
69
70 GOOD LUCK!
71 James

Replies

Subject Author
Re: [gentoo-embedded] Wind River Linux experience Kfir Lavi <lavi.kfir@×××××.com>