All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33
Date: Tue, 20 Aug 2013 13:44:14 -0400	[thread overview]
Message-ID: <20130820174413.GF8481@edge> (raw)
In-Reply-To: <4044911E-C108-4FC2-8B32-6992C7AC06AD@ti.com>

On Tue, Aug 20, 2013 at 01:38:28PM -0400, Cooper Jr., Franklin wrote:
> 
> 
> On Aug 20, 2013, at 12:21 PM, "Dmytriyenko, Denys" <denys@ti.com> wrote:
> 
> > On Tue, Aug 20, 2013 at 12:54:11PM -0400, Cooper Jr., Franklin wrote:
> >> 
> >> 
> >>> -----Original Message-----
> >>> From: Dmytriyenko, Denys
> >>> Sent: Tuesday, August 20, 2013 11:24 AM
> >>> To: Cooper Jr., Franklin
> >>> Cc: meta-arago@arago-project.org
> >>> Subject: Re: [meta-arago] [master & danny][PATCH 1/7] linux-libc-headers: Add
> >>> linux-libc-headers version 2.6.33
> >>> 
> >>> On Mon, Aug 19, 2013 at 10:30:20PM -0400, Cooper Jr., Franklin wrote:
> >>>> 
> >>>> 
> >>>> On Aug 19, 2013, at 4:36 PM, "Dmytriyenko, Denys" <denys@ti.com> wrote:
> >>>> 
> >>>>> On Wed, Jul 31, 2013 at 07:31:46PM -0500, Franklin S. Cooper Jr wrote:
> >>>>>> * This is the version that was originally being using in
> >>>>>> arago/oe-classic based  SDK.
> >>>>> 
> >>>>> Why do we need 2.6.33? All our old kernels are at least 2.6.37 now
> >>>>> and there is corresponding linux-libc-headers available...
> >>> 
> >>>> It's been awhile but I believe am18x still didn't like the 2.6.37
> >>>> headers for some crazy reason.
> >>> 
> >>> Do you have any more details? I'm testing it right now and it seems to be
> >>> building fine so far against 2.6.37.2...
> >> 
> >> [Franklin] I believe it's a runtime issue with tslib. The am18 kernel 
> >> conflicted with the 2.6.33 version of linux-libc-headers that was used to 
> >> build tslib.
> > 
> > But otherwise libnl-3.2.21 doesn't seem to build against 2.6.33 headers...
> > 
> I need to submit patches to enable wilink 6 for am18 and am37 anyway by 
> adding older versions of various recipes which would fix this problem.

Ok, then, let's leave 2.6.33 headers out until that time - I'll pick the other 
4 patches from this series today. Thanks.

-- 
Denys


      reply	other threads:[~2013-08-20 17:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  0:31 [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33 Franklin S. Cooper Jr
2013-08-01  0:31 ` [master & danny][PATCH 2/7] arago.conf: Set machines to use " Franklin S. Cooper Jr
2013-08-01  0:31 ` [master & danny][PATCH 3/7] branding-amsdk: Set linux-libc-headers to 3.2 Franklin S. Cooper Jr
2013-08-19 21:37   ` Denys Dmytriyenko
2013-08-01  0:31 ` [master & danny][PATCH 4/7] arago-perfs.inc: Set linux-libc-header version to 3.2 for beagleboard Franklin S. Cooper Jr
2013-08-01  0:31 ` [master & danny][PATCH 5/7] arago.conf: Separate work directories by linux-libc-headers version Franklin S. Cooper Jr
2013-08-01  0:31 ` [master & danny][PATCH 6/7] toolchain-external-linaro: Use separate linux-libc-headers provider Franklin S. Cooper Jr
2013-08-19 21:41   ` Denys Dmytriyenko
2013-08-01  0:31 ` [master & danny][PATCH 7/7] meta-toolchain-arago: Add in linux-libc-headers version to variable Franklin S. Cooper Jr
2013-08-19 21:36 ` [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33 Denys Dmytriyenko
2013-08-20  2:30   ` Cooper Jr., Franklin
2013-08-20 16:23     ` Denys Dmytriyenko
2013-08-20 16:54       ` Cooper Jr., Franklin
2013-08-20 17:21         ` Denys Dmytriyenko
2013-08-20 17:38           ` Cooper Jr., Franklin
2013-08-20 17:44             ` Denys Dmytriyenko [this message]

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=20130820174413.GF8481@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.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.