From: Denys Dmytriyenko <denis@denix.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto + meta-networking
Date: Tue, 23 Jul 2013 11:49:29 -0400 [thread overview]
Message-ID: <20130723154929.GD21440@denix.org> (raw)
In-Reply-To: <1443099.tO82y7b3tx@helios>
On Wed, Jul 17, 2013 at 02:03:41PM +0100, Paul Eggleton wrote:
> On Wednesday 17 July 2013 08:56:34 Brian Hutchinson wrote:
> > Thanks Paul, I worried about mixing branches since I've never tried that
> > before. The only reason I picked Denzil is because I need ti816x support
> > and Dylan and Danny don't have machine confs for it in meta-ti. So what
> > would be easier, getting the machine support I need in Dylan or back
> > porting the net-snmp recipe to Denzil?
>
> I don't have a feel for the former - if the reason is not already clear you'd
> probably want to ask the meta-ti folks why that machine isn't supported in
> later branches and how hard it would be to update support. This might be worth
Just to update everyone on this list - the issue with ti81x has been discussed
on meta-ti list multiple times before and Brian already knew the answer to that.
> doing if you're starting something new with denzil, since that's two versions
> behind current stable.
>
> Having said that, backporting the net-snmp recipe should be fairly trivial
> though.
--
Denys
next prev parent reply other threads:[~2013-07-23 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 21:06 Yocto + meta-networking Brian Hutchinson
2013-07-16 21:19 ` Saul Wold
2013-07-16 21:47 ` Brian Hutchinson
2013-07-16 21:28 ` Paul Eggleton
2013-07-17 12:56 ` Brian Hutchinson
2013-07-17 13:03 ` Paul Eggleton
2013-07-17 13:12 ` Brian Hutchinson
2013-07-23 15:49 ` Denys Dmytriyenko [this message]
2013-07-23 14:36 ` Brian Hutchinson
2013-07-23 14:58 ` Paul Eggleton
2013-07-23 15:07 ` Brian Hutchinson
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=20130723154929.GD21440@denix.org \
--to=denis@denix.org \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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.