linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] at91: drop at91x40 support
Date: Mon, 20 Sep 2010 08:32:43 +0200	[thread overview]
Message-ID: <20100920063243.GA32018@game.jcrosoft.org> (raw)
In-Reply-To: <4C96F63A.2090704@snapgear.com>

On 15:50 Mon 20 Sep     , Greg Ungerer wrote:
> On 19/09/10 00:28, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >On 19:33 Sat 18 Sep     , Greg Ungerer wrote:
> >>On 18/09/10 16:22, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >>>as it's broken for releases and no one care about it
> >>>
> >>>Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD<plagnioj@jcrosoft.com>
> >>>Cc: Andrew Victor<linux@maxim.org.za>
> >>>Cc: Nicolas Ferre<nicolas.ferre@atmel.com>
> >>>Cc: Greg Ungerer<gerg@snapgear.com>
> >>
> >>NAK, I care. I sent a fix to this very list about a week ago
> >>to fix the current compile problem.
> >sorry but not see it
> 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-September/025404.html
> 
> 
> >and I see it failled to build for at least 4 releases and
> 
> And this is not really due to the board support code (which
> you propose to remove) at all. It is almost always due to
> breakage of something else. The patch I reference above is
> a good example. Breakage in the non-MMU support code is
> another example (and I have another patch I need to send to
> fix a problem there too).
which means no one test it or used it
> 
> 
> >no debug-macro.S for years
> >since what 4 or 5 years we just have the timer and irq
> 
> I don't follow. What is wrong with
> arch/arm/mach-at91/include/mach/debug-macro.S?
the at91x40 can not use it as it's not have DBGU support


> 
> The AT91x40 parts are pretty simple, what else do you expect?
> 
> 
> >do you have plan to update it?
> 
> I don't see anything to update. It does exactly what I want it to do.
> The board support code you point at causes me no troubles, and not
> very often do I need to fix/change/update it.
you have no flash, no uart, no pio support, no watchdog supportm so tc support,
the CPU type is no even selected in the Kconfig

so yes the current implementation is not really usefull for anything

Best Regards,
J.

  reply	other threads:[~2010-09-20  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18  6:22 [PATCH] at91: drop at91x40 support Jean-Christophe PLAGNIOL-VILLARD
2010-09-18  9:33 ` Greg Ungerer
2010-09-18 14:28   ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-20  5:50     ` Greg Ungerer
2010-09-20  6:32       ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-09-20  6:44         ` Greg Ungerer
2010-09-23 11:22           ` Jean-Christophe PLAGNIOL-VILLARD

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=20100920063243.GA32018@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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).