public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] avr32: Retire AVR32 for good
Date: Wed, 5 Jul 2017 12:04:15 +0200	[thread overview]
Message-ID: <595CB99F.7020802@denx.de> (raw)
In-Reply-To: <CAHp75Vev3XCdC+TkZu+1u5nCZ1gK7-aVq2_HmpGpLg09FO7+=w@mail.gmail.com>

Hello Andy,

Am 05.07.2017 um 11:49 schrieb Andy Shevchenko:
> On Wed, Jul 5, 2017 at 6:08 AM, Heiko Schocher <hs@denx.de> wrote:
>> Am 04.07.2017 um 18:25 schrieb Andy Shevchenko:
>>>
>>> AVR32 is gone. It's already more than two years for no support in
>>> Buildroot,
>>> even longer there is no support in GCC (last version is heavily patched
>>> 4.2.4).
>>>
>>> Linux kernel v4.12 got rid of it (and v4.11 didn't build successfully).
>>>
>>> There is no good point to keep this support in U-Boot either.
>
>> It seems you do not remove all avr32 specific defines here from this
>> list, for example:
>>
>> pollux:u-boot hs [master] $ grep -lr SYS_CLKDIV_CPU .
>> ./arch/avr32/cpu/at32ap700x/clk.c
>> ./arch/avr32/cpu/cpu.c
>> ./arch/avr32/include/asm/arch-at32ap700x/clk.h
>> ./scripts/config_whitelist.txt
>> ./include/configs/atstk1002.h
>> ./include/configs/grasshopper.h
>> ./include/configs/atngw100.h
>> ./include/configs/atngw100mkii.h
>> pollux:u-boot hs [master] $
>>
>> Can you please try to check here the defines you remove for
>> example in arch/avr32/cpu?
>
> Thanks, I would use advice from Tom.

Fine.

>> Oh... you do not remove the "grasshoper" board ... it is also
>> an AVR32 based board:
>>
>> pollux:u-boot hs [master] $ cat configs/grasshopper_defconfig | grep AVR32
>> CONFIG_AVR32=y
>> pollux:u-boot hs [master] $
>
>> Ok, you only missed the grasshoper board, can you please remove this
>> too?
>
>>From the above patch:
> "delete mode 100644 configs/grasshopper_defconfig"
>
> What did you miss?

Ah, it was too early in the morning ...

You only remove configs/grasshopper_defconfig, but not:

./include/configs/grasshopper.h

nor the files in

./board/in-circuit/grasshopper

and as there is only one in-circuit board, please delete the complete
./board/in-circuit directory.

Thanks!

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2017-07-05 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 16:25 [U-Boot] [PATCH v1] avr32: Retire AVR32 for good Andy Shevchenko
2017-07-04 19:37 ` Tom Rini
2017-07-04 19:50   ` Simon Glass
2017-07-05  3:08 ` Heiko Schocher
2017-07-05  3:21   ` Tom Rini
2017-07-05  9:49   ` Andy Shevchenko
2017-07-05 10:04     ` Heiko Schocher [this message]
2017-07-05 10:00 ` Andy Shevchenko

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=595CB99F.7020802@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /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