From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: dm3730
Date: Mon, 21 Nov 2011 17:06:56 +0000 [thread overview]
Message-ID: <2451003.Qx4lekPWFq@helios> (raw)
In-Reply-To: <jae01t$scs$1@dough.gmane.org>
On Monday 21 November 2011 17:59:41 Koen Kooi wrote:
> Op 21-11-11 17:47, Paul Eggleton schreef:
> > On Monday 21 November 2011 17:10:30 Koen Kooi wrote:
> >> Worse, if you follow the offical yocto instructions you'll get only
> >> broken and/or incomplete beagleboard support.
> >
> > Rather than vague assertions perhaps you would care to elaborate on
> > what's broken and/or incomplete about our beagleboard support?
>
> I hope the irony of yocto people asking other people what their own layers
> actually support isn't lost on the people involved.
There's no irony at all. I personally am not an expert on the beagleboard.
Given that you *are* however, perhaps you might have simply said - as you
point out, in the context of this discussion - that the Yocto project doesn't
include DSP support for the beagleboard? That would have been enough. Almost
stating that it's "broken" is going too far, in my opinion.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-21 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 8:06 dm3730 Raffaele Recalcati
2011-11-19 11:51 ` dm3730 Kridner, Jason
2011-11-19 18:31 ` dm3730 Raffaele Recalcati
2011-11-21 15:38 ` dm3730 Raffaele Recalcati
2011-11-21 16:10 ` dm3730 Koen Kooi
2011-11-21 16:47 ` dm3730 Paul Eggleton
2011-11-21 16:56 ` dm3730 Koen Kooi
2011-11-21 16:59 ` dm3730 Koen Kooi
2011-11-21 17:06 ` Paul Eggleton [this message]
2011-11-21 17:42 ` dm3730 Peter Bigot
2011-11-22 7:52 ` dm3730 Raffaele Recalcati
2011-11-22 17:28 ` dm3730 Raffaele Recalcati
2011-11-21 16:30 ` dm3730 Eric Bénard
2011-11-19 11:54 ` dm3730 Enrico
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=2451003.Qx4lekPWFq@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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 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.