Skip to contentSkip to conversation

VoVPN-GW_100MHz: drop unsupported board configuration

PATCH New Wolfgang Denk 2 participants 6 messages Oct 24, 2010 – Oct 27, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.

---

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(-)
boards.cfg +0 -1
index 4efbff8..42fc967 100644
@@ -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
doc/README.scrapyard +1 -0
index a707c6f..4286559 100644
@@ -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 <[email protected]>
 NC650	powerpc	MPC852	333d86d   2010-10-19	Wolfgang Denk <[email protected]>
 CP850	powerpc	MPC852	333d86d   2010-10-19	Wolfgang Denk <[email protected]>
 logodl	ARM	PXA2xx	059e778   2010-10-18	August Hoeraendl <[email protected]>
Signature · 1 line
1.7.2.3
#1 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

Quoted 4 lines · Wolfgang Denk

The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.

Quoted 9 lines

---

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

#2 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

In reply to Wolfgang Denk
Quoted 11 lines · In message <[email protected]> you wrote:

The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.

---

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...

Quoted 5 lines

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

Signature · 4 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I'd rather be led to hell than managed to heaven.
#3 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

In reply to Wolfgang Denk

[looks like this message got lost, resending]

Quoted 4 lines · Wolfgang Denk

The 100MHz configuation of the VoVPN-GW has never been supported, so drop it now.

Quoted 9 lines

---

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

#4 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

Dear Rogan Dawes,

Quoted 1 line · In message <[email protected]> you wrote:

[looks like this message got lost, resending]

No, it was not lost, just unreplied.

Quoted 2 lines

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

Signature · 6 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If all the Chinese simultaneously jumped into the Pacific  off  a  10
foot platform erected 10 feet off their coast, it would cause a tidal
wave that would destroy everything in this country west of Nebraska.
#5 lore raw

PATCH 1/1 VoVPN-GW_100MHz: drop unsupported board configuration

Quoted 6 lines · Wolfgang Denk

Dear Rogan Dawes,

Quoted 1 line · In message <[email protected]> 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