On Wed, May 4, 2011 at 11:19 AM, Mark Cave-Ayland mark.cave-ayland@siriusit.co.uk wrote:
On 04/05/11 08:57, Artyom Tarasenko wrote:
I think so. Actually m48t59 is emulated in sparc32, but not connected in case of sparc64.
The referencing comment in the opensolaris source:
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/sun4u/os/f...
- Appropriate tod module will be dynamically selected while booting
- based on finding a device tree node with a "device_type" property
value
- of "tod". If such a node describing tod is not found, for backward
- compatibility, a node with a "name" property value of "eeprom" and
- "model" property value of "mk48t59" will be used. Failing to find a
- node matching either of the above criteria will result in no tod
module
- being selected; this will cause the boot process to halt
On the real U30 machine:
ok cd /pci@1f,4000/ebus@1/eeprom@14,0 ok .properties address fffa4000 reg 00000014 00000000 00002000 model mk48t59 name eeprom ok
Oh, that's interesting. If I look in drivers/obio.c then I can see an eeprom device named "mk48t08" rather than "mk48t59". Is this a typo, or does it need a new explicit device defined in pci.c's ebus_config_cb() somewhere?
Have you meanwhile tried to change the name to "mk48t59" ? I think changing the chip in qemu is not neccessary (and even if it is the name in OpenBIOS has to be changed anyway).
If Blue's subsequent comment about it already being wired up to the ebus is correct, then yes, probably renaming might work if the device registers are mapped correctly.
Yes, Blue is right (and I've managed to correct my wrong statement one day before he did), the device is connected via ebus.
Alas this was the last time I touched SPARC64 before switching to SPARC32, and so I never really looked into this.
ATB,
Mark.
-- Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS Sirius Corporation plc - control through freedom http://www.siriusit.co.uk t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs