public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: Igor Stoppa <igor.stoppa@nokia.com>,
	me@felipebalbi.com,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: omap24xx is broken in current head
Date: Wed, 10 Sep 2008 16:40:53 -0700	[thread overview]
Message-ID: <20080910234053.GQ21163@atomide.com> (raw)
In-Reply-To: <20080811152944.GP25784@atomide.com>

* Tony Lindgren <tony@atomide.com> [080811 08:32]:
> * Koen Kooi <k.kooi@student.utwente.nl> [080811 18:00]:
> >
> > Op 11 aug 2008, om 16:50 heeft Tony Lindgren het volgende geschreven:
> >
> >> * Igor Stoppa <igor.stoppa@nokia.com> [080810 20:39]:
> >>> On Sun, 2008-08-10 at 14:37 +0200, ext Koen Kooi wrote:
> >>>
> >>>> "Broken as hell" if you want to do anything NEON related with it.
> >>>
> >>> yup
> >>> Very unlucky but very true.
> >>>> I
> >>>> use 2007q3 with the -Os fix for compiling omap3 kernels
> >>>
> >>> Felipe: that's also what we should use internally, since it's the  
> >>> only
> >>> one approved by our system performance team.
> >>
> >> I'll revert this patch for now to avoid adding a compiler dependency
> >> as we already have a pile of other issues to solve.
> >
> > Speaking of compiler dependencies, how about applying my patch that  
> > enable vanilla gcc to compile the kernel? Russel (or Erik) seems to be  
> > fond of rejecting my mails to the LAKML list, so I can't post it there. A 
> > copy of it can be found here:
> >
> > http://ewi546.ewi.utwente.nl/git/?p=openembedded.git;a=blob;f=packages/linux/linux-omap2-git/beagleboard/no-harry-potter.diff;h=2bb20ab9c025312fcf0434de5bcb88aeceb4f87f;hb=HEAD
> 
> That seems like a good patch, you should see what the issue is with
> posting to LAKML. Maybe add it to Russell's patch system meanwhile? :)
> 
> Meanwhile, yeah I'd say if that works on more compilers, let's add it
> to l-o tree.

I still don't see this patch anywhere.. Koen, what's your mail problem
with LAKML? Maybe Russell can help with this issue?

Anyways, I'll apply this to l-o tree. Seems like the dash is the right
naming according to this:

http://sourceware.org/ml/binutils/2006-12/msg00149.html

Tony


> 
> Tony
> 
> 
> > regards,
> >
> > Koen
> >
> >>
> >>
> >> Let's plan on re-applying this patch once the other issues are out of
> >> the way.
> >>
> >> Tony
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-omap" 
> >> in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>
> >
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-09-10 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 11:58 omap24xx is broken in current head Felipe Balbi
2008-08-10 12:16 ` Felipe Balbi
2008-08-10 12:31   ` Dirk Behme
2008-08-10 12:37   ` Koen Kooi
2008-08-10 17:22     ` Igor Stoppa
2008-08-11 14:50       ` Tony Lindgren
2008-08-11 14:59         ` Felipe Balbi
2008-08-11 14:59         ` Koen Kooi
2008-08-11 15:29           ` Tony Lindgren
2008-09-10 23:40             ` Tony Lindgren [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=20080910234053.GQ21163@atomide.com \
    --to=tony@atomide.com \
    --cc=igor.stoppa@nokia.com \
    --cc=k.kooi@student.utwente.nl \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    /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