From: "Steve DeLaney" <onramp123@yahoo.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: mpc8xxx_gpio.c on mpc8349e-mitx
Date: Sat, 20 Dec 2008 09:40:01 -0800 [thread overview]
Message-ID: <02dd01c962c9$fc4d1b30$6b03a8c0@sdelaney2> (raw)
We are currently working on LTIB toolchain, and are upgrading a GPIO driver
on MPC8349E-MITX platform.
This has taken us to the latest kernel 2.6.27.10
we ran across a patch on ozlabs patchwork that looks like it should
work for us, and we thank you first of all for the contribution.
The topic here pertains to how various distros are related
Sorry for this basic question but it will help us better understand
the best path for our development.
in ozlabs patchwork Sep 21 08 is what appears to be the original
implementation of GPIO support.
In the denx git there is arch/powerpc/sysdev/mpc8xxx_gpio.c, so it looks
like the ozlabs GPIO support made it into the denx distro.
mpc8xxx_gpio.c is not present in the kernel.org 2.6.27.10 distro.
But is is likely that mpc8xxx_gpio.c will eventually go upstream to
kernel.org?
Just also curious what are the primary powerpc contributions, such as
denx, freescale, others??
Thanks,
/steverino2
next reply other threads:[~2008-12-20 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 17:40 Steve DeLaney [this message]
2008-12-22 9:02 ` mpc8xxx_gpio.c on mpc8349e-mitx Peter Korsgaard
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='02dd01c962c9$fc4d1b30$6b03a8c0@sdelaney2' \
--to=onramp123@yahoo.com \
--cc=linuxppc-embedded@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 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).