From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c
Date: Mon, 17 Jun 2013 01:27:24 -0700 [thread overview]
Message-ID: <20130617082724.GI20992@atomide.com> (raw)
In-Reply-To: <CACVXFVMthQNgAe3QhMo8HUxuEYcFSOwsdb7RfAsFqwGFKL+dXA@mail.gmail.com>
* Ming Lei <tom.leiming@gmail.com> [130617 01:22]:
> On Mon, Jun 17, 2013 at 4:06 PM, Arnaud Patard
> <arnaud.patard@rtp-net.org> wrote:
> > Sricharan R <r.sricharan@ti.com> writes:
> >
> > I hoped to have missed some mails and that people were testing pandabard
> > support with full support but given what I see, the ethernet support is
> > not there yet. This thread is about removing the non-DT boot. I see some
> > contradiction here. Please, look again at what Thomas said in the IGEP thread:
> > breaking existing support is bad and removing non-DT boot for panda with
> > not-working ethernet would exactly to that.
>
> +1
>
> Even no any USB support on Sricharan's setting.
That's also related to the auxclk. Let's see what Mike says before
we start adding back any legacy hacks for it.
> > Yeah, I'm aware that some extra patches are being developped like the
> > omap clocks one: https://patchwork.kernel.org/patch/2541331/ but they
> > don't seem to be in -next. So, again, please, wait that all needed bits
> > are merged mainline before killing non-DT support (or provide 'mixed'
> > support like what is/was done on kirkwood)
>
> Agree, please don't be too quick, :-)
Too quick? The basic DT based booting has been working for a few years
now to some extent on omaps :)
Regards,
Tony
next prev parent reply other threads:[~2013-06-17 8:27 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 19:17 [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tony Lindgren
2013-05-17 19:17 ` [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Tony Lindgren
2013-05-20 9:54 ` Russell King - ARM Linux
2013-05-20 17:10 ` Tony Lindgren
2013-07-06 13:10 ` Russell King - ARM Linux
2013-07-06 13:36 ` Russell King - ARM Linux
2013-07-08 9:34 ` Tony Lindgren
2013-07-08 14:21 ` Russell King - ARM Linux
2013-07-09 8:23 ` Tony Lindgren
2013-07-12 9:09 ` Peter Ujfalusi
2013-07-22 9:40 ` Tomi Valkeinen
2013-10-27 13:26 ` Javier Martinez Canillas
2013-10-28 13:32 ` Tomi Valkeinen
2013-10-28 14:25 ` Javier Martinez Canillas
2013-07-13 2:31 ` Olof Johansson
2013-07-13 3:10 ` Olof Johansson
2013-07-15 6:55 ` Tony Lindgren
2013-07-06 21:36 ` Arnd Bergmann
2013-07-06 23:37 ` debugging options (was: Re: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c) Russell King - ARM Linux
2013-05-17 19:17 ` [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c Tony Lindgren
2013-06-03 15:28 ` Ming Lei
2013-06-12 16:31 ` Tony Lindgren
2013-06-12 17:14 ` Tony Lindgren
2013-06-13 9:21 ` Sricharan R
2013-06-13 10:12 ` Sricharan R
2013-06-13 11:05 ` Tony Lindgren
2013-06-13 13:36 ` Ming Lei
2013-06-14 13:31 ` Ming Lei
2013-06-14 13:58 ` Ming Lei
2013-06-17 7:42 ` Sricharan R
2013-06-17 8:06 ` Arnaud Patard (Rtp)
2013-06-17 8:16 ` Ming Lei
2013-06-17 8:27 ` Tony Lindgren [this message]
2013-06-17 8:41 ` Ming Lei
2013-06-17 8:49 ` Tony Lindgren
2013-06-17 8:24 ` Tony Lindgren
2013-06-17 9:46 ` Arnaud Patard (Rtp)
2013-06-17 10:26 ` Tony Lindgren
2013-06-18 11:27 ` Tony Lindgren
2013-06-19 9:45 ` Arnaud Patard (Rtp)
2013-06-19 9:58 ` Tony Lindgren
2013-06-20 7:29 ` Arnaud Patard (Rtp)
2013-06-21 6:01 ` Tony Lindgren
2013-05-17 19:17 ` [PATCH 3/6] ARM: OMAP2+: Remove legacy mux data for omap4 Tony Lindgren
2013-05-17 19:17 ` [PATCH 4/6] ARM: OMAP2+: Remove omap4 pdata from hsmmc.c Tony Lindgren
2013-05-17 19:18 ` [PATCH 5/6] ARM: OMAP2+: Remove omap4 pdata for USB Tony Lindgren
2013-05-17 19:18 ` [PATCH 6/6] ARM: OMAP2+: Remove omap4 ocp2scp pdata Tony Lindgren
2013-05-17 20:05 ` Felipe Balbi
2013-05-21 11:53 ` Kishon Vijay Abraham I
2013-06-07 10:05 ` [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tomi Valkeinen
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=20130617082724.GI20992@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).