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: Wed, 03 Jan 2007 20:58:12 +1100 [thread overview]
Message-ID: <1167818293.6165.143.camel@localhost.localdomain> (raw)
In-Reply-To: <20070103080151.214ebb62@mlejnas.priv.castalie.org>
On Wed, 2007-01-03 at 08:01 +0100, Simon Vallet wrote:
> On Wed, 03 Jan 2007 07:41:26 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > BTW. What is this evil^H^H^H^Hbinary driver you are talking about ?
>
> Yes, blobs are evil, but a binary driver is still better than no driver
> at all...
>
> I'm working on the unicorn driver for the BeWan ADSL PCI card -- the
> card manufacturer does not seem willing to provide the relevant info
> (I'm not really aware of the specifics -- Sven Luther will probably
> know more about this). Besides, much of the functionality of the card
> is implemented in software, so a 100% open-source driver would probably
> require a lot of work.
>
> Last but not least I wanted to dig a bit into binary formats anyway ;-)
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 ?
Ben.
next prev parent reply other threads:[~2007-01-03 9:59 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 [this message]
2007-01-03 10:32 ` Simon Vallet
2007-01-03 20:36 ` Benjamin Herrenschmidt
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=1167818293.6165.143.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 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.