From: "Mark Chambers" <markc@mail.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: U-Boot and kernel 2.6
Date: Fri, 11 Jun 2004 19:18:46 -0400 [thread overview]
Message-ID: <015901c4500a$735d0eb0$0301a8c0@chuck2> (raw)
In-Reply-To: 40CA25B8.8050809@mvista.com
I have seen many references to OCP. How does one find out what it is?
Mark Chambers
----- Original Message -----
From: "Mark A. Greer" <mgreer@mvista.com>
> Here are some thoughts that don't directly address the bi_rec (or
> whatever) issue but they are related...
>
> Some things have changed since that thread. In particular, the "On Chip
> Peripheral" or OCP support has been added to the kernel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-11 23:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 6:45 U-Boot and kernel 2.6 Meriin Michael-BMM063
2004-06-11 10:36 ` David Woodhouse
2004-06-11 11:03 ` Pantelis Antoniou
2004-06-11 11:20 ` David Woodhouse
2004-06-11 13:03 ` Wolfgang Denk
2004-06-11 13:23 ` Pantelis Antoniou
2004-06-11 14:09 ` Wolfgang Denk
[not found] ` <40C9BED6.3010809@intracom.gr>
2004-06-11 14:34 ` David Woodhouse
2004-06-11 15:11 ` Wolfgang Denk
2004-06-11 17:17 ` Greg Goodwin
2004-06-11 15:31 ` Mark Chambers
2004-06-11 16:22 ` Wolfgang Denk
2004-06-11 16:48 ` Kenneth Johansson
2004-06-11 14:43 ` Wolfgang Denk
2004-06-11 21:35 ` Mark A. Greer
2004-06-11 23:18 ` Mark Chambers [this message]
2004-06-11 23:27 ` Mark A. Greer
2004-06-12 2:12 ` Kumar Gala
2004-06-11 16:48 ` Tom Rini
[not found] ` <0F48024310E5D6118D200002B3A440DB08B07A3D@zil01exm08.mcil.comm.mot.com >
2004-06-11 19:27 ` Ricardo DIz
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 17:47 Ricardo DIz
2006-08-01 5:12 ` Dmitry Chichkov
2006-08-01 7:10 ` Wolfgang Denk
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='015901c4500a$735d0eb0$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
/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.