From: Peter Korsgaard <jacmet@sunsite•dk>
To: onramp123@yahoo•com
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: mpc8xxx_gpio.c on mpc8349e-mitx
Date: Mon, 22 Dec 2008 10:02:33 +0100 [thread overview]
Message-ID: <87d4fkbn12.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <02dd01c962c9$fc4d1b30$6b03a8c0@sdelaney2> (Steve DeLaney's message of "Sat\, 20 Dec 2008 09\:40\:01 -0800")
>>>>> "Steve" == Steve DeLaney <onramp123@yahoo•com> writes:
Hi,
Steve> We are currently working on LTIB toolchain, and are upgrading
Steve> a GPIO driver on MPC8349E-MITX platform.
Steve> This has taken us to the latest kernel 2.6.27.10
Steve> we ran across a patch on ozlabs patchwork that looks like it should
Steve> work for us, and we thank you first of all for the contribution.
You're welcome.
Steve> The topic here pertains to how various distros are related
Steve> Sorry for this basic question but it will help us better understand
Steve> the best path for our development.
Steve> in ozlabs patchwork Sep 21 08 is what appears to be the original
Steve> implementation of GPIO support.
Steve> In the denx git there is arch/powerpc/sysdev/mpc8xxx_gpio.c, so it looks
Steve> like the ozlabs GPIO support made it into the denx distro.
More importantly, it's included in the mainline kernel.org kernel
since 2.6.28-rc1
Steve> mpc8xxx_gpio.c is not present in the kernel.org 2.6.27.10 distro.
Steve> But is is likely that mpc8xxx_gpio.c will eventually go upstream to
Steve> kernel.org?
It is. 2.6.28 is scheduled to release any moment now.
Steve> Just also curious what are the primary powerpc contributions,
Steve> such as denx, freescale, others??
It's basically all over the map. I wrote the gpio driver and I'm not
involved with any of those.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2008-12-22 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 17:40 mpc8xxx_gpio.c on mpc8349e-mitx Steve DeLaney
2008-12-22 9:02 ` Peter Korsgaard [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=87d4fkbn12.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite$(echo .)dk \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=onramp123@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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