linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: linuxppc-embedded@ozlabs.org, paulus@samba.org
Cc: Peter Korsgaard <jacmet@sunsite.dk>,
	Andrei Konovalov <akonovalov@ru.mvista.com>,
	Rick Moleres <Rick.Moleres@xilinx.com>
Subject: [PATCH 7/7] [PPC] Don't define a custom bd_t for Xilixn Virtex based boards.
Date: Fri, 27 Apr 2007 13:50:05 -0600	[thread overview]
Message-ID: <11777034162194-git-send-email-grant.likely@secretlab.ca> (raw)
In-Reply-To: <11777034164090-git-send-email-grant.likely@secretlab.ca>

Why create a platform specific board_info structure that is hacked
together, ugly, and dangerous, when we've got a perfectly fine common
board_info structure that is hacked-together, ugly and dangerous.

Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
---
 arch/ppc/platforms/4xx/virtex.h |   15 +--------------
 1 files changed, 1 insertions(+), 14 deletions(-)

diff --git a/arch/ppc/platforms/4xx/virtex.h b/arch/ppc/platforms/4xx/virtex.h
index 4fc76da..7382804 100644
--- a/arch/ppc/platforms/4xx/virtex.h
+++ b/arch/ppc/platforms/4xx/virtex.h
@@ -14,6 +14,7 @@
 #define __ASM_VIRTEX_H__
 
 #include <asm/ibm405.h>
+#include <asm/ppcboot.h>
 
 /* Ugly, ugly, ugly! BASE_BAUD defined here to keep 8250.c happy. */
 #if !defined(BASE_BAUD)
@@ -21,22 +22,8 @@
 #endif
 
 #ifndef __ASSEMBLY__
-typedef struct board_info {
-	unsigned int	 bi_memsize;		/* DRAM installed, in bytes */
-	unsigned char	 bi_enetaddr[6];	/* Local Ethernet MAC address */
-	unsigned int	 bi_intfreq;		/* Processor speed, in Hz */
-	unsigned int	 bi_busfreq;		/* PLB Bus speed, in Hz */
-	unsigned int	 bi_pci_busfreq;	/* PCI Bus speed, in Hz */
-} bd_t;
-
-/* Some 4xx parts use a different timebase frequency from the internal clock.
- * the Virtex 405 does not, so just use a macro to make tbfreq match intfreq
-*/
-#define bi_tbfreq bi_intfreq
-
 extern const char* virtex_machine_name;
 #define PPC4xx_MACHINE_NAME (virtex_machine_name)
-
 #endif /* !__ASSEMBLY__ */
 
 /* We don't need anything mapped.  Size of zero will accomplish that. */
-- 
1.5.1

  reply	other threads:[~2007-04-27 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 19:49 [PATCH 0/7] Revised Xilinx virtex establish sanity patchset Grant Likely
2007-04-27 19:49 ` Grant Likely
2007-04-27 19:49   ` [PATCH 1/7] [PPC] Rework Kconfig dependancies for Xilinx Virtex ppc405 platform Grant Likely
2007-04-27 19:50     ` [PATCH 2/7] [PPC] Merge common virtex header files Grant Likely
2007-04-27 19:50       ` [PATCH 3/7] [PPC] New registration for common Xilinx Virtex ppc405 platform devices Grant Likely
2007-04-27 19:50         ` [PATCH 4/7] [PPC] Stop using ppc_sys for Xilinx Virtex boards Grant Likely
2007-04-27 19:50           ` [PATCH 5/7] [PPC] Add uartlite boot console driver for the zImage wrapper Grant Likely
2007-04-27 19:50             ` [PATCH 6/7] [PPC] Add sane defaults for Xilinx EDK generated xparameters files Grant Likely
2007-04-27 19:50               ` Grant Likely [this message]
2007-04-28  1:53                 ` XILINX SPI IP core with INTC IP core Leonid
2007-04-30 15:31                   ` Rick Moleres
2007-04-30 16:19                     ` Leonid

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=11777034162194-git-send-email-grant.likely@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=Rick.Moleres@xilinx.com \
    --cc=akonovalov@ru.mvista.com \
    --cc=jacmet@sunsite.dk \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=paulus@samba.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).