All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Vandenabeele <peter.vandenabeele@mind.be>
To: David Ho <DavidHo@nanometrics.ca>
Cc: Marius Groeger <mgroeger@sysgo.com>,
	linuxppc-embedded@lists.linuxppc.org,
	Marc Leeman <marc.leeman@barco.com>,
	samlinuxppc@yahoo.com.cn, Patrick Huesmann <tricknology@gmx.de>
Subject: Re: How to port ppc-linux to new custom boards? (virtexII)
Date: Wed, 25 Aug 2004 16:30:25 +0200	[thread overview]
Message-ID: <20040825143025.GJ23113@mind.be> (raw)
In-Reply-To: <OF545365DC.C126C7D8-ON85256EFB.004B2B8D-85256EFB.004C42EB@nanometrics.ca>


On Wed, Aug 25, 2004 at 09:52:58AM -0400, David Ho wrote:
> > > Finally, do not overestimate the commercial support, to my experience;
> > > the collaborative mailing lists are often as good if not better to point
> > > you in the correct direction due to the diverse expertises of the ppl on
> > > the list.

I would be very careful with generalisation ...

> > Correct.
> >
> > I'd like to add, though, that commercial support is somthing you payed for,
> > and which you can *claim*, so IMHO you shouldn't underestimate it. A
> > guaranteed support line can be very critical at certain stages of your
> > project.
>
> Sorry to stick my nose in your discussion, but I have a strong opinion on
> commerial support.  Working in a small company, we have never gotten the
> level of commitment we would expect from companies like ISI (vendor of
> pSOS) and Timesys.  You can get the basic installation support fine.  But
> when you need to get into the nitty gritty detail their value is a lot less
> compared to mailing lists.

Would the base problem not be that the classic model of "1-year support for a
fixed fee" creates a false illusion ? How can you expect a support company to
get into intensive research of a complex problem if this just creates additional
cost, but no additional revenue ? For a big customer, that is paying hefty
yearly fees, it is obvious to do this investment, but for a small customer ...

> The way I see it is being large commercial OS vendor that they are, they
> seem to funnel their resource to the big customers who are willing to pay
> the big bucks to get stuff done.

Seems very logical. Those who pay extra for extra work, will get extra
work delivered. Those who rely on the 1-year support for a fixed fee
will get what remains. IMHO this is best resolved with just charging
hourly: you pay for what you actually got ...

> When choosing commercial support, one critical factor is their customer
> base.  Big fish don't go after the tiny ticks in the sea, they go for
> seals.  And you really have to find the right sized OS vender to give you
> the attention you need.

I have seen a number of "small" support companies deliver excellent
support to e.g. large semiconductor companies.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-25 14:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  6:27 How to port ppc-linux to new custom boards? (virtexII) Patrick Huesmann
2004-08-24  7:25 ` Marc Leeman
2004-08-25  7:34   ` Marius Groeger
2004-08-25  7:57     ` Marc Leeman
2004-08-25 13:52     ` David Ho
2004-08-25 14:30       ` Peter Vandenabeele [this message]
2004-08-25 20:08         ` Handling of cascaded interrupt controllers Jeff Domogala
2004-08-26  7:02         ` How to port ppc-linux to new custom boards? (virtexII) Marc Leeman
2004-08-24  8:01 ` Oliver Fuchs
2004-08-24  8:31 ` Peter Ryser
     [not found] <31481.1093602240@www36.gmx.net>
2004-08-27 11:18 ` Patrick Huesmann
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 15:17 Patrick Huesmann
2004-08-24  1:30 ` Song Sam
2004-08-24  4:14 ` Peter Ryser
2004-08-24  8:51 ` Peter 'p2' De Schrijver
2004-08-24  9:14   ` Patrick Huesmann
2004-08-24  9:42     ` Peter 'p2' De Schrijver
2004-08-24 10:01     ` Song Sam
2004-08-25  2:00   ` Song Sam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040825143025.GJ23113@mind.be \
    --to=peter.vandenabeele@mind.be \
    --cc=DavidHo@nanometrics.ca \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=marc.leeman@barco.com \
    --cc=mgroeger@sysgo.com \
    --cc=samlinuxppc@yahoo.com.cn \
    --cc=tricknology@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.