The 85x0 BSP has an example of how to do this in startup.

init_hwinfo.c contains this function


static void add_one_tsec(unsigned off, 
					unsigned intr_tx, 
					unsigned int intr_rx, 
					unsigned int intr_err,
					unsigned char *mac,
					unsigned char phy_addr)
{
	paddr_t		paddr = immr_paddr + off;

	hwi_add_device(HWI_ITEM_BUS_UNKNOWN, HWI_ITEM_DEVCLASS_NETWORK,
"tsec", 0);

	hwi_add_location(paddr, 8, 0, hwi_find_as(paddr, 0));

	hwi_add_irq(intr_tx);
	hwi_add_irq(intr_rx);
	hwi_add_irq(intr_err);

	if (mac != NULL) {
		hwi_add_nicaddr(mac, 6);
	}

	if (phy_addr != 0xFF) {
		hwi_add_nicphyaddr(phy_addr);
	}
}

You can then see the corresponding code in the mpc5xx network driver on
the foundry which uses the "syspage" option


http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev_q
nx/mpc85xx/detect.c?root=core_networking&rev=552&system=exsy1001&view=ma
rkup


(in the ppc85xx_get_syspage function)

		Robert.
-----Original Message-----
From: Brian Stecher [mailto:community-noreply@qnx.com] 
Sent: Friday, February 13, 2009 9:19 AM
To: ostech-core_os
Subject: Re: Writing to the system page?

On Fri, Feb 13, 2009 at 06:26:30AM -0500, Marc Roessler wrote:
> So my idea is to write that info to the system page when the image is
setup by UBoot, then start the image.
> 
> However, I haven't found any documentation on how to write to the
system page?

You can't write to the system page from the IPL (UBoot) since it doesn't
exist at that time - it's dynamically allocated by the startup process.
What you need to do is put the information in some place that the
startup code can find and then in init_hwinfo routine of startup,
extract the info and use the hwi_* functions (e.g. hwi_add_nicphyaddr())
to put the information into the hwinfo section of the system page for
the driver to find.

-- 
Brian Stecher (bstecher@qnx.com)        QNX Software Systems
phone: +1 (613) 591-0931 (voice)        175 Terence Matthews Cr.
       +1 (613) 591-3579 (fax)          Kanata, Ontario, Canada K2M 1W8

_______________________________________________
OSTech
http://community.qnx.com/sf/go/post22201

> On Fri, Feb 13, 2009 at 06:26:30AM -0500, Marc Roessler wrote:
> > So my idea is to write that info to the system page when the image is setup 
> by UBoot, then start the image.
> > 
> > However, I haven't found any documentation on how to write to the system 
> page?
> 
> You can't write to the system page from the IPL (UBoot) since it doesn't
> exist at that time - it's dynamically allocated by the startup process.
> What you need to do is put the information in some place that the 

The main problem here is "some place".
There is no senseful interface in the u-boot code to pass the needed info to startup. There is a boardinfo structure, 
which contains some infos, but not all. You only get this structure with the "bootm" command, not with "go" or "bootelf"
. Normally you need access to the u-boot env. It would be nice to get the ram copy of this env from u-boot, to fill in a
 hwinfo-entry during startup... Well, no interface for this in u-boot.
I am thinking about an u-boot-patch, which will pass the boardinfo-struct, the address and size of the u-boot env by CPU
 registers(Perhaps r31,r30,... in the PPC case, saving r3,r4,... for arc, argv)...

Well, here u-boot is like the Linux kernel, ...why having clean binary interfaces if you can patch the source. ;-)  

- Michael


startup
> code can find and then in init_hwinfo routine of startup, extract the info 
> and use the hwi_* functions (e.g. hwi_add_nicphyaddr()) to put the 
> information into the hwinfo section of the system page for the driver 
> to find.
> 
> -- 
> Brian Stecher (bstecher@qnx.com)        QNX Software Systems
> phone: +1 (613) 591-0931 (voice)        175 Terence Matthews Cr.
>        +1 (613) 591-3579 (fax)          Kanata, Ontario, Canada K2M 1W8