linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: leeyang <leeyang77@hotmail.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: [trini@kernel.crashing.org: [PATCH] Allow openpic_init to set all combos of polarity and sense]
Date: Mon, 29 Apr 2002 21:04:45 -0700	[thread overview]
Message-ID: <20020430040445.GC21482@opus.bloom.county> (raw)
In-Reply-To: <3CCE1653.7050709@embeddededge.com>


On Mon, Apr 29, 2002 at 11:58:11PM -0400, Dan Malek wrote:
> Tom Rini wrote:
>
> >Note, Sandpoint is probably currently broken in linuxppc_2_4_devel since
> >I believe it relied on overloading NumInitSenses .....
>
> I thought Paulus finally took this hack and implemented it in a way
> that made him happy. :-)  Was I mistaken?  Several of us checked this
> in over and over, it really shouldn't be removed unless there is
> something better.

Right.  The hack is gone, and now we have openpic_set_sources().  If a
board relied on the hack, it's quite probably non-functional right now
(the lopec didn't get _anywhere_, but that might have been due to always
having a bogus polarity & whatnot).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-04-30  4:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30  0:34 [trini@kernel.crashing.org: [PATCH] Allow openpic_init to set all combos of polarity and sense] Tom Rini
     [not found] ` <OE120wZDyDG742l3ew100002f33@hotmail.com>
     [not found]   ` <20020430033341.GB21482@opus.bloom.county>
2002-04-30  3:58     ` Dan Malek
2002-04-30  4:04       ` Tom Rini [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=20020430040445.GC21482@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=leeyang77@hotmail.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).