From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 2/5] [PPC] Merge common virtex header files
Date: Tue, 01 May 2007 00:35:03 -0400 [thread overview]
Message-ID: <4636C377.4070101@dlasys.net> (raw)
In-Reply-To: <528646bc0704292141n322c145cmc3d2606b13b0b053@mail.gmail.com>
Grant Likely wrote:
>
> Is the redboot bd_info structure already in the kernel tree? We could
> use a config option to select between the u-boot and redboot
> structures for all virtex platforms. That would keep the uglyness
> down to a minimum.
>
> g.
>
There are a plethora of bd_info's in the kernel tree. I think that
u-boot is probably the most common,
but the u-boot one is huge and full of cruft.
There are also likely to be any number for board/loader combinations
that are not in the kernel.
I have cut an pasted ours below - not that I am trying to sell it.
But I would prefer that if there is a bd_info struct that it be defined
by the board not virtex.h or virtex.c.
//Information passed to program when it is executed.
typedef struct _BOARD_INFO
{uint32_t bi_signature; // 0x00 valid bi signature
uint32_t bi_memMax; // 0x04 DRAM installed, maximum byte
address
uint32_t bi_intfreq; // 0x08 Processor speed, in Hz
uint32_t bi_busfreq; // 0x0C PLB Bus speed, in Hz
uint32_t bi_version; // 0x10 local pico number format #.##,
eg 3.09
uint8_t *bi_cmdline; // 0x14
uint32_t bi_capabilities; // 0x18 Pico capabilities mask
uint32_t bi_debug; // 0x1C Pico flags mask
uint32_t bi_flashstart; // 0x20 start of FLASH memory
uint32_t bi_flashsize; // 0x24 size of FLASH memory
uint32_t bi_envSize; // 0x28 environment size
uint8_t bi_enetaddr[6]; // 0x2C Local Ethernet MAC address
uint16_t bi_cflags; // 0x32 console flags
char *bi_envP; // 0x34 pointer to environment string
uint32_t bi_model; // 0x38 0x0E16'FX', (ie 0x0E164658) etc
uint32_t bi_resv; // 0x38 reserved
} BOARD_INFO; // 0x40
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2007-05-01 4:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 7:27 Patchset to establish sanity in Xilinx Virtex support Grant Likely
2007-04-15 7:27 ` [PATCH 1/5] [PPC] Rework Kconfig dependancies for Xilinx Virtex ppc405 platform Grant Likely
2007-04-15 7:27 ` [PATCH 2/5] [PPC] Merge common virtex header files Grant Likely
2007-04-15 7:27 ` [PATCH 3/5] [PPC] New registration for common Xilinx Virtex ppc405 platform devices Grant Likely
2007-04-15 7:27 ` [PATCH 4/5] [PPC] Stop using ppc_sys for Xilinx Virtex boards Grant Likely
2007-04-15 7:27 ` [PATCH 5/5] [PPC] Add uartlite boot console driver for the zImage wrapper Grant Likely
2007-04-25 12:13 ` Peter Korsgaard
2007-04-25 12:12 ` [PATCH 4/5] [PPC] Stop using ppc_sys for Xilinx Virtex boards Peter Korsgaard
2007-04-25 12:11 ` [PATCH 3/5] [PPC] New registration for common Xilinx Virtex ppc405 platform devices Peter Korsgaard
2007-04-27 18:50 ` Grant Likely
2007-04-25 12:07 ` [PATCH 2/5] [PPC] Merge common virtex header files Peter Korsgaard
2007-04-27 18:49 ` Grant Likely
2007-04-30 4:26 ` Peter Korsgaard
2007-04-30 4:41 ` Grant Likely
2007-05-01 4:35 ` David H. Lynch Jr. [this message]
2007-05-01 7:16 ` Grant Likely
2007-05-01 4:28 ` David H. Lynch Jr.
2007-05-01 6:54 ` Grant Likely
2007-04-15 10:48 ` [PATCH 1/5] [PPC] Rework Kconfig dependancies for Xilinx Virtex ppc405 platform Dale Farnsworth
2007-04-15 14:20 ` Grant Likely
2007-04-25 12:03 ` Peter Korsgaard
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=4636C377.4070101@dlasys.net \
--to=dhlii@dlasys.net \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.