[U-Boot] [PATCH] VoVPN-GW_100MHz: drop unsupported board configuration
The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.
Signed-off-by: Wolfgang Denk wd@denx.de ---
This commit shows a problem with the concept of the "README.scrapyard" file: I'm supposed to enter the commit ID for the commit I'm just about to check in; this cannot work. Hope we remember to clean this up when making the next entries...
Anybody having any better ideas? Some clever git attributes trick?
boards.cfg | 1 - doc/README.scrapyard | 1 + 2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/boards.cfg b/boards.cfg index 4efbff8..42fc967 100644 --- a/boards.cfg +++ b/boards.cfg @@ -524,7 +524,6 @@ MPC8272ADS powerpc mpc8260 mpc8260ads freescale - MPC8260ADS:ADSTYPE=CONFIG_SYS PQ2FADS-VR powerpc mpc8260 mpc8260ads freescale - MPC8260ADS:ADSTYPE=CONFIG_SYS_PQ2FADS,8260_CLKIN=66000000 PQ2FADS-ZU powerpc mpc8260 mpc8260ads freescale - MPC8260ADS:ADSTYPE=CONFIG_SYS_PQ2FADS PQ2FADS_lowboot powerpc mpc8260 mpc8260ads freescale - MPC8260ADS:ADSTYPE=CONFIG_SYS_PQ2FADS,SYS_TEXT_BASE=0xFF800000 -VoVPN-GW_100MHz powerpc mpc8260 vovpn-gw funkwerk - VoVPN-GW:CLKIN_100MHz VoVPN-GW_66MHz powerpc mpc8260 vovpn-gw funkwerk - VoVPN-GW:CLKIN_66MHz MPC8308RDB powerpc mpc83xx mpc8308rdb freescale MPC8323ERDB powerpc mpc83xx mpc8323erdb freescale diff --git a/doc/README.scrapyard b/doc/README.scrapyard index a707c6f..4286559 100644 --- a/doc/README.scrapyard +++ b/doc/README.scrapyard @@ -11,6 +11,7 @@ easily if here is something they might want to dig for...
Board Arch CPU removed Commit last known maintainer/contact ============================================================================= +VoVPN-GW_100MHz powerpc MPC8260 - 2010-10-24 Juergen Selent j.selent@elmeg.de NC650 powerpc MPC852 333d86d 2010-10-19 Wolfgang Denk wd@denx.de CP850 powerpc MPC852 333d86d 2010-10-19 Wolfgang Denk wd@denx.de logodl ARM PXA2xx 059e778 2010-10-18 August Hoeraendl august.hoerandl@gmx.at
On 2010/10/24 4:00 PM, Wolfgang Denk wrote:
The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.
Signed-off-by: Wolfgang Denk wd@denx.de
This commit shows a problem with the concept of the "README.scrapyard" file: I'm supposed to enter the commit ID for the commit I'm just about to check in; this cannot work. Hope we remember to clean this up when making the next entries...
Anybody having any better ideas? Some clever git attributes trick?
How about documenting a git command line for showing when a particular set of lines is added?
e.g.
git blame doc/README.scrapyard
This will show the revision at which a particular line was introduced, and will therefore provide a guide to when the feature was removed.
Include the cmdline at the top of the scrapyard file, and it should be fairly self-evident, I would hope.
Rogan
In message 1287928835-5279-1-git-send-email-wd@denx.de you wrote:
The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.
Signed-off-by: Wolfgang Denk wd@denx.de
This commit shows a problem with the concept of the "README.scrapyard" file: I'm supposed to enter the commit ID for the commit I'm just about to check in; this cannot work. Hope we remember to clean this up when making the next entries...
Anybody having any better ideas? Some clever git attributes trick?
boards.cfg | 1 - doc/README.scrapyard | 1 + 2 files changed, 1 insertions(+), 1 deletions(-)
Aoolied, thanks.
Best regards,
Wolfgang Denk
[looks like this message got lost, resending]
On 2010/10/24 4:00 PM, Wolfgang Denk wrote:
The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.
Signed-off-by: Wolfgang Denk wd@denx.de
This commit shows a problem with the concept of the "README.scrapyard" file: I'm supposed to enter the commit ID for the commit I'm just about to check in; this cannot work. Hope we remember to clean this up when making the next entries...
Anybody having any better ideas? Some clever git attributes trick?
How about documenting a git command line for showing when a particular set of lines is added?
e.g.
git blame doc/README.scrapyard
This will show the revision at which a particular line was introduced, and will therefore provide a guide to when the feature was removed.
Include the cmdline at the top of the scrapyard file, and it should be fairly self-evident, I would hope.
Rogan
Dear Rogan Dawes,
In message 4CC83D9D.505@dawes.za.net you wrote:
[looks like this message got lost, resending]
No, it was not lost, just unreplied.
Include the cmdline at the top of the scrapyard file, and it should be fairly self-evident, I would hope.
Agreed that this is one of the possible workarounds.
Best regards,
Wolfgang Denk
On 2010/10/27 5:10 PM, Wolfgang Denk wrote:
Dear Rogan Dawes,
In message 4CC83D9D.505@dawes.za.net you wrote:
[looks like this message got lost, resending]
No, it was not lost, just unreplied.
Ok, I didn't see it on gmane, so I assumed it had gone astray.
Rogan
participants (2)
-
Rogan Dawes -
Wolfgang Denk