From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Simon Vallet <linux-ppc@castalie.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: R_PPC_ADDR16_HI relocs in PPC modules ?
Date: Thu, 04 Jan 2007 07:36:43 +1100 [thread overview]
Message-ID: <1167856603.6165.145.camel@localhost.localdomain> (raw)
In-Reply-To: <20070103113238.0d99b015.linux-ppc@castalie.org>
On Wed, 2007-01-03 at 11:32 +0100, Simon Vallet wrote:
> On Wed, 03 Jan 2007 20:58:12 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > Doh ! I've been in "contact" with that driver in a previous life... it's
> > a whole bunch of horrid C++ with windows wrappers all over... or did
> > they improve it ? It's still an ST chip ?
>
> Well -- obviously I can't tell much about the source ;-), but it
> certainly looks like C++ to me. The last version of the driver is some
> years old, actually, so it probably hasn't changed much since you were
> "in contact" with it -- and yes, as far as I know the card still uses an
> ST chipset.
>
> Since you're somewhat familiar with this driver, do you
> think the ELF translation approach is a viable one ?
No idea.
Ben.
next prev parent reply other threads:[~2007-01-03 20:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 16:25 R_PPC_ADDR16_HI relocs in PPC modules ? Simon Vallet
2007-01-02 17:16 ` Segher Boessenkool
2007-01-02 18:09 ` Simon Vallet
2007-01-02 20:48 ` Segher Boessenkool
2007-01-03 0:47 ` Paul Mackerras
2007-01-03 1:20 ` Segher Boessenkool
2007-01-02 20:41 ` Benjamin Herrenschmidt
2007-01-03 7:01 ` Simon Vallet
2007-01-03 9:58 ` Benjamin Herrenschmidt
2007-01-03 10:32 ` Simon Vallet
2007-01-03 20:36 ` Benjamin Herrenschmidt [this message]
2007-01-02 21:31 ` Alan Modra
2007-01-03 6:49 ` [PATCH] Add support for R_PPC_ADDR16_HI relocations Simon Vallet
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=1167856603.6165.145.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-ppc@castalie.org \
--cc=linuxppc-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).