From: David Brown <davidb@codeaurora.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: David Brown <davidb@codeaurora.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support
Date: Fri, 2 Dec 2011 07:26:09 -0800 [thread overview]
Message-ID: <20111202152609.GA6986@huya.qualcomm.com> (raw)
In-Reply-To: <201112021417.17082.GNUtoo@no-log.org>
On Fri, Dec 02, 2011 at 02:17:17PM +0100, Denis 'GNUtoo' Carikli wrote:
> >And I've learned what I needed to now: someone does still care about
> >the target.
> However in a response to the following mail:
> [Question] RPC and SMD implementation
> David Brown already told that:
> >Is there much reason to get the msm72xx support into the kernel in the
> >first place? These targets are old, and I don't believe any new
> >devices are being made using them
> And:
> >Things are a lot easier in the newer RPC/SMD versions,
> >and I don't see a strong reason to keep the kruft in the kernel
> >necessary to support the 72xx chips.
> I guess that means that RPC for msm7x00 won't hit mainline.
> So without RPC the port to mainline cannot be complete(no modem, no audio, no
> GPS,and maybe more depending on the device).
There isn't anything stopping someone from working on the port. The
Android kernels for the target are still available. But, I think most
people working on the MSM code will be focusing on newer devices,
especially now that there is an 8660 dev board available.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: msm: Remove MSM7x00 support
Date: Fri, 2 Dec 2011 07:26:09 -0800 [thread overview]
Message-ID: <20111202152609.GA6986@huya.qualcomm.com> (raw)
In-Reply-To: <201112021417.17082.GNUtoo@no-log.org>
On Fri, Dec 02, 2011 at 02:17:17PM +0100, Denis 'GNUtoo' Carikli wrote:
> >And I've learned what I needed to now: someone does still care about
> >the target.
> However in a response to the following mail:
> [Question] RPC and SMD implementation
> David Brown already told that:
> >Is there much reason to get the msm72xx support into the kernel in the
> >first place? These targets are old, and I don't believe any new
> >devices are being made using them
> And:
> >Things are a lot easier in the newer RPC/SMD versions,
> >and I don't see a strong reason to keep the kruft in the kernel
> >necessary to support the 72xx chips.
> I guess that means that RPC for msm7x00 won't hit mainline.
> So without RPC the port to mainline cannot be complete(no modem, no audio, no
> GPS,and maybe more depending on the device).
There isn't anything stopping someone from working on the port. The
Android kernels for the target are still available. But, I think most
people working on the MSM code will be focusing on newer devices,
especially now that there is an 8660 dev board available.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-12-02 15:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 0:29 [PATCH 1/3] ARM: msm: Remove MSM7x00 support David Brown
2011-12-01 0:29 ` David Brown
2011-12-01 0:29 ` [PATCH 2/3] gpio_msm: remove support for MSM7x01 David Brown
2011-12-01 0:29 ` David Brown
2011-12-01 0:29 ` [PATCH 3/3] ARM: msm: Remove cpu_is test for msm7201 soc David Brown
2011-12-01 0:29 ` David Brown
2011-12-01 15:17 ` [PATCH 1/3] ARM: msm: Remove MSM7x00 support Daniel Walker
2011-12-01 15:17 ` Daniel Walker
2011-12-01 15:17 ` Daniel Walker
2011-12-01 18:17 ` David Brown
2011-12-01 18:17 ` David Brown
2011-12-01 18:39 ` Daniel Walker
2011-12-01 18:39 ` Daniel Walker
2011-12-01 19:27 ` David Brown
2011-12-01 19:27 ` David Brown
2011-12-01 19:33 ` Daniel Walker
2011-12-01 19:33 ` Daniel Walker
2011-12-01 19:43 ` David Brown
2011-12-01 19:43 ` David Brown
2011-12-01 19:53 ` Daniel Walker
2011-12-01 19:53 ` Daniel Walker
2011-12-01 20:17 ` David Brown
2011-12-01 20:17 ` David Brown
2011-12-01 20:19 ` Russell King - ARM Linux
2011-12-01 20:19 ` Russell King - ARM Linux
2011-12-01 20:25 ` Daniel Walker
2011-12-01 20:25 ` Daniel Walker
2011-12-01 20:35 ` Russell King - ARM Linux
2011-12-01 20:35 ` Russell King - ARM Linux
2011-12-01 20:49 ` Daniel Walker
2011-12-01 20:49 ` Daniel Walker
2011-12-01 21:03 ` Russell King - ARM Linux
2011-12-01 21:03 ` Russell King - ARM Linux
2011-12-01 21:34 ` Daniel Walker
2011-12-01 21:34 ` Daniel Walker
2011-12-01 20:26 ` David Brown
2011-12-01 20:26 ` David Brown
2011-12-01 20:32 ` Daniel Walker
2011-12-01 20:32 ` Daniel Walker
2011-12-02 13:17 ` Denis 'GNUtoo' Carikli
2011-12-02 13:17 ` Denis 'GNUtoo' Carikli
2011-12-02 15:26 ` David Brown [this message]
2011-12-02 15:26 ` David Brown
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=20111202152609.GA6986@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=GNUtoo@no-log.org \
--cc=bryanh@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.