linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Cc: Atul Sabharwal <iamatul@comcast.net>
Subject: Re: u-boot debugging
Date: Mon, 23 Jan 2006 10:32:37 +0100	[thread overview]
Message-ID: <200601231032.38295.david.jander@protonic.nl> (raw)
In-Reply-To: <005301c61e54$aadb1b10$02c0650a@ATULSPC>

On Saturday 21 January 2006 07:34, Atul Sabharwal wrote:
> You have a conflict of interest as you are just pissed with Metrowerks
> as they are your competitors.  Open source is about free speech and
> not for people with vested interests.  You seem to be one of the guys
> with vested interest.

Everybody has their interests. Even OSS programmers have interests, if not 
always of economical nature. I don't think Mr. Denk has any more reasons to 
"be pissed" with Metrowerks than you might have reasons to "be pissed" with 
DENX or Abatron.

> You cannot repress people and tell them *oxymorons* or ninkampoops...
> If you do the cost benefit analysis between BDI and Metrowerks debugger,
> its the same.  And their UI is better than ddd and works with a BDI also.
> So, if you consider all aspects, its a better product.

That is a very subjective observation. Here is a slightly more objective one 
for you: BDI can use almost any UI that supports gdb, and there are quite a 
lot. Not only DDD. Does Metrowerks offer you that amount of choice?

> And opensource is used all over the globe including the Asian subcontinent.
> And there are still sites which use hubs as people dont have the excess
> money
> to throw away on legacy products.  Just sitting in your small cube does not
> give
> insight to global technology trends...

Well, I suppose using a 10Mbps switch shouldn't cost much more than a 100Mbps 
hub, and you almost said it yourself, that it would be more efficient in a 
crowded network ;-)
What I really wonder is what the choice between a switch and a hub has to do 
with "global technology trends".
I detect an increasing amount of resentment in your words, and that is not 
good as far as my experience goes.

Greetings,

-- 
David Jander

  reply	other threads:[~2006-01-23  9:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 17:56 u-boot debugging atul.sabharwal
2006-01-20 19:46 ` Wolfgang Denk
2006-01-21  6:34   ` Atul Sabharwal
2006-01-23  9:32     ` David Jander [this message]
2006-01-23 13:44       ` Atul Sabharwal
2006-01-23 22:32       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-01-23 18:42 sri.dharmasanam
2006-01-23  7:48 Paula Saameño
2006-01-22 10:10 Albert David
2006-01-23 14:10 ` Atul Sabharwal
     [not found] <mailman.3.1137805202.13229.linuxppc-embedded@ozlabs.org>
2006-01-21 14:20 ` Glenn Burkhardt
2006-01-22  8:28   ` Frank
2006-01-20 21:13 atul.sabharwal
2006-01-23  9:25 ` Alexandre BASTOS
2006-01-20 18:13 atul.sabharwal
2006-01-20 18:06 atul.sabharwal
2006-01-20 19:48 ` Wolfgang Denk
2006-01-20 20:40   ` bennett78
2006-01-20 18:00 atul.sabharwal
2006-01-20  6:51 Mustafa Çayır
2006-01-20 13:40 ` Wolfgang Denk

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=200601231032.38295.david.jander@protonic.nl \
    --to=david.jander@protonic.nl \
    --cc=iamatul@comcast.net \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).