From: "Imre Kaloz" <kaloz@openwrt.org>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>,
"David Goodenough" <david.goodenough@btconnect.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Can the OpenRB board descriptions be merged into the mainline kernel?
Date: Tue, 16 Mar 2010 22:58:00 +0100 [thread overview]
Message-ID: <op.u9okmyyw2s3iss@ecaz> (raw)
In-Reply-To: <20100316143903.GK8963@zod.rchland.ibm.com>
On Tue, 16 Mar 2010 15:39:03 +0100, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> On Tue, Mar 16, 2010 at 12:23:19PM +0000, David Goodenough wrote:
>> OpenWRT has some fixes which adds the board descriptions for the OpenRB
>> (ppc504 based boards). Is there any reason why these should not be
>
> ppc504? I've not heard of that one. Is that a typo for 405?
Typo.
>> merged into the mainline kernel? The fixes are all licences GPL2.
>>
>> If not do you want the original authors to submit them, or shall I take the
>> OpenWRT specific bits out and post them here?
>
> What exactly do you mean by "board description"?
These are part of the patches I've told you about over IRC. The port uses the
ppc40x_simple stuff with cuImage wrapper. It also has a CF connector, so
that driver needs to be merged, too..
I'll submit everything when I'm a bit better.. Spent the last two weeks in bed :/
Imre
next prev parent reply other threads:[~2010-03-16 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 12:23 Can the OpenRB board descriptions be merged into the mainline kernel? David Goodenough
2010-03-16 14:39 ` Josh Boyer
2010-03-16 21:58 ` Imre Kaloz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 22:49 David Goodenough
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=op.u9okmyyw2s3iss@ecaz \
--to=kaloz@openwrt.org \
--cc=david.goodenough@btconnect.com \
--cc=jwboyer@linux.vnet.ibm.com \
--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.