From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Jason McMullan <jason.mcmullan@gmail.com>
Cc: "Anton Wöllert" <a.woellert@gmail.com>,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc8xx and ld.so problem
Date: Fri, 1 Jul 2005 11:42:23 -0300 [thread overview]
Message-ID: <20050701144223.GB11975@logos.cnet> (raw)
In-Reply-To: <1120244191.18872.3.camel@jmcmullan.timesys>
On Fri, Jul 01, 2005 at 02:56:30PM -0400, Jason McMullan wrote:
> On Fri, 2005-07-01 at 07:17 -0300, Marcelo Tosatti wrote:
> > That was a quick response - thanks.
> >
> > Two questions:
> >
> > - Do you happen to know about details of dcbz's (mis)behaviour on 8xx?
> >
> > I ask that mainly because I worry about in-kernel dcbz users.
>
> IIRC, it isn't used in any 8xx code paths.
OK!
> > - Shouldnt upstream glibc have that fixed for 8xx by now?
>
> Ha. Funny. The glibc powerpc maintainer doesn't want any embedded
> fixes in the mainline.
Who is that?
> Last I checked, that was for 'the tools vendors' to fix.
Silly - so embedded developers are supposed rely on "embedded vendors"
and not on the mainstream software distributions?
> "We won't work around processor bugs" is their philosophy.
>
> I went through a similar (unsuccessful) battle with the
> amcc 440ep's "blrl" errata and gcc/glibc.
>
> It would be nice if the politics there have changed
> (maybe they just didn't like me personally), but I don't have
> much hope.
If enough people complain they will, hopefully, listen.
next prev parent reply other threads:[~2005-07-01 19:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42C1AAC1.4060702@gmail.com>
[not found] ` <20050629085913.GA2153@logos.cnet>
[not found] ` <faba7798050630071347d4ad63@mail.gmail.com>
2005-07-01 9:44 ` mpc8xx and ld.so problem Marcelo Tosatti
2005-07-01 14:55 ` Jason McMullan
2005-07-01 10:17 ` Marcelo Tosatti
2005-07-01 18:56 ` Jason McMullan
2005-07-01 14:42 ` Marcelo Tosatti [this message]
2005-07-04 8:22 ` Yuli Barcohen
2005-07-05 19:53 ` Tom Rini
2005-07-06 8:58 ` Yuli Barcohen
2005-07-08 0:36 ` Marcelo Tosatti
2005-07-10 7:31 ` Yuli Barcohen
2005-07-13 15:41 ` Theo Gjaltema
2005-07-13 20:32 ` Wolfgang Denk
2005-07-13 21:32 ` Theo Gjaltema
2005-07-13 23:11 ` Wolfgang Denk
2005-07-14 5:44 ` Anton Wöllert
2005-07-14 8:23 ` ptrace on linux 2.6.12 causes oops Anton Wöllert
2005-07-14 13:31 ` Kumar Gala
2005-07-14 11:20 ` Marcelo Tosatti
[not found] ` <faba77980507140809ad923db@mail.gmail.com>
2005-07-14 15:11 ` Anton Wöllert
2005-07-14 20:27 ` aris
2005-07-14 11:19 ` Marcelo Tosatti
2005-07-15 9:42 ` Anton Wöllert
2005-07-15 5:03 ` Marcelo Tosatti
2005-07-03 16:01 ` mpc8xx and ld.so problem Anton Wöllert
2005-07-01 18:40 Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2005-07-14 13:32 Joakim Tjernlund
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=20050701144223.GB11975@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=a.woellert@gmail.com \
--cc=jason.mcmullan@gmail.com \
--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 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.