linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Adrian Bunk <bunk@kernel.org>,
	Stefan Roese <sr@denx.de>,
	paulus@samba.org
Subject: Re: platforms/44x/warp-nand.c bogosity
Date: Fri, 1 Aug 2008 11:59:01 -0400	[thread overview]
Message-ID: <20080801115901.082491ba@lappy.seanm.ca> (raw)
In-Reply-To: <20080801112628.35fb0ff2@zod.rchland.ibm.com>

On Fri, 1 Aug 2008 11:26:28 -0400
"Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:

> I don't believe it is intentional, no.  Sean can you look at this and
> see what's up?  I have a couple of fixes to queue up from you already
> and if you can get this one done in the next few days I'll included it
> as well.

So I went back in the archives. Somebody else, Thomas Gleixner I
believe, was already working on the ndfc port. So, since I *had* to
have a working ndfc, I put a local copy in my kernel and forgot about
it.

It looks like Thomas has dropped the port. I should probably resubmit
the patch with the arch/ppc code removed. However, I don't think this
would be for 2.6.27 timeframe since there will probably be discussion.
For one, my patch just gets it working... the warp-nand.c file shows
that it is not a complete solution ;) Second, there are some byte order
issues.

So could we just leave warp-nand.c "there but disabled" for now?

Cheers,
   Sean

  parent reply	other threads:[~2008-08-01 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 15:14 platforms/44x/warp-nand.c bogosity Adrian Bunk
2008-08-01 15:26 ` Josh Boyer
2008-08-01 15:32   ` Valentine Barshak
2008-08-02  3:42     ` Sean MacLennan
2008-08-01 15:59   ` Sean MacLennan [this message]
2008-08-01 15:41 ` Sean MacLennan

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=20080801115901.082491ba@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=bunk@kernel.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sr@denx.de \
    /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).